My Oracle Support Banner

RMAN: RESYNC CATALOG on PHYSICAL STANDBY database failing RMAN-20999: internal error (Doc ID 2240323.1)

Last updated on DECEMBER 30, 2022

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.


RESYNC on the PHYSICAL STANDBY fails with error

RMAN-01005: starting partial resync of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of resync command on default channel at 02/21/2017 14:10:36
RMAN-20999: internal error

The issue can be reproduced at will with the following steps:

RMAN> resync catalog;


The backups has been always taken on PRIMARY Database
This is the first backup on STANDBY.


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

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