RE: RMAN repository error - ORA-02290 on RT_C_STATUS

From: Jorgensen, Finn <Finn.Jorgensen_at_constellation.com>
Date: Wed, 8 Jun 2011 13:27:44 -0400
Message-ID: <9CE162BC5ED2C643956B526A7EDE46FF02445527DBE1_at_EXM-OMF-04.Ceg.Corp.Net>

That constraint in my 11.2 repository database checks for D, E, O and I so something has gone wrong in your upgrade. That's probably why Oracle suggested you rerun it.

Thanks,
Finn

-----Original Message-----
From: Lou Avrami [mailto:avramil_at_concentric.net] Sent: Wednesday, June 08, 2011 1:03 PM
To: Jorgensen, Finn; 'Mercadante, Thomas F (LABOR)'; 'oracle-l_at_freelists.org' Subject: RE: RMAN repository error - ORA-02290 on RT_C_STATUS

By "Both databases" I meant that the repository was also 11.2.

• Jorgensen, Finn <Finn.Jorgensen_at_constellation.com> wrote:
  >
  > Why would you not just upgrade your repository to 11.2? I have tons of databases between version 9.2.0.2 and 11.2.0.2 all using a 11.2.0.2 repository.
  >
  > Thanks,
  > Finn
  >
  >
  > -----Original Message-----
  > From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Lou Avrami
  > Sent: Tuesday, June 07, 2011 4:26 PM
  > To: Mercadante, Thomas F (LABOR); oracle-l_at_freelists.org
  > Subject: RE: RMAN repository error - ORA-02290 on RT_C_STATUS
  >
  >
  > Hey Tom,
  >
  > Both of the database involved here are 11.2.
  > The constraint RT_C_STATUS is checking for the values of 'D','E','O' for STATUS, the same as for 9.2.
  >
  > The logical assumption would be that something is trying to insert an record with an invalid value ... but I have no explanation why this is occurring. We've run a couple of weeks of backups on the particular target database and not encountered issues until now.
  >
  > "Kosher", indeed. :-)
  >
  > Lou
  >
  > > ---- Mercadante, Thomas F (LABOR) <Thomas.Mercadante_at_labor.ny.gov> wrote:
  > > >
  > > > Lou,
  > > >
  > > > 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.
  > > >
  > > > Tom
  > > >
  > > > -----Original Message-----
  > > > From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Lou Avrami
  > > > Sent: Tuesday, June 07, 2011 3:19 PM
  > > > To: oracle-l_at_freelists.org
  > > > 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.
  > > >
  > > > Thanks,
  > > > Lou Avrami
  > > >
  > > > --
  > > > http://www.freelists.org/webpage/oracle-l
  > > >
  > > >
  > > >
  > > >
  > >
  > --
  > http://www.freelists.org/webpage/oracle-l
  >
  >
  > >>> This e-mail and any attachments are confidential, may contain legal,
  > professional or other privileged information, and are intended solely for the
  > addressee. If you are not the intended recipient, do not use the information
  > in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2
  >
  †Ûiÿü0ÁúÞzX¬¶Ê+ƒün– {ú+iÉ^

Received on Wed Jun 08 2011 - 12:27:44 CDT