I faced in my costumer environment, the issue RMAN-20110, during primary RMAN backup execution. This environment has a primary and data guard databases.
To simulate the issue before fix it, simple execute a resync catalog:
rman target / catalog /@zdlra01
RMAN> resync catalog;
resync catalog;
starting full resync of recovery catalog
uncatalog BACKUPPIECE c-1234567890-0987654321-0a in NOCATALOG mode
RMAN Command Id : 2025-01-31T08:53:00
RMAN Command Id : 2025-01-31T08:53:00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of resync command on default channel at 01/31/2025 08:53:12
RMAN-20110: set_stamp set_count conflict
No backup for that specific database, will execute until you fix it, so, this is a critical issue. To fix the error you need to uncatalog the backup piece. Let’s see how to do that.
First, connect without catalog and list the backup piece:
[oracle@oraserver ~]$ export NLS_DATE_FORMAT='DD-MON-YYYY HH24:MI:SS'
[oracle@oraserver ~]$ rman target /
Recovery Manager: Release 19.0.0.0.0 - Production on Fri Jan 31 09:18:18 2025
Version 19.25.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1234567890)
RMAN> set echo on ;
RMAN> echo set on
RMAN> list backuppiece 'c-1234567890-0987654321-0a';
list backuppiece 'c-1234567890-0987654321-0a';
using target database control file instead of recovery catalog
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
912434 912434 1 1 AVAILABLE SBT_TAPE c-1234567890-0987654321-0a
Now, we need to uncatalog the backup piece. In the same session connected without catalog, execute the command below:
RMAN> change backuppiece 'c-1234567890-0987654321-0a' uncatalog;
change backuppiece 'c-1234567890-0987654321-0a' uncatalog;
uncataloged backup piece
backup piece handle=c-1234567890-0987654321-0a RECID=912434 STAMP=1191779835
Uncataloged 1 objects
Let’s see if it worked.
[oracle@oraserver ~]$ rman target / catalog /@zdlra01
Recovery Manager: Release 19.0.0.0.0 - Production on Fri Jan 31 09:20:32 2025
Version 19.25.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1234567890)
connected to recovery catalog database
recovery catalog schema version 23.04.00.23. is newer than RMAN version
RMAN> resync catalog;
resync catalog;
starting full resync of recovery catalog
full resync complete
Oracle suggests to catalog the backup again, but for me, the problem returned. If you want to try to catalog the backup again, execute the command below:
[oracle@oraserver ~]$ rman target / catalog /@zdlra01
Recovery Manager: Release 19.0.0.0.0 - Production on Fri Jan 31 09:20:32 2025
Version 19.25.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1234567890)
connected to recovery catalog database
recovery catalog schema version 23.04.00.23. is newer than RMAN version
RMAN> catalog device type 'SBT_TAPE' backuppiece 'c-1234567890-0987654321-0a';
Test resync catalog again:
[oracle@oraserver ~]$ rman target / catalog /@zdlra01
Recovery Manager: Release 19.0.0.0.0 - Production on Fri Jan 31 09:20:32 2025
Version 19.25.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1234567890)
connected to recovery catalog database
recovery catalog schema version 23.04.00.23. is newer than RMAN version
RMAN> resync catalog;
resync catalog;
starting full resync of recovery catalog
full resync complete
If work for you, finished here, but if not, you will need to uncatalog the backup again and I suggest executing a backup level 1 or if possible, a level 0, just to stay safe.
[oracle@oraserver ~]$ rman target / catalog /@zdlra01
Recovery Manager: Release 19.0.0.0.0 - Production on Fri Jan 31 09:20:32 2025
Version 19.25.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1234567890)
connected to recovery catalog database
recovery catalog schema version 23.04.00.23. is newer than RMAN version
RMAN> backup incremental level 1 cumulative device type sbt filesperset=1 section size 64G database plus archivelog filesperset=32;
Oracle RMAN development team found a bug related that and one reason for this issue is, if you have primary and standby executing backups in the same time, for example, backup RMAN level 1 executing at 10AM in both databases.
Try to reschedule it with 1h of difference.
My Piece of Data 