Re: ORA-00001: UNIQUE CONSTRAINT (RMAN_CTXP.BRL_U1) VIOLATED DURING A RESYNC.
- From: "Finn Jorgensen" <finn.oracledba@xxxxxxxxx>
- To: ecpdba97@xxxxxxxxx
- Date: Mon, 16 Jun 2008 19:42:15 -0500
Frank,
I haven't seen the particular error you're having, but why don't you
install another Oracle_home which is 10.2.0.4 next to the other one
and migrate your RMAN instance to this oracle_home? In that way your
standby's stay on their current version and you get your RMAN instance
patched. Seems like it would solve both problems.
Finn
On Mon, Jun 16, 2008 at 5:35 PM, Frank Pettinato <ecpdba97@xxxxxxxxx> wrote:
> Good day all.
>
>
> Has anyone seen anything like this before? I was running a normal hot backup
> to disk that I have been running for several months and suddenly my backup
> failed with this error during a resync. According to MetaLink and my support
> analyst I need to apply a patch (10.2.0.4) but I am afraid that this will
> cause problems with my Standby servers which run out of the same Oracle home
> and are on the same server.
>
> It seems pretty straight forward to me. If you check the RMAN catalog I see
> the BRL table and a unique constraint called BRL_U1 on DB_INCKEY, RECID and
> STAMP. I re-created the catalog and attempted the resync again, but it
> still will not work. Is my problem in the controlfile on the database that I
> am attempting to back up? Should I re-create that controlfile?
>
> Thanks much...
>
> Here is my info:
> Server(s) config 1 - Primary - Multi-node RAC Oracle 10.2.0.3 on Windows 64
> bit
> Server config 2 - Standby - Single (Non-RAC) Oracle 10.2.0.3 on Windows 64
> bit . RMAN recovery catalogs.
>
> Frank
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
