Rman Resync or Register of 18.104.22.168 target with Multiple Pbd's in Recovery Catalog To 12.2 Fails with ORA-20110: set stamp set count conflict
(Doc ID 2291791.1)
Last updated on MARCH 09, 2019
Applies to:Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
- 22.214.171.124 database with Multiple PDB's .
- DATABASE BP 126.96.36.199.161018 or Higher has been applied on 188.8.131.52
- Resync or Register database of target database 184.108.40.206 with Recovery Catalog of 12.2.0 Fails with Below error :-
Recovery Manager: Release 220.127.116.11.0 - Production on Thu Apr 20 11:22:57 2017
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
RMAN-06005: connected to target database: PROD (DBID=nnnnnnnnn)
RMAN-06008: connected to recovery catalog database
RMAN-06619: recovery catalog schema release 12.02.00.01. is newer than RMAN release
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-20110: set stamp set count conflict
DATABASE BP 18.104.22.168.161018 or Higher has been applied on 22.214.171.124 . After this Resync or Register of target database fails with 12.2 recovery catalog
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