Oracle 19, recover standby become easier

Since oracle 19 , recover standby become quite easier. Here my dataguard configuration and it shows ORA-16810 error.

DGMGRL> show configuration
Configuration - ora19_cfg
  Protection Mode: MaxPerformance
  Members:
  ora19_pri - Primary database
    ora19_stb - Physical standby database
    Error: ORA-16810: multiple errors or warnings detected for the member
 
Fast-Start Failover:  Disabled
Configuration Status:
ERROR   (status updated 6 seconds ago)

To recovery standby ,we need disable redo apply at first.

DGMGRL> edit database ora19_stb set state=apply-off;

Then, run recover standby from service with rman

RMAN> recover standby database from service '//mydom-dscan:1521/ora19_pri.mydomaine.local';
Starting recover at 19-OCT-21
using target database control file instead of recovery catalog
Executing: alter database flashback off
Oracle instance started
Total System Global Area   20619403816 bytes
Fixed Size                    12685864 bytes
Variable Size               5771362304 bytes
Database Buffers           14696841216 bytes
Redo Buffers                 138514432 bytes
contents of Memory Script:
{
   restore standby controlfile from service  '//mydom-dscan:1521/ora19_pri.mydomaine.local';
   alter database mount standby database;
}
executing Memory Script
Starting restore at 19-OCT-21
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=266 instance=ora19_stb1 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: using network backup set from service //mydom-dscan:1521/ora19_pri.mydomaine.local
channel ORA_DISK_1: restoring control file
..
Finished restore at 19-OCT-21
released channel: ORA_DISK_1
Statement processed
Executing: alter system set standby_file_management=manual
contents of Memory Script:
{
set newname for tempfile  1 to
 "+DATA4101/ora19_stb/TEMPFILE/temp.763.1085327449";
....
set newname for datafile  94 to
...
switch datafile all;
}
executing Memory Script
contents of Memory Script:
{
  recover database from service  '//mydom-dscan:1521/ora19_pri.mydomaine.local';
}
executing Memory Script
Starting recover at 19-OCT-21
hannel ORA_DISK_1: restore complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using network backup set from service //mydom-dscan:1521/ora19_pri.mydomaine.local
....
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
...
starting media recovery
..
archived log for thread 1 with sequence 848 is already on disk as file +RECO/ora19_stb/ARCHIVELOG/2021_10_19/thread_1_seq_848.56713.1086362725
..
media recovery complete, elapsed time: 00:00:01
Finished recover at 19-OCT-21
flashback needs to be reenabled on standby open
Executing: alter system set standby_file_management=auto
Finished recover at 19-OCT-21

Enable redo apply

DGMGRL> edit database ora19_stb set state=apply-on;

DGMGRL> show configuration
Configuration - ora19_cfg
  Protection Mode: MaxPerformance
  Members:
  ora19_pri - Primary database
    ora19_stb - Physical standby database
      rcat53        - Recovery appliance (receiving current redo)
    rcat54        - Recovery appliance
Fast-Start Failover:  Disabled
Configuration Status:
SUCCESS   (status updated 8 seconds ago)

Published by dbaliw

Highly experienced Oracle Database Administrator and Exadata Specialist with over 15 years of expertise in managing complex database environments. Skilled in cloud technologies, DevOps practices, and automation. Certified Oracle Cloud Infrastructure Architect and Oracle Certified Master with a strong background in performance tuning, high availability solutions, and database migrations.

Leave a comment