RMAN-20035: invalid high recid

" It was messed up in RMAN catalog database " if following 2 things mixed.
1) restored old controlfile from old backup AND
2) forget ‘OPEN RESETLOGS’

you will get error just like what I got here:

> rman target / catalog rman1/*@mycatalog

Recovery Manager: Release 10.2.0.3.0 – Production on *

connected to target database: MYDATABASE (DBID=*)
connected to recovery catalog database

RMAN> backup current controlfile;

Starting backup at 20-NOV-07
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 11/20/2007 10:53:18
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20035: invalid high recid

2 options here:
1) unregister/register your target database again, and lose previous backup information except those backup happened during days in CONTROLFILE_RECORD_KEEP_TIME.
2)create new catalog hold new backup and keep old catalog (let it be!)

Let us take the 2dn choice:

SQL> create user rman2 identified by namr default tablespace rman temporary tablespace temp quota unlimited on rman;
User created.

SQL> GRANT connect, resource, recovery_catalog_owner TO rman2;
Grant succeeded.

> rman catalog rman2/*@mycatalog

Recovery Manager: Release 9.2.0.8.0 – 64bit Production

connected to recovery catalog database
recovery catalog is not installed

RMAN> create catalog;
recovery catalog created

> rman target / catalog rman2/*@mycatalog

Recovery Manager: Release 10.2.0.3.0 – Production *

connected to target database: MYDATABASE (DBID=*)
connected to recovery catalog database
PL/SQL package RMAN2.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old

RMAN> UPGRADE CATALOG;
recovery catalog owner is RMAN2
enter UPGRADE CATALOG command again to confirm catalog upgrade

RMAN> UPGRADE CATALOG;
recovery catalog upgraded to version 10.02.00.03
DBMS_RCVMAN package upgraded to version 10.02.00.03
DBMS_RCVCAT package upgraded to version 10.02.00.03

RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete

Now, go to verify it works:
RMAN> run
{
   allocate channel t1 type ‘sbt_tape’
      parms ‘ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)’;2> 3> 4>
5> backup current controlfile;
6> }

allocated channel: t1
channel t1: sid=346 devtype=SBT_TAPE
channel t1: Data Protection for Oracle: version 5.4.1.0

Starting backup at 20-NOV-07
channel t1: starting full datafile backupset
channel t1: specifying datafile(s) in backupset
including current control file in backupset
channel t1: starting piece 1 at 20-NOV-07
channel t1: finished piece 1 at 20-NOV-07
piece handle=a5j1h22f_1_1 tag=TAG20071120T112606 comment=API Version 2.0,MMS Version 5.4.1.0
channel t1: backup set complete, elapsed time: 00:00:03
Finished backup at 20-NOV-07

Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=c-797705013-20071120-00 comment=API Version 2.0,MMS Version 5.4.1.0
Finished Control File and SPFILE Autobackup at 20-NOV-07
released channel: t1

We are safe now.

Advertisements

About Pang

Oracle DBA working in database, fusion middleware and identity management and cloud.
This entry was posted in Oracle database. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s