This content has been marked as final. Show 4 replies
One of the first steps in creating dataguard is to put the database in logging mode:
So any statement using the nologging option would be ignored.
alter database force logging; select force_logging from v$database;
Is your database in nologging mode and there is a physical standby?? If this is the case then you will have some issues if there were any nologging statements done on the database.
Currently it is in Force Logging. (since i am in this project)
But, i got the info from others that there was some problem with the no logging during the DR dirll in the past. ( I dont have full details of this).
So, I just want to make sure if some no-logging operations were done in the past, which may cause problems after opening the stdby db in Read-write mode
Is there a way to figure out, which tables/segments/datafiles has issue with No-logging ?
Just found this query after searching....
Having non- zero values for UNRECOVERABLE_CHANGE#, UNRECOVERABLE_TIME states that the NO logging operation was done on that datafile.
select file#, name, UNRECOVERABLE_CHANGE#, UNRECOVERABLE_TIME from v$datafile;
I am not sure, how far it is reliable. Tried testing by append hing without No Logging, but still i get the ZERO value.