SRDC – Collect Data Guard Diagnostic Information (Doc ID 2219763.1)

Been in DataGuard HELL and Doc ID 2219763.1 is a good starting point for troubleshooting.

Many SR’s opened without any success. Oracle suppport suggest to recreate controlfile – YIKES!

Basically, RMAN backup is being performed from standby.

From primary RMAN deletes archivelog to prevent fill up.

My unnderstanding, if archivelogs are in FRA, then cleanup shoud be automatic provided there are no BUGS.

Solution for QA – RMAN delete archivelogs without connecting to catalog at primary

and RMAN backups connecting to catalog at standby. Not sure if there are any repercussions.

RMAN Archivelog Deletion Errors – 12.1.0.2.0 – Script below seems overly complicated.

Any suggestions or ideas? TIA.

16> connect target *
17> connect catalog *
18>
19> crosscheck archivelog all;
20> delete noprompt archivelog until time 'sysdate-4/24';
21> list archivelog all;
22>
23> run {
24> allocate channel c1 device type disk;
25> SQL "alter database backup controlfile to trace as
25> ''/tmp/ctl_@_trace.sql'' reuse resetlogs";
26> SQL "create pfile=''/tmp/init@.ora'' from spfile";
27> release channel c1;
28> }
29> show all;
30> crosscheck archivelog all;
31> crosscheck backup;
32> delete noprompt obsolete;
33> delete noprompt expired backup;
34> resync catalog from db_unique_name all;
35>

RMAN-06216: WARNING: db_unique_name mismatch - 7 objects could not be updated
RMAN-06218: List of objects requiring same operation on database with db_unique_name SID_DR
RMAN-06211: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece    c-1072717639-20240124-03
RMAN-06214: Backup Piece    c-1072717639-20240124-05
RMAN-06214: Backup Piece    c-1072717639-20240124-07
RMAN-06214: Backup Piece    c-1072717639-20240125-01
RMAN-06214: Backup Piece    c-1072717639-20240125-03
RMAN-06214: Backup Piece    c-1072717639-20240125-05
RMAN-06214: Backup Piece    c-1072717639-20240126-00

RMAN-06216: WARNING: db_unique_name mismatch - 6 objects could not be updated
RMAN-06218: List of objects requiring same operation on database with db_unique_name SID_DR
RMAN-06211: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece    c-1072717639-20240124-02
RMAN-06214: Backup Piece    c-1072717639-20240125-00
RMAN-06214: Backup Piece    c-1072717639-20240125-02
RMAN-06214: Backup Piece    c-1072717639-20240125-04
RMAN-06214: Backup Piece    c-1072717639-20240125-07
RMAN-06214: Backup Piece    c-1072717639-20240126-01

RMAN-06207: WARNING: 6 objects could not be deleted for SBT_TAPE channel(s) due
RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece    c-1072717639-20240124-02
RMAN-06214: Backup Piece    c-1072717639-20240124-05
RMAN-06214: Backup Piece    c-1072717639-20240125-00
RMAN-06214: Backup Piece    c-1072717639-20240125-02
RMAN-06214: Backup Piece    c-1072717639-20240125-04
RMAN-06214: Backup Piece    c-1072717639-20240125-07

RMAN-06207: WARNING: 6 objects could not be deleted for SBT_TAPE channel(s) due
RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece    c-1072717639-20240124-03
RMAN-06214: Backup Piece    c-1072717639-20240124-07
RMAN-06214: Backup Piece    c-1072717639-20240125-01
RMAN-06214: Backup Piece    c-1072717639-20240125-03
RMAN-06214: Backup Piece    c-1072717639-20240125-05
RMAN-06214: Backup Piece    c-1072717639-20240126-00