The DG main library forgot what the nologgin table operation is like in the case of force logging.

This article introduces you to the DG main library forget force logging in the case of insert append nologgin table operation is how, the content is very detailed, interested friends can refer to, hope to be helpful to you.

Some netizens asked if there is no force logging in the primary library in the dg environment, what will happen to the insert append nologgin table, and whether the standby will actively report an error to abort synchronization, and so on.

In this case, standby will not take the initiative to report an error, only when the standby side accesses the table, it will report an ORA-26040 error, but it does not affect dg synchronization.

Treatment method:

1) find the corresponding data file, confirm the time of append operation, and find the scn before append through v$archived_log.

2) backup incremental from scn xxxxx datafile 1

3) restore the standby end and resynchronize it

About the DG main library forgot force logging in the case of insert append nologgin table operation is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.