You may face RMAN-20035: invalid high RECID after connecting to catalog database.
executing command: SET COMMAND ID
starting full resync of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 07/27/2016 10:54:19
RMAN-03014: implicit resync of recovery catalog failed
on default channel at 07/27/2016 10:54:19
RMAN-20035: invalid high RECID
Solution:
Unregister the database and register again .
$ rman Recovery Manager: Release 12.1.0.2.0 - Production on Fri Sep 16 11:10:19 2016 Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved. RMAN> connect target sys/oracle@TESTDB connected to target database: TESTDB(DBID=3098444898) RMAN> connect catalog RMAN_db/rman@CATLOGDB connected to recovery catalog database RMAN> unregister database; database name is "BSSPRDM" and DBID is 1302028423 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
Now run rman command, it will work:
RMAN> backup archivelog all delete input executing command: SET COMMAND ID allocated channel: t1 channel t1: SID=1455 instance=BSSPRDM1 device type=SBT_TAPE channel t1: NMDA Oracle v8.2.2 allocated channel: t2 channel t2: SID=394 instance=BSSPRDM1 device type=SBT_TAPE channel t2: NMDA Oracle v8.2.2 sql statement: alter database backup controlfile to trace specification does not match any archived log in the repository starting full resync of recovery catalog full resync complete Starting backup at 27-JUL-16 current log archived channel t1: starting archived log backup set channel t1: specifying archived log(s) in backup set input archived log thread=1 sequence=7492 RECID=10274 STAMP=918315965 channel t1: starting piece 1 at 27-JUL-16 channel t2: starting archived log backup set channel t2: specifying archived log(s) in backup set input archived log thread=2 sequence=2782 RECID=10273 STAMP=918315961 channel t2: starting piece 1 at 27-JUL-16 channel t2: finished piece 1 at 27-JUL-16 piece handle=RMAN_BSSPRDM_arc_f_20160727_28601_tprbootu_1_1.bak tag=TAG20160727T154606 comment=API Version 2.0,MMS Version 8.2.2.0 channel t2: backup set complete, elapsed time: 00:00:45 channel t1: finished piece 1 at 27-JUL-16 piece handle=RMAN_BSSPRDM_arc_f_20160727_28600_torbootu_1_1.bak tag=TAG20160727T154606 comment=API Version 2.0,MMS Version 8.2.2.0 channel t1: backup set complete, elapsed time: 00:00:55 Finished backup at 27-JUL-16
SEE ALSO:
rman-07539-insufficient-privileges-to-create-or-upgrade-the-catalog-schema
rman-06428-recovery-catalog-is-not-installed
rman-dbms_rcvcat-version-11-02-00-03-in-rcvcat-database-is-too-old
