Steve,

There is a step in upgrades that requires you upgrade the recovery catalog
after applying some patchs (not all patches require it).  It is always safe
to run the upgrade just to be safe.  :)

Connect to the target and catalog as normal via RMAN.  Once connected issue
"upgrade catalog;" twice (it is required to issue it twice to confirm the
upgrade request).

This will reinstall the recovery catalog packages and upgrade the catalog to
the correct version that supports the target.  The catalog can still run on
a lower level of oracle (for example: we have a 9.2 catalog in a 8.1.7.4
instance) but must be at least the level of the target instance.

Hope this helps!!  Good luck!

Mike Leary
Oracle DBA / Data Architect
Managed Security Services
TruSecure Corporation
678.728.1000
mleary AT trusecureonline DOT com
www.trusecure.com


-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Steven 
Jenner
Sent: Thursday, March 04, 2004 8:46 AM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] Failed Oracle backups

Hi, we have been performing hot Oracle backups on a customers server using
RMAN and Veritas and all has been well. Recently however our customer
upgraded their version of Oracle to 8.1.7.4 whereas the version of Oracle
that is running on the Veritas Recovery Catalogue server is 8.1.7.0.

Since the upgrade all hot backups have failed with the folowing entries
being written to the bphdb log

RMAN-06008: connected to recovery catalog database

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: t1
RMAN-08500: channel t1: sid=10 devtype=SBT_TAPE
RMAN-08526: channel t1: VERITAS NetBackup for Oracle8 - Release 3.4GA
(030800)

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: t2
RMAN-08500: channel t2: sid=38 devtype=SBT_TAPE
RMAN-08526: channel t2: VERITAS NetBackup for Oracle8 - Release 3.4GA
(030800)

RMAN-03022: compiling command: backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06004: ORACLE error from recovery catalog database: ORA-06550: line 1,
column 21:
PLS-00302: component 'LOCKFORCKPT' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
RMAN-06097: text of failing SQL statement: begin dbms_rcvcat . lockForckpt ;
end ;
RMAN-06099: error occurred in source file: krmk.pc, line: 2121

Recovery Manager complete.

I believe that this all points to a compatibility issue with the two Oracle
differing versions and am hoping that someone out there can confirm this??

Hope you can help.

 

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

***********************************************************************
This message is intended only for the use of the intended recipient and
may contain information that is PRIVILEGED and/or CONFIDENTIAL.  If you
are not the intended recipient, you are hereby notified that any use,
dissemination, disclosure or copying of this communication is strictly
prohibited.  If you have received this communication in error, please
destroy all copies of this message and its attachments and notify us
immediately.
***********************************************************************