In Oracle Data Guard, changing the protection mode involves adjusting the configuration to one of the three protection modes: Maximum Protection, Maximum Availability, or Maximum Performance. The steps to change the protection mode are straightforward but need to be done carefully to avoid any potential issues with your Data Guard setup. Primary database: Verify the … Read more
The ORA-16855 error indicates that the transport lag (the delay in sending redo data from the primary to the standby database) has exceeded the specified threshold. Cause: The current apply lag has exceeded the value specified by the ApplyLagThreshold configurable property. This can be due to either a significant transport lag or poor performance of … Read more
Maximum Protection Mode 1. No data loss 2. Redo has to be written to both Primary redo logs and standby redo logs (of atleast one standby database) before transaction commits 3. Primary database shuts down if redo stream is prevented to write at standby redo logs of atleast one standby database 4. Configure standby redo … Read more
It has been seen in cases where ORA-16401 and ORA-16055 reported in primary alert log when redo log switch is over frequently. So suggestion is to Increase the Size of the Online Redologs to reduce Redolog Switch Frequency. And this may also required to improve primary database performance. Please note if using Maximum Protection mode, … Read more
DISABLE_ARCHIVE_LOGGING From 12c, during Import operations we can disable archive logging, hence no redo will be generated for the whole impdp job. The ideology behind this feature is, when import process is going on with logging and “we can see huge redo log generations which leads to frequent log switches [depending on the exported objects] … Read more
Once an Archive Log is received or archived from a Standby Redo Log on the Standby Database, it is registered in the Standby Control file (you can query the Registration by v$archived_log on a Physical Standby Database and dba_logstdby_log on a Logical Standby Database). If such a File is missing or corrupted for any Reason … Read more
Cause: Looks like ADR is having the issue. Solution: Added the below parameter in the both the nodes and restarted the listener DIAG_ADR_ENABLE_LISTENER=OFF There are 3 parameters associated with ADR: DIAG_ADR_ENABLED DIAG_SIGHANDLER_ENABLED DIAG_DDE_ENABLED As long as you don’t set “DIAG_ADR_ENABLED = OFF” … ADR will still be enabled for the other services. THIS LOG.XML NEED … Read more
Check the datafile location along with name: Set standby file management parameter to manual before moving datafile: Stop the MRP : Move the datafile now : Bounce the DB to overcome this issue: Open the DB in read only: Start MRP: Now validate ,all datafiles are in same location:
Issue : ORA-16047: DGID mismatch between destination setting and target database Since LOG_ARCHIVE_DEST_3 is getting error, we will defer it and enable it back, which will resolve the issue. Error is now resolved. Hope it worked !! 