RMAN-03014: implicit resync of recovery catalog failed

I got ” RMAN-03014: implicit resync of recovery catalog failed ”  error in Oracle database.

RMAN-03014: implicit resync of recovery catalog failed

Details of error are as follows.

RMAN-03014: implicit resync of recovery catalog failed

Cause: of the failure.

Action: No action is required.

RMAN backup is failing with RMAN-03014: implicit resync of recovery catalog failed 

RMAN-20110: set_stamp set_count conflict

$ rman target / CATALOG=<user>/<password>@<catalog_tnsname>

Recovery Manager: Release 12.2.0.1.0 - Production on Mon Sep 24 09:03:15 2018

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

connected to target database: <db_name> (DBID=25012363860)
connected to recovery catalog database

RMAN> run
{
EXECUTE GLOBAL SCRIPT 'DB_backupset_ARC';
}
2> 3> 4>
executing global script: DB_backupset_ARC

starting full resync of recovery catalog                                          <<<<<
uncatalog BACKUPPIECE db_gitcn71p_1_2 in NOCATALOG mode              <<<<<<<
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script DB_backupset_ARC
RMAN-03002: failure of sql command at 09/24/2018 09:06:44
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 09/24/2018 09:06:44
RMAN-20110: set_stamp set_count conflict               <<<<<<<<<<

RMAN>

implicit resync of recovery catalog failed

This RMAN-03014 error is related to the Two different backupsets conflicted with their set_stamp and set_count.

To solve this error, connect catalog database and run the unregister and register database again.

connect catalog user/pwd@CATALOG_DB
connect target /

RMAN> unregister database;
RMAN> register database;

OR

Second case is as follows.

Both backupset had same set_stamp and set_count

or

– Resync error when fuzzy backup generated at backup.

The RMAN Debug trace output shows as below:

DBGRESYNC: channel default: Calling checkBackupDataFile for set_stamp 986422329 set_count 221714 [10:26:48.872] (resync)  <<< set_stamp and set_count
DBGRESYNC: channel default: file# 1119 recid 683532 [10:26:48.872] (resync)
DBGRPC: krmxrpc - channel default kpurpc2 err=20110 db=rcvcat proc=RMAN.DBMS_RCVCAT.CHECKBACKUPDATAFILE excl: 144 <<<<<<<
DBGRCVCAT: checkBackupDataFile - locked bs_key13930437
DBGRCVCAT: addBackupDataFile - bs_key 13930437 file# 1119
DBGRCVCAT: addBackupDatafile set stamp set count conflict - bs_key 13930437 bdf_key 14932719 dbinc_key 398174 file# 1119 bdf_recid 683532 bdf_stamp 986424804 ckp_scn 14930781223030 ckp_time 09-SEP-18 datafile_blocks 898326528 block_size 8192 plugin_scn 0 section_size 0 <<<<<<
DBGRPC: krmxrpc - channel default kpurpc2 err=0 db=rcvcat proc=RMAN.DBMS_RCVCAT.CANCELCKPT excl: 0
DBGRCVCAT: cancelCkpt - rollback, release locks
DBGRPC: krmxrpc - channel default kpurpc2 err=0 db=target proc=SYS.DBMS_BACKUP_RESTORE.CFILEUSECURRENT excl: 0
DBGMISC: ENTERED krmzlog [10:26:50.523]
RMAN-08192: uncatalog BACKUPPIECE db_gitcn71p_1_2 in NOCATALOG mode <<<<<<

OR it may show output as below:

DBGRESYNC: channel default: Calling checkBackupRedoLog for set_stamp 1048402308 set_count 10725 recid 206657 [14:35:40.998] (resync)
DBGRESYNC: channel default: sequence 34078 first change 52958919311 next change 52958989119 [14:35:40.998] (resync)
DBGRPC: krmxrpc - channel default kpurpc2 err=20110 db=rcvcat proc=RMANCAT.DBMS_RCVCAT.CHECKBACKUPREDOLOG excl: 87
DBGRCVCAT: checkBackupRedoLog - locked bs_key178041640
DBGRCVCAT: checkIncarnation - returning 178031149
DBGRCVCAT: checkBackupRedoLog set stamp set count conflict - bs_key 178041640 brl_key 184531191 dbinc_key 178031149 brl_recid 206657 brl_stamp 1055435457 thread# 2 sequence# 34078 blocks 311842 block_size 512
DBGRPC: krmxrpc - channel default kpurpc2 err=0 db=rcvcat proc=RMANCAT.DBMS_RCVCAT.CANCELCKPT excl: 0
DBGRCVCAT: cancelCkpt - rollback, release locks
DBGMISC: ENTERED krmzlog [14:35:42.607]
RMAN-08192: uncatalog BACKUPPIECE /oracle_sdz_prod/rman/CALIFPCD/2020/08/14/CALIFPCD_f5v7qmc4_1_1_ARCH_bkup in NOCATALOG mode

1) Use below query to find the backup piece information from target database

select device_type, handle from v$backup_piece where set_stamp=&set_stamp and set_count=&set_count;

In the above example : set_stamp 986422329 & set_count 221714

2) Connect to target database and uncatalog the backup piece from controlfile

$ export NLS_DATE_FORMAT='DD-MON-YYYY HH24:MI:SS'
$ rman target /
RMAN> set echo on ;
RMAN> list backuppiece 'db_gitcn71p_1_2';
RMAN> change backuppiece 'db_gitcn71p_1_2' uncatalog;
RMAN> exit

3) Execute resync catalog

$ rman target / CATALOG=<user>/<password>@<catalog_tnsname>
RMAN> resync catalog;

4) Re-catalog removed backup piece

$ rman target / CATALOG=<user>/<password>@<catalog_tnsname>
RMAN> catalog device type 'SBT_TAPE' backuppiece 'db_gitcn71p_1_2';

Do you want to learn Oracle Database for Beginners, then read the following articles.

Oracle Tutorial | Oracle Database Tutorials for Beginners ( Junior Oracle DBA )