Re: RMAN Catalog Error
- From: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
- To: stephan uzzell <SUzzell@xxxxxxxxxx>
- Date: Wed, 2 Jul 2014 10:15:57 -0300
Have you tried to unregister the database and register it again? You will
lose some history, but it may resolve the resync issue.
As to the error ORA-20999: internal error: found non-null and null site
name, this is a custom error. So I would look at the catalog database and
see if there's any trigger there which can raise this error.
hth
Cheers
Alan.-
Alan.-
On Wed, Jul 2, 2014 at 9:48 AM, Uzzell, Stephan <SUzzell@xxxxxxxxxx> wrote:
> Hi folks, I’ve struck out searching for this, and wondering if anyone
> has any ideas. Pretty much all of our databases are running backups while
> connected to the catalog; all succeed except one. Several recent backups
> have failed with:
>
>
>
> RMAN-00571: ===========================================================
>
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
>
> RMAN-00571: ===========================================================
>
> RMAN-03002: failure of backup plus archivelog command at 07/01/2014
> 11:00:18
>
> RMAN-03014: implicit resync of recovery catalog failed
>
> RMAN-06004: ORACLE error from recovery catalog database: ORA-20999:
> internal error: found non-null and null site name
>
>
>
> This is 11.2.0.3.PSU7 on Linux x64; catalog is also 11.2.0.3.PSU7 on Linux
> x64.
>
>
>
> I’m thinking about taking a backup without connecting to the catalog, and
> then hoping I can resynch. I’m a little bothered by the “implicit resynch
> failed” error, though…
>
>
>
> Any thoughts?
>
>
>
> Thanks,
>
> stephan
>
>
>
> *Stephan Uzzell* | Senior Database Administrator | Managed Services
> |MICROS Systems, Inc.
> Direct: 443.285.8000x2345 | Mobile: 443.864.1725 | suzzell@xxxxxxxxxx |
> www.micros.com
>
>
>
Other related posts:
