My Oracle Support Banner

RMAN>upgrade Catalog Failed with ORA-02292 (Doc ID 1303486.1)

Last updated on DECEMBER 02, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.1 [Release 10.2 to 11.2]
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Catalog schema:  RMAN

*****************

Upgrade Catalog schema to 11.2 failed with,

RMAN> upgrade catalog;

error creating remove_null_db_unique_name_rows_from_node
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06004: ORACLE error from recovery catalog database: ORA-02292: integrity constraint (RMAN.TSATT_F2) violated - child record found

Or,

error creating remove_null_db_unique_name_rows_from_node
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571:===========================================================
RMAN-6004: ORACLE error from recovery catalog database:
ORA-1: unique constraint (RMAN.SITE_TFATT_P) violated

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.