- 01 Dec, 2023
- 0 Comments
- 1 Min Read
RMAN-20035: Invalid High RECID In Rman Catalog
You can get this error 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/2023 10:54:19
RMAN-03014: implicit resync of recovery catalog failed
on default channel at 07/27/2023 10:54:19
RMAN-20035: invalid high RECID
Solution :
Unregister the database and register again .
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 | $ rmanRecovery Manager: Release 12.1.0.2.0 - Production on Fri Sep 23 11:10:19 2023Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.RMAN> connect target sys/oracle@TESTDBconnected to target database: TESTDB(DBID=3098444898)RMAN> connect catalog RMAN_db/rman@CATLOGDBconnected to recovery catalog databaseRMAN> unregister database;database name is "BSSPRDM" and DBID is 1302028423Do you really want to unregister the database (enter YES or NO)? YESdatabase unregistered from the recovery catalogRMAN> register database;database registered in recovery catalogstarting full resync of recovery catalogfull resync completeNow run rman command, it will work:RMAN> backup archivelog all delete inputexecuting command: SET COMMAND IDallocated channel: t1channel t1: SID=1455 instance=BSSPRDM1 device type=SBT_TAPEchannel t1: NMDA Oracle v8.2.2allocated channel: t2channel t2: SID=394 instance=BSSPRDM1 device type=SBT_TAPEchannel t2: NMDA Oracle v8.2.2sql statement: alter database backup controlfile to tracespecification does not match any archived log in the repositorystarting full resync of recovery catalogfull resync completeStarting backup at 27-JUL-23current log archivedchannel t1: starting archived log backup setchannel t1: specifying archived log(s) in backup setinput archived log thread=1 sequence=7492 RECID=10274 STAMP=918315965channel t1: starting piece 1 at 27-JUL-23channel t2: starting archived log backup setchannel t2: specifying archived log(s) in backup setinput archived log thread=2 sequence=2782 RECID=10273 STAMP=918315961channel t2: starting piece 1 at 27-JUL-23channel t2: finished piece 1 at 27-JUL-23piece handle=RMAN_BSSPRDM_arc_f_20230727_28601_tprbootu_1_1.bak tag=TAG20230727T154606 comment=API Version 2.0,MMS Version 8.2.2.0channel t2: backup set complete, elapsed time: 00:00:45channel t1: finished piece 1 at 27-JUL-23piece handle=RMAN_BSSPRDM_arc_f_20230727_28600_torbootu_1_1.bak tag=TAG20230727T154606 comment=API Version 2.0,MMS Version 8.2.2.0channel t1: backup set complete, elapsed time: 00:00:55Finished backup at 27-JUL- 23 |