RE: RMAN repository error - ORA-02290 on RT_C_STATUS

From: Mercadante, Thomas F (LABOR) <"Mercadante,>
Date: Tue, 7 Jun 2011 15:33:59 -0400
Message-ID: <AD4532B304E00C4F9AEFA0D338DF7DD10118FD3489_at_excnysm95banp.nysemail.nyenet>


I have a 9.2 and 10.2 Rman repositories here.

The check constraint you mention exists in the 9.2 repos and it's restrictions are the STATUS column has to have values of ('D','E','O').

The 10.2 repository does not have the check constraint but has a differently named one (RT_C1_STATUS) with valid values of ('D','E','O','I').

So I'm wondering if the specific database that is having this issue is maybe a 10.2 database using a 9.2 repository attempting to store a value of 'I' in the STATUS column.

Just sayin. I can think of several ways to fix this. They may not kosher.

But that's just me.


-----Original Message-----

From: [] On Behalf Of Lou Avrami Sent: Tuesday, June 07, 2011 3:19 PM
Subject: RMAN repository error - ORA-02290 on RT_C_STATUS

Hi there Oracle-L,

We're getting interesting errors when trying to run RMAN backups against a particular database, involving the repository table RT and the RT_C_STATUS check constraint:

RMAN-03002: failure of allocate command at 06/06/2011 14:12:31
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 06/06/2011 14:12:31
ORA-02290: check constraint (RMANCAT.RT_C_STATUS) violated

This error occurs consistently for just one out of about 100 databases in this RMAN repository database.

Oracle Support suggested running the UPGRADE REPOSITORY comamnd, but that doesn't seem to have worked.

Has anyone encountered previously encountered this problem? Any ideas or suggestions would be appreciated.

Lou Avrami


i0zX+n{+i^ Received on Tue Jun 07 2011 - 14:33:59 CDT

Original text of this message