My Oracle Support Banner

Rman Backup On Physical Standby Database Failing with RMAN-20079 after Structure Changes on Primary (Doc ID 1326706.1)

Last updated on DECEMBER 14, 2017

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.
***Checked for relevance on 24-Jun-2013***


RMAN catalog is used to backup the database on Standby Database side.

New tablespace was added on the Primary Database side.

No RMAN backup or connection made on the Primary Database

RMAN backup on standby database failing with errors after adding new tablespace on primary.

RMAN backup failing with:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 05/17/2011 10:55:28
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel at 05/17/2011 10:55:28
RMAN-20079: full resync from primary database is not done


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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.