Solutions for RMAN-00600 [13200] in oracle

On dataguard, use rman to connect to the catalog database for backup. When backing up, the rman log reports the following error:

Starting backup at 2014/04/23-10:02:02
Archived log/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_201_9ofpggpg _. arc not found or out of sync with catalog
Skipping inaccessible file/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_201511_9ofpggpg _. arc
Archived log/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_201411_9ofqblsm _. arc not found or out of sync with catalog
Skipping inaccessible file/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_201411_9ofqblsm _. arc
Archived log/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_4412_9ofr6px7 _. arc not found or out of sync with catalog
Skipping inaccessible file/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_201412_9ofr6px7 _. arc
Archived log/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_201413_9ofs2v2m _. arc not found or out of sync with catalog
Skipping inaccessible file/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_201413_9ofs2v2m _. arc
RMAN-06061: WARNING: skipping archived log compromises recoverability
Released channel: ch00
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-03002: failure of backup command at 04/23/2014 10:02:23
RMAN-00600: internal error, arguments [13200] [] [] [] [] []

At the beginning, according to the document: 341337.1, the reason for this error was that the information registered in the catalog database was called during backup because the backup was initiated in the dataguard database, find the corresponding path on the dataguard host and the archived log is deleted manually. Therefore, inaccessible is reported.
We recommend that you set the same directory for the FRA area of production and consumer uard. (Or use link to point to the same directory), and then in rman:

1. Resync catalog
2. Crosscheck archivelog all
3. Delete expired archivelog all;

However, after such processing, the system continues to report errors.

At last, we found that DB_UNIQUE_NAME is still a problem. Because the DB_UNIQUE_NAME parameter is not configured, when you connect to the CATALOG database for backup, there will be two locations in the same log file, causing a backup exception:

G3ah1040: mobprd> rman target/catalog catuser/catpwd @ cattns
 
Recovery Manager: Release 11.2.0.3.0-Production on Wed Apr 23 10:31:53 2014
 
Copyright (c) 1982,201 1, Oracle and/or its affiliates. All rights reserved.
 
Connected to target database: mobprd (DBID = 3585792802)
Connected to recovery catalog database
 
RMAN> list archivelog sequence 201410; <because dataguard does not configure DB_UNIQUE_NAME, two records are archived for the same sequence # in the catalog database.
 
List of Archived Log Copies for database with db_unique_name mobprd
========================================================== ==================================
 
Key Thrd Seq S Low Time
----------------------------
539685219 201410 A 23-APR-14
Name:/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_201511_9ofpggpg _. arc
 
539722379 201410 A 23-APR-14
Name:/aabb/qb/mobprd/log/fra/mobprd/archivelog/2014_04_23/o1_mf_1_201511_9ofpghkq _. arc

Topic: for DB_UNIQUE_NAME, some companies choose to back up data on mongouard to reduce the pressure on production. The master database is rac + asm, and the slave database is a file system. During the backup recovery test, if DB_UNIQUE_NAME is not set, even if the backup is a file on the file system, the path of the restore to asm will be encountered during restore, however, the asm path does not exist.