Backup Fails with Invalid RECID Error: Scenario

Recovery Manager: Release 11.2.0.3.0 - Production on Mon Mar 2 08:34:53 2015

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: testdb01 (DBID=120324587)

connected to recovery catalog database

RMAN>

echo set on

RMAN> run {

2> backup  tag "INCR_1_MON_02" as compressed backupset archivelog all delete input filesperset 4 ;

3> backup  tag "INCR_1_MON_02" incremental level=1 database include current controlfile;

4> backup  tag "INCR_1_MON_02" as compressed backupset archivelog all delete input filesperset 4 ;

5> backup  tag "INCR_1_MON_02" current controlfile;

6> backup  tag "INCR_1_MON_02" current controlfile for standby;

7> }

Starting backup at 02-MAR-15

current log archived

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of backup command at 03/02/2015 08:34:55

RMAN-03014: implicit resync of recovery catalog failed

RMAN-06004: ORACLE error from recovery catalog database: RMAN-20035: invalid high RECID

Solution:

rmanc

Recovery Manager: Release 11.2.0.3.0 - Production on Mon Mar 2 08:47:09 2015

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: T7BIO (DBID=123456789)

connected to recovery catalog database

RMAN> unregister database;

database name is "testdb01" and DBID is 123456789

Do you really want to unregister the database (enter YES or NO)? yes

database unregistered from the recovery catalog

RMAN> register database;

database registered in recovery catalog

starting full resync of recovery catalog

full resync complete

Backup Fails with Invalid RECID Error: Scenario

In this scenario, you attempt a backup and receive the following error messages:

RMAN-3014: Implicit resync of recovery catalog failed

RMAN-6038: Recovery catalog package detected an error

RMAN-20035: Invalid high RECID error

Backup Fails with Invalid RECID Error: Diagnosis

In one common scenario, you restore a backup control file created through a non-Oracle mechanism, and then open the database without the RESETLOGS option. If you had created the backup control file through the RMAN BACKUP command or the SQL ALTER DATABASE BACKUP CONTROLFILE statement, then Oracle would have required you to reset the online logs.

The control file and the recovery catalog are now not synchronized. The database control file is older than the recovery catalog, because at one time the recovery catalog resynchronized with the old current control file, and now the database is using a backup control file. RMAN detects that the control file currently in use is older than the control file previously used to resynchronize.

Another common scenario occurs when you attempt to copy the target database to a new machine as follows:

On machine 1, you shut down the database and make a copy of the control file with an operating system utility. You do not use CATALOG to add this control file copy to the repository.

You transfer the control file copy to machine 2.

On machine 2, you create a new initialization parameter file and new database instance.

You mount the control file copy on machine 2. Oracle does not recognize the control file as a backup control file: to Oracle it looks like the current control file.

You start RMAN and connect to the new target database and the recovery catalog on machine 2. Because the control file was not created with RMAN and was not cataloged as a control file copy, RMAN sees the database on machine 2 as the database on machine 1.

You restore and recover database the new database on machine 2 and then open it. As a consequence, various records are added to the recovery catalog during the restore and recovery. For example, the highest RECID in the recovery catalog moves from 90 to 100.

On machine 1, you start RMAN and connect to the original target database and recovery catalog. The recovery catalog indicates that the highest RECID is 100, but the control file indicates that the highest RECID is 90. The control file RECID should always be greater than or equal to the recovery catalog RECID, so RMAN issues RMAN-20035.

*********************************************************************************