We're here to help!

How to sync standby from task performed on primary in non-archive mode

Follow
Description
This article explains how to recover your standby database after you performed tasks on primary in
non-archive mode.
Ex: You would want to turn off archive mode for housekeeping or for loading data which would produce huge amount of archived logs and when storage is constraint.
 
Note:  During these task it is recommended to turn off the schedulers and daemon on both primary and standby.
 
Solution

 Synchronising standby database

Environment Linux: dbv1 (Primary), dbv2 (Standby)

1. Send log

Screen_Shot_2019-12-17_at_3.44.52_PM.png

2. Apply Log

Screen_Shot_2019-12-17_at_3.45.05_PM.png

3. Check the log gap report.

Screen_Shot_2019-12-17_at_3.45.17_PM.png

4. Stop the scheduler and daemon if running

5.  Primary - Disable archive log

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.

Total System Global Area 668082176 bytes
Fixed Size 2256232 bytes
Variable Size 247464600 bytes
Database Buffers 411041792 bytes
Redo Buffers 7319552 bytes
Database mounted.
SQL> alter database noarchivelog;
Database altered.
SQL> alter database open;
Database altered.

6. Perform necessary task in primary

7. Enable the archive log mode back in primary

SQL> shutdown immediate;
SQL> startup mount;
ORACLE instance started.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.

8. Perform SSD.

Synchronisation  uses RMAN incremental backup based on primary based on SCN(system change number)

Click here for details

Screen_Shot_2019-12-17_at_3.57.59_PM.png

Screen_Shot_2019-12-17_at_3.59.16_PM.png

9. Send log

Screen_Shot_2019-12-17_at_3.59.37_PM.png

10. Apply log

Screen_Shot_2019-12-17_at_3.59.51_PM.png 

11. Log gap report

Screen_Shot_2019-12-17_at_4.06.23_PM.png

 

 

Have more questions? Submit a request

Comments