My Oracle Support Banner

RMAN Resync of Recovery Catalog Fails with - RMAN-03014 and RMAN-20110: Set_stamp Set_Count Conflict (Doc ID 2453569.1)

Last updated on MAY 21, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.

Symptoms

 Backup 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>

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.