cancel
Showing results for 
Search instead for 
Did you mean: 

RMAN-03002: failure of catalog comma

Former Member
0 Kudos

We are using Tivoli with BRTOOLS and no RMAN at all..not sure why at the end of Backup its executing "'SHELL=/bin/sh /oracle/QAS/102_64/bin/rman nocatalog'" command and gives the following errors.

BR0530I Cataloging backups of all database files...

BR0278E Command output of 'SHELL=/bin/sh /oracle/QAS/102_64/bin/rman nocatalog':

Recovery Manager: Release 10.2.0.2.0 - Production on Fri Oct 8 01:23:12 2010

Copyright (c) 1982, 2005, Oracle. All rights reserved.

RMAN>

RMAN> connect target *

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-04002: ocipi failed, ORA 1

RMAN> *end-of-file*

RMAN>

host command complete

RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30>

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of catalog command at 10/08/2010 01:23:15

RMAN-06171: not connected to target database

RMAN>

Recovery Manager complete.

BR0280I BRBACKUP time stamp: 2010-10-08 01.23.15

BR0279E Return code from 'SHELL=/bin/sh /oracle/QAS/102_64/bin/rman nocatalog': 1

BR0536E RMAN call for database instance QAS failed

BR0280I BRBACKUP time stamp: 2010-10-08 01.23.15

BR0532E Cataloging backups of all database files failed

BR0280I BRBACKUP time stamp: 2010-10-08 01.23.40

BR0317I 'Alter database end backup' successful

BR0056I End of database backup: beehfpbh.fnf 2010-10-08 01.23.15

BR0280I BRBACKUP time stamp: 2010-10-08 01.23.41

This is not happening on our DEV but only on QAS environment.

Will appreciate your help.

Laxmichand

Accepted Solutions (0)

Answers (2)

Answers (2)

stefan_koehler
Active Contributor
0 Kudos

Hello Laxmichand,

and to get the RMAN error fixed - you need to relink your rman binaries.


shell> su - ora<SID>
shell> cd $ORACLE_HOME/rdbms/lib
shell> make -f ins_rdbms.mk irman

Regards

Stefan

Former Member
0 Kudos

Hi Stefan,

we are having exactly the same Problem but we are running Windows 2003 with Oracle 10.2

How can I solve the RMAN Problem on Windows?

volker_borowski2
Active Contributor
0 Kudos

Hi,

you are doing a "full" backup.

This implies the successfull backup being cataloged, no matter how it had been taken.

You can do a full backup to disk / tape / util_file (as in your case) or with rman.

In the first cases the backups are done in any way and in the end you can calatog

them as a level 0 backup, which is where rman comes in.

Very usefull, if you like to start using incremental backups, but have no trust in rman yet

If you do not like to catalog it, you need to do a "whole" (DB13) or "-m all" (direct call) backup.

You protocols wil get *.anf instead of *.fnf extension.

Hope this helps

Volker