Re: RMAN fails with ORA-00001: unique constraint (RMAN.DF_P) violated
Date: Wed, 04 Mar 2015 23:51:15 -0500
Message-ID: <54F7E0C3.4070509_at_yahoo.com>
Pavan, after searching MOS, here is what I came up with. All versions below 12.1 are believed to be affected. The conclusion is inevitable: the only cure is to upgrade to 12c.
Bug 10190398 - DF_U1 unique constraint violated error during RMAN resync (Doc ID 10190398.8) To BottomTo Bottom <https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=1286yeu2gs_9&_afrLoop=428332703853943#>
_Bug 10190398 DF_U1 unique constraint violated error during RMAN
resync_
This note gives a brief overview of bug 10190398.
The content was last updated on: 28-JUN-2013
/Click here
<https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=10190398.8&id=245840.1>
for details of each of the sections below./
_Affects:_
*Product (/Component/)* Oracle Server (Rdbms)
*Range of versions /believed/ to be affected* Versions BELOW 12.1
*Versions /confirmed/ as being affected*
*Platforms affected* Generic (all / most platforms affected)
_Fixed:_
On 03/04/2015 09:53 PM, pavan kumar wrote:
> Hi,
>
> 1. Can you able to find RMAN.DF_P constraints details from catalog db
> 2. Secondly, check/once again try why that record is failing, if it's
> too old record in catalog table, you may delete that record from
> catalog table/segment and re-try
>
> - Thanks
> Pavan kumar N
>
> ------------------------------------------------------------------------
> *From:* Rich <richa03_at_gmail.com>
> *To:* Oracle-L Freelists <oracle-l_at_freelists.org>
> *Sent:* Wednesday, 4 March 2015 9:18 PM
> *Subject:* RMAN fails with ORA-00001: unique constraint (RMAN.DF_P)
> violated
>
> Hi List,
> This is 11.1.0.7 on RHEL 5.1 (external application requirements).
>
> I don't know if this is related, however, this started with only
> incremental backups failing with:
> ORA-19643: datafile 6: incremental-start SCN is too recent
> ORA-19640: datafile checkpoint is SCN 656412919 time 02/27/2015 06:46:55
> (sometimes datafile 83 and different SCN numbers)
>
> Fulls were OK until just recently; they now fail with:
> ORA-00001: unique constraint (RMAN.DF_P) violated
>
> No changes to backup scripts which are fairly standard - the logfile
> and error stack (for a full) is:
> RMAN> run {
> 2> show all;
> 3> backup incremental level = 0 database plus archivelog
> delete input tag Full_DB_20150304_062126 ;
> 4> delete noprompt force obsolete ;
> 5> }
> starting full resync of recovery catalog
> RMAN-00571: ===========================================================
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
> RMAN-00571: ===========================================================
> RMAN-03002: failure of show command at 03/04/2015 06:21:31
> RMAN-03014: implicit resync of recovery catalog failed
> RMAN-03009: failure of full resync command on default channel at
> 03/04/2015 06:21:31
> ORA-00001: unique constraint (RMAN.DF_P) violated
>
> Google and MOS have been little to no help...did find Bug 9288598,
> however, this is not a standby and I don't think it ever was.
> Support is also "working" on this, however, not much there either
> (just sent them log files and a debug).
>
> We do see that these datafiles (6 & 83) as well as some others have
> UNRECOVERABLE_CHANGE# populated and UNRECOVERABLE_TIME with a date
> back in 2013. This looks to me like there was some NOLOGGING activity
> back then, but I don't think this should be an issue?
>
> Any ideas?
>
> Thanks,
> Rich
>
>
-- Mladen Gogala Oracle DBA http://mgogala.freehostia.com -- http://www.freelists.org/webpage/oracle-lReceived on Thu Mar 05 2015 - 05:51:15 CET