RMAN catalog errors

Oracle 10.2.0.4 running in archivelog
connect rman using same database as catalog and target. Trying to backup the catalog. Not sure why I received the first error - database incarnation not set (the only change I made was to enable archiving on the db). The second error I have not encountered with RMAN. Please help.
RMAN> backup database plus archivelog
2> format '/a0221/d01/arch1/ufms609/%U';
Starting backup at 15-MAR-10
current log archived
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 03/15/2010 09:33:56
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20020: database incarnation not set
RMAN> reset database;
database incarnation already registered
RMAN> unregister database;
database name is "UFMS609" and DBID is 706395303
Do you really want to unregister the database (enter YES or NO)? yes
database unregistered from the recovery catalog
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-02291: integrity constraint (RMAN.RLH_F1) violated - parent key not found

Please disregard this post. After I posted I exited rman and reinitialized - somehow this cleared whatever problems rman didnt like before.

Similar Messages

Rman catalog error

Hi all,
when i'm trying to register a database in recovery catalog i'm getting the following error.
register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-02291: integrity constraint (RMAN.RLH_F1) violated - parent key not found

Have a look at the thread and see if it would help you unregister it properly. It has works for various related errors
Grid Control and Rman Catalog

RMAN-06010: error while looking up datafile: 82

Iam building dataguard - Physical Standby database by using the RMAN duplicate command and we are not using the recovery catalog but control file.
Iam getting the following error while running the duplicate command.
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";
RMAN-06010: error while looking up datafile: 82
Actually we dropped the datafile(tablespace) before taken the backup but it is giving error though we are using the latest control file.
I do not see this file is available in the database as we dropped it successfully.
Could some one let me know what could be the problem and how to resolve it.
Your early response is greatly appreciated.
Note:
backup script -- It went successfully.
# Script to be used to backup the production in preparation of creating a DataGuard instance
YYYY=`date +"%Y"`
mmdd=`date +"%m%d"`
hh=`date +"%H"`
mm=`date +"%M"`
ss=`date +"%S"`
hhmmss=${hh}${mm}${ss}
dt=${YYYY}${mmdd}_${hhmmss}
echo "Starting backup on O01FLX3"
$ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/full_backup_run_$dt.log
connect target /
configure device type disk clear;
configure channel device type disk maxpiecesize 4G;
configure device type disk backup type to compressed backupset parallelism 8;
run{
change archivelog all validate;
backup current controlfile for standby format '/tmp/stby_snapcf_O01FLX3.f';
backup database format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.bak';
sql 'alter system archive log current';
backup archivelog all format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.arc';
EXIT
EOF
duplicate Script:
#!/bin/ksh
# Script to create standby database for production.
YYYY=`date +"%Y"`
mmdd=`date +"%m%d"`
hh=`date +"%H"`
mm=`date +"%M"`
ss=`date +"%S"`
hhmmss=${hh}${mm}${ss}
dt=${YYYY}${mmdd}_${hhmmss}
echo "Starting dataguard instance on O01FLX3DR"
$ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/cr_stdby_O01FLX3$dt.log
connect target /
connect auxiliary sys/xxxxxx@O01FLX3DR
configure channel device type disk maxpiecesize 4G;
configure device type disk backup type to compressed backupset parallelism 8;
run {
set until time "to_date('20080217:19:00', 'YYYYMMDD:HH24:MI')";
duplicate target database for standby dorecover nofilenamecheck;
exit;
EOF
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";

Thank you for your reply. Actually Iam not renaming the datafile but building the
dataguard instance and some how control file is looking for old datafile that was deleted.
Actually both primary and dataguard instances are running on 10.2.0.3 . Oracle control file is listing the datafile 82 as old deleted file, while building the dataguard.
---- This file was deleted long time back but still oracle control file is looking for this file while building the dataguard. Iam using the latest control file.
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3"
When I listed the datafile 82, it is showing the correct datafile.
RMAN> list backup of datafile 82;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
50234 Incr 2 26.93M DISK 00:04:03 18-FEB-08
BP Key: 101470 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51757_1_20080218_647031779.bak
List of Datafiles in backup set 50234
File LV Type Ckp SCN Ckp Time Name
82 2 Incr 7953177017970 18-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
BS Key Type LV Size Device Type Elapsed Time Completion Time
50334 Incr 2 27.76M DISK 00:04:16 19-FEB-08
BP Key: 101587 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51857_1_20080219_647119328.bak
List of Datafiles in backup set 50334
File LV Type Ckp SCN Ckp Time Name
82 2 Incr 7953257549488 19-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
So Iam thinking that there should be a problem in control file and let me know how to resolve it.
Please let me know if you have any questions.
Thanks for your help.
Suresh.D

Restore spfile from rman backup ---- error.

Hi,
I am trying to execute recovery on new machine ...
I have done the following steps..
I have one database as ora10g2 as peroduction database on one machine as hosta
I have created a catalog on another machine cora10g2 (hostb)
I have taken a full backup from hosta as per following ...
the following command execute from hosta machine.
$ rman target sys/<passwd>@ora10g2 catalog rman/rman@cora10g2 ...
Backup completed ...
Now I am trying to restore this backup on hostb machine where i have already rman catlog database ..
I have done the following setting ...on host b
set oracle_sid=DUP
and execute following command ...
rman target / catalog rman/rman@cora10g2
RMAN> set dbid 2760732370
executing command: SET DBID
database name is "BAAN10G2" and DBID is 2760732370
RMAN>
RMAN>
RMAN> startup force nomount ;
startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/oracle/dbs/baan10g2/dbs/initbaan10g2.ora'
starting Oracle instance without parameter file for retrival of spfile
Oracle instance started
Total System Global Area 159383552 bytes
Fixed Size 1977112 bytes
Variable Size 67114216 bytes
Database Buffers 83886080 bytes
Redo Buffers 6406144 bytes
RMAN>
RMAN>
RMAN>
RMAN> show all ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/backup/control/cntrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/baanora3/rman/ora10g2/bkup_db_%d_s%s_P%p_t%t' MAXPIECESIZE 1024;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
RMAN>
RMAN>
RMAN> list backup of spfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
2420 Full 7.33M DISK 00:00:01 14-JUN-07
BP Key: 2426 Status: AVAILABLE Compressed: NO Tag: TAG20070614T182935
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070614-00
SPFILE Included: Modification time: 14-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2509 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2515 Status: AVAILABLE Compressed: NO Tag: TAG20070615T130416
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-00
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2694 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2739 Status: AVAILABLE Compressed: NO Tag: TAG20070615T131703
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-01
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2760 Full 80.00K DISK 00:00:01 15-JUN-07
BP Key: 2763 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163437
Piece Name: /rman/spfile/spfile.ora
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2769 Full 7.33M DISK 00:00:02 15-JUN-07
BP Key: 2771 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163441
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-02
SPFILE Included: Modification time: 15-JUN-07
RMAN>
RMAN>
RMAN> restore spfile from autobackup ;
Starting restore at 19-JUN-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=36 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=35 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=34 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=33 devtype=DISK
channel ORA_DISK_1: looking for autobackup on day: 20070619
channel ORA_DISK_1: looking for autobackup on day: 20070618
channel ORA_DISK_1: looking for autobackup on day: 20070617
channel ORA_DISK_1: looking for autobackup on day: 20070616
channel ORA_DISK_1: looking for autobackup on day: 20070615
channel ORA_DISK_1: looking for autobackup on day: 20070614
channel ORA_DISK_1: looking for autobackup on day: 20070613
channel ORA_DISK_1: no autobackup in 7 days found
channel ORA_DISK_2: looking for autobackup on day: 20070619
channel ORA_DISK_2: looking for autobackup on day: 20070618
channel ORA_DISK_2: looking for autobackup on day: 20070617
channel ORA_DISK_2: looking for autobackup on day: 20070616
channel ORA_DISK_2: looking for autobackup on day: 20070615
channel ORA_DISK_2: looking for autobackup on day: 20070614
channel ORA_DISK_2: looking for autobackup on day: 20070613
channel ORA_DISK_2: no autobackup in 7 days found
channel ORA_DISK_3: looking for autobackup on day: 20070619
channel ORA_DISK_3: looking for autobackup on day: 20070618
channel ORA_DISK_3: looking for autobackup on day: 20070617
channel ORA_DISK_3: looking for autobackup on day: 20070616
channel ORA_DISK_3: looking for autobackup on day: 20070615
channel ORA_DISK_3: looking for autobackup on day: 20070614
channel ORA_DISK_3: looking for autobackup on day: 20070613
channel ORA_DISK_3: no autobackup in 7 days found
channel ORA_DISK_4: looking for autobackup on day: 20070619
channel ORA_DISK_4: looking for autobackup on day: 20070618
channel ORA_DISK_4: looking for autobackup on day: 20070617
channel ORA_DISK_4: looking for autobackup on day: 20070616
channel ORA_DISK_4: looking for autobackup on day: 20070615
channel ORA_DISK_4: looking for autobackup on day: 20070614
channel ORA_DISK_4: looking for autobackup on day: 20070613
channel ORA_DISK_4: no autobackup in 7 days found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/19/2007 18:00:13
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
RMAN>
I am not able to restore spfile from rman backup ;;;

Hi,
I would like to know few things
1. How are you setting the db_name ? you can set db_id at RMAN, how are you setting the db_name ?
2. Do you have any default init file at default location ? if yes, is the db_name parameter set correctly in that file ?
Since spfile is yet to be restored, you must set the db_name parameter correctly before you start spfile restore.This can be done with init file at default location which can even contain just one paremeter i.e db_name.

RMAN Backup error:ORA-04030: out of process memory

Hi,
Our RMAN backup is failing with below error:
===========================
RMAN-03002: failure of backup plus archivelog command at 05/22/2010 05:31:33
ORA-04030: out of process memory when trying to allocate 82444 bytes (pga heap,control file i/o buffer)
=============================
Please suggest
Thanks and Regards

We upgrade our catalog database(Linux) to 10.2.0.4 and our target database is 10.2.0.3(Windows),
we executed upgrade catalog twice and then when we again tried to execute the below command
rman sys/syspwd@targetdb catalog rman/rman@rmancat
Recovery Manager: Release 10.2.0.4.0 - Production on Sat May 22 15:10:36 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.03 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.03 in TARGET database is not current
connected to target database: WEBCT (DBID=3699379059)
connected to recovery catalog database
RMAN>
=======================
Still we are getting this error
and our backup falied with below errors:
======================
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.03 in TARGET database is not current PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.03 in TARGET database is not current connected to target database: WEBCT (DBID=3699379059) connected to recovery catalog database
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/22/2010 15:09:44
ORA-06550: line 1, column 14:
PLS-00306: wrong number or types of arguments in call to 'VALIDATEARCHIVEDLOG'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
==========================
Please suggest

RMAN script errors out for some DB's

I have a single RMAN script that uses env variables to execute RMAN for two databases. It runs fine. I cloned the two DB's (changed DBID's), all four are on the same host. Now I try to use same script for all four. I receive an error when trying to run against the cloned databases. Here is script:
spool log to full.log append;
connect catalog rman/xxxxxx@iasrman
connect target /
run {
sql 'ALTER SYSTEM SWITCH LOGFILE';
backup incremental level 0 database diskratio=0 plus archivelog delete input;
And here is error, it stops same place everytime, input appreciated.
Recovery Manager: Release 9.2.0.5.0 - 64bit Production
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: PRSMQ02 (DBID=944525168)
RMAN> 2> 3> 4>
sql statement: ALTER SYSTEM SWITCH LOGFILE
Starting backup at 30-MAY-07
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=20 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=19 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=18 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=17 devtype=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=25 recid=25 stamp=623931644
channel ORA_DISK_1: starting piece 1 at 30-MAY-07
channel ORA_DISK_2: starting archive log backupset
channel ORA_DISK_2: specifying archive log(s) in backup set
input archive log thread=1 sequence=26 recid=26 stamp=623931644
channel ORA_DISK_2: starting piece 1 at 30-MAY-07
channel ORA_DISK_1: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931649_s59_s1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/q02/archive/prism/log_prsmq02_25.arc recid=25 stamp=623931644
channel ORA_DISK_2: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931649_s60_s1 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_2: deleting archive log(s)
archive log filename=/q02/archive/prism/log_prsmq02_26.arc recid=26 stamp=623931644
Finished backup at 30-MAY-07
Starting backup at 30-MAY-07
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
channel ORA_DISK_1: starting incremental level 0 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00009 name=/q02/oradata01/prsmdata/Data_13.dbf
input datafile fno=00016 name=/q02/oradata01/prsmdata/Data_20.dbf
input datafile fno=00025 name=/q02/oradata01/prsmdata/Data_04.dbf
input datafile fno=00005 name=/q02/oraindx01/prsmdata/Index_11.dbf
input datafile fno=00020 name=/q02/oradata01/prsmdata/Tools02.dbf
input datafile fno=00022 name=/q02/oraindx01/prsmdata/index_12.dbf
channel ORA_DISK_1: starting piece 1 at 30-MAY-07
channel ORA_DISK_2: starting incremental level 0 datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00010 name=/q02/oradata01/prsmdata/Data_14.dbf
input datafile fno=00015 name=/q02/oradata01/prsmdata/Data_19.dbf
input datafile fno=00024 name=/q02/oradata01/prsmdata/Data_03.dbf
input datafile fno=00003 name=/q02/oratmp01/prsmdata/rbs01.dbf
input datafile fno=00001 name=/q02/orasys01/prsmdata/system01.dbf
input datafile fno=00012 name=/q02/orasys01/prsmdata/system02.dbf
channel ORA_DISK_2: starting piece 1 at 30-MAY-07
channel ORA_DISK_3: starting incremental level 0 datafile backupset
channel ORA_DISK_3: specifying datafile(s) in backupset
input datafile fno=00008 name=/q02/oradata01/prsmdata/Data_12.dbf
input datafile fno=00014 name=/q02/oradata01/prsmdata/Data_18.dbf
input datafile fno=00023 name=/q02/oradata01/prsmdata/Data_02.dbf
input datafile fno=00028 name=/q02/oradata01/prsmdata/Data06.dbf
input datafile fno=00019 name=/q02/oratmp01/prsmdata/rbs02.dbf
input datafile fno=00021 name=/q02/orasys01/prsmdata/DRSYS.dbf
channel ORA_DISK_3: starting piece 1 at 30-MAY-07
channel ORA_DISK_4: starting incremental level 0 datafile backupset
channel ORA_DISK_4: specifying datafile(s) in backupset
input datafile fno=00007 name=/q02/oradata01/prsmdata/Data_11.dbf
input datafile fno=00013 name=/q02/oradata01/prsmdata/Data_17.dbf
input datafile fno=00018 name=/q02/oradata01/prsmdata/Data_01.dbf
input datafile fno=00006 name=/q02/oradata01/prsmdata/Tools01.dbf
input datafile fno=00002 name=/q02/oradata01/prsmdata/Users01.dbf
input datafile fno=00026 name=/q02/oradata01/prsmdata/Data05.dbf
channel ORA_DISK_4: starting piece 1 at 30-MAY-07
channel ORA_DISK_5: starting incremental level 0 datafile backupset
channel ORA_DISK_5: specifying datafile(s) in backupset
input datafile fno=00004 name=/q02/oradata01/prsmdata/Data_15.dbf
input datafile fno=00011 name=/q02/oradata01/prsmdata/Data_16.dbf
input datafile fno=00017 name=/q02/oradata01/prsmdata/Data_22.dbf
input datafile fno=00027 name=/q02/oradata01/prsmdata/Data_05.dbf
channel ORA_DISK_5: starting piece 1 at 30-MAY-07
channel ORA_DISK_1: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s1 comment=NONE
channel ORA_DISK_1: starting piece 2 at 30-MAY-07
channel ORA_DISK_2: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s1 comment=NONE
channel ORA_DISK_2: starting piece 2 at 30-MAY-07
channel ORA_DISK_3: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s1 comment=NONE
channel ORA_DISK_3: starting piece 2 at 30-MAY-07
channel ORA_DISK_4: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s1 comment=NONE
channel ORA_DISK_4: starting piece 2 at 30-MAY-07
channel ORA_DISK_5: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s1 comment=NONE
channel ORA_DISK_5: starting piece 2 at 30-MAY-07
channel ORA_DISK_2: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s2 comment=NONE
channel ORA_DISK_2: starting piece 3 at 30-MAY-07
channel ORA_DISK_1: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s2 comment=NONE
channel ORA_DISK_1: starting piece 3 at 30-MAY-07
channel ORA_DISK_4: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s2 comment=NONE
channel ORA_DISK_4: starting piece 3 at 30-MAY-07
channel ORA_DISK_5: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s2 comment=NONE
channel ORA_DISK_5: starting piece 3 at 30-MAY-07
channel ORA_DISK_3: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s2 comment=NONE
channel ORA_DISK_3: starting piece 3 at 30-MAY-07
channel ORA_DISK_2: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s3 comment=NONE
channel ORA_DISK_2: starting piece 4 at 30-MAY-07
channel ORA_DISK_4: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s3 comment=NONE
channel ORA_DISK_4: starting piece 4 at 30-MAY-07
channel ORA_DISK_1: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s3 comment=NONE
channel ORA_DISK_1: starting piece 4 at 30-MAY-07
channel ORA_DISK_2: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s4 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:53:23
channel ORA_DISK_5: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s3 comment=NONE
channel ORA_DISK_5: starting piece 4 at 30-MAY-07
channel ORA_DISK_3: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s3 comment=NONE
channel ORA_DISK_3: starting piece 4 at 30-MAY-07
channel ORA_DISK_4: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s4 comment=NONE
channel ORA_DISK_4: starting piece 5 at 30-MAY-07
channel ORA_DISK_1: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s4 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:59:04
channel ORA_DISK_3: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s4 comment=NONE
channel ORA_DISK_3: backup set complete, elapsed time: 01:00:10
channel ORA_DISK_5: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s4 comment=NONE
channel ORA_DISK_5: backup set complete, elapsed time: 01:00:25
channel ORA_DISK_4: finished piece 5 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s5 comment=NONE
channel ORA_DISK_4: backup set complete, elapsed time: 01:01:40
Finished backup at 30-MAY-07
Starting backup at 30-MAY-07
current log archived
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 05/30/2007 11:22:38
RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE

connect target /You need to inform the connection string to target database.
Can to be explicitly or with 'export sid' in your script.

Can't register a database in RMAN catalog (PL/SQL package not current)

Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
Regards

user13064912 wrote:
Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
RegardsCould you try to run the rman at the target database server (MPOWER), instead of rman catalog server ant try to register your database?
Your rman client is higher than your target server. That could be the problem.
Best Regards,
Gokhan
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

RMAN-20260 error while trying to delete a backup piece

Hello,
In my company we use Oracle 10g, backup managed by RMAN and integrated with TSM.
In order to remove the old backup files, there is a delete script to do this.
Basically this script:
connect to RMAN catalog
allocate channel for maintenance device type 'sbt_tape'
change backuppiece <file names from rc_backup_piece older than 35 days> delete;
When this command is run, this error is being generated:
RMAN-03002: failure of delete command at 01/18/2010 17:14:00
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20260: backup piece not found in the recovery catalog
RMAN-06092: error while looking up backup piece
Any ideas?
Thanks in advance.
Fer

Hy Tycho,
Yes, it's a tape backup.
This is the channel used to take the backup:
allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/opt/tsm..../...opt)';
I tried this rman command with a file name that is 35 days older in rc_backup_piece:
list backuppiece <file name>;
I received this error:
RMAN-20260: backup piece not found in the recovery catalog;
How can this file be in the rc_backup_piece and not appear in the list backuppiece ?
Thanks a lot.
Fer

RMAN catalog Downgrade from 11gR1 (11.1.0.6.0) to 10gR2 (10.2.0.4)

I am in the process of downgrading rman catalog from 11gR1 (11.1.0.6.0) to 10gR2 (10.2.0.4). Using expdp/impdp we migrated the rman schema from 11g to 10g. I am able to connect to 10g catalog now. but if i run any command it gives following error.
./rman target sys
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Feb 16 11:21:11 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
target database Password:
connected to target database:
RMAN> connect catalog rman/*******@rman
connected to recovery catalog database
RMAN> show all ;
RMAN configuration parameters for database with db_unique_name NACC are:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 02/16/2010 11:21:34
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20299: DBMS_RCVMAN package not compatible with the recovery catalog
RMAN> exit
Have i missed anything which has to be done .
Thanks
Ajeet

Hi Tycho ,
Thanks for your help and suggestions . What i did is i migrated the rman catalog from 11gR1 (11.1.0.6.0) to 10gR2 (10.2.0.4) then connected rman catalog from 11gR2 Client which is the highest version available and then did the following.
RMAN> upgrade catalog;
recovery catalog upgraded to version 11.02.00.01
DBMS_RCVMAN package upgraded to version 11.02.00.01
DBMS_RCVCAT package upgraded to version 11.02.00.01
RMAN>
Now i am able to connect directly and take backup's from 11gR2 , 11gR1 and 10gR2 clients respectively. I also tested the backup's from grid control which are working fine.
Currently my rman catalog database is 10.2.0.4 and my rman catalog schema is 11.02.00.01.
Thanks for everyone's help.
Ajeet
Edited by: user12169940 on Feb 17, 2010 4:02 AM

Question:rman recover (error:Bad header found during inspecting archived )

oracle9208 aix5.2
after restore database successfully,i recover database
i receive info in alert_sid.log
Corrupt block seq: 0 blocknum=1.
Bad header found during inspecting archived log
Data in bad block - seq:184680448. bno:369098753. time:0
beg:0 cks:260
calculated check value: 2653
Reread of seq=0, blocknum=1, file=/dev/rora_redo1_21, found same corrupt data
alter database recover datafile list
161 , 162 , 163 , 164 , 165 , 166 , 167 , 168
Completed: alter database recover datafile list
161 , 162 ,
Fri Nov 6 22:37:17 2009
alter database recover if needed
start until time 'NOV 01 2009 21:07:53' using backup controlfile
Media Recovery Start
ORA-279 signalled during: alter database recover if needed
start until time...
then recover processes hang for a long time
so why and how can i solve this problem??

Dear user097815,
I think there are a couple of syntax errors and it would be better for you to first try each one one-by-one than add them into your "run" block.
RMAN> allocate channel for maintenance device type 'SBT_TAPE';
using target database control file instead of recovery catalog
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=910 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: Data Protector A.06.10/611
RMAN> allocate auxiliary channel t1 type 'sbt_tape';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "auxiliary": expecting one of: "channel"
RMAN-01007: at line 1 column 10 file: standard input
RMAN> ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "auxiliary": expecting one of: "channel"
RMAN-01007: at line 1 column 10 file: standard input
RMAN> run
ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt;
}Hope That Helps.
Ogan

RMAN throwing errors during Tablespace Backup - RMAN-06004 and RMAN-06019

Hi All.
Please help me to fix trail of error message I'm getting while trying backup of a newly added tablespace in database. I'm using RMAN as a recovery method.
Tablespace Name: test
DB Version: Oracle 10g R1.
OS: Red Hat Linux 5
RMAN> report schema;
Report of database schema
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
1 490 SYSTEM YES /u01/app/oracle/oradata/qrcl/system01.dbf
2 25 UNDOTBS1 YES /u01/app/oracle/oradata/qrcl/undotbs01.dbf
3 270 SYSAUX NO /u01/app/oracle/oradata/qrcl/sysaux01.dbf
4 23 USERS NO /u01/app/oracle/oradata/qrcl/users01.dbf
5 40 TEST NO /u01/app/test01.dbf
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
1 20 TEMP 32767 /u01/app/oracle/oradata/qrcl/temp01.dbf
RMAN>
RMAN> backup tablespace "test";
Starting backup at 22-AUG-12
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 08/22/2012 11:57:13
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20202: tablespace not found in the recovery catalog
RMAN-06019: could not translate tablespace name "test"
RMAN> restore tablespace test;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "test": expecting one of: "double-quoted-string, identifier, single-quoted-string"
RMAN-01007: at line 1 column 20 file: standard input
I tried to update Catalog Server but still no luck:
RMAN> RESYNC CATALOG;
starting full resync of recovery catalog
full resync complete
Please Assist.
Thanks
Prashant Dixit

Hello Prashant;
The main issue is your tablespace name is an RMAN Reserved Word "Test"
http://docs.oracle.com/cd/B13789_01/server.101/b10770/rcmcomma.htm#1006728
Different test
-- Create the tablespace
CREATE TABLESPACE OTN_TEST DATAFILE
'/u01/oradata/RECOVER2/test01.dbf' SIZE 1M AUTOEXTEND OFF
LOGGING
ONLINE;-- Create a user for the tablespace
CREATE USER RMAN_TEST
IDENTIFIED BY RMAN_TEST
DEFAULT TABLESPACE OTN_TEST
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
ALTER USER RMAN_TEST QUOTA UNLIMITED ON "OTN_TEST"; -- Create a table in the tablespace
CREATE TABLE RMAN_TEST.EMP
EMPNO     NUMBER,
ENAME     VARCHAR2(30 BYTE),
JOB       VARCHAR2(30 BYTE),
MGR       NUMBER,
HIREDATE DATE,
SAL       NUMBER,
COMM      NUMBER,
DEPTNO    NUMBER
TABLESPACE OTN_TEST;-- Add some data
SET DEFINE OFF;
Insert into RMAN_TEST.EMP
   (EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO)
Values
   (7369, 'SMITH', 'CLERK', 7902, TO_DATE('12/17/1980 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
    800, 20, 0);
Insert into RMAN_TEST.EMP
   (EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO)
Values
   (5000, 'NOCATALOG', 'DBA', 77902, TO_DATE('04/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
    200, 0, 0);
COMMIT;-- start RMAN and backup tablespace
RMAN> BACKUP TABLESPACE OTN_TEST;
Starting backup at 22-AUG-12
starting full resync of recovery catalog
full resync complete
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00007 name=/u01/oradata/RECOVER2/test01.dbf
channel ORA_DISK_1: starting piece 1 at 22-AUG-12
channel ORA_DISK_1: finished piece 1 at 22-AUG-12
piece handle=/u01/app/oracle/flash_recovery_area/RECOVER2/backupset/2012_08_22/o1_mf_nnndf_TAG20120822T080711_839pczng_.bkp tag=TAG20120822T080711 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 22-AUG-12
Starting Control File and SPFILE Autobackup at 22-AUG-12
piece handle=/u01/app/oracle/flash_recovery_area/RECOVER2/autobackup/2012_08_22/o1_mf_s_791971633_839pd1bm_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 22-AUG-12
Note
If you dropped the tablespace then you need to recover the database to a point in time, not the tablespace.
Best Regards
mseberg

RMAN clone error

Hi:
I got error at end when doing a RMAN clone on linux, RMAN 11.1.0.7. 89163 is the next to last highest sequence
number in the backup log file. So in the clone script I put 89165.
ORA-19870: error while restoring backup piece
ORA-19504: failed to create file
ORA-17502: ksfdcre:4 Failed to create file
ORA-15173: entry 'archive' does not exist in directory '/'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/19/2012 17:36:15
RMAN-03015: error occurred in stored script Memory Script
RMAN-20506: no backup of archived log found
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 89163 and starting SCN of 11158664662 found to restore
What is the problem here?
Can I bring up the database up?
Thank you for your help.

Then you may get an error as below
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 89165you can try to open the database with resetlogs as you would not be having the archive sequence 89165
Also, 1 suggestion. Since you are on 11g, why not use the feature "active database" ?
rman target sys/pwd@target catalog xxxx auxiliary wwww
RMAN>duplicate target database to 'CLONEDB' from active database;This does not require you to take the backup first and then start the cloning activity

Rman target error

hi,
while i'm target the database i'm getting following error. pls help me target the database
RMAN TARGET / CATALOG RMAN01/RMAN01@ADAPTIME Recovery Manager:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "recovery": expecting one of: "append, at, auxil
iary, catalog, cmdfile, clone, checksyntax, debug, log, msglog, mask, msgno, noc
atalog, pipe, rcvcat, script, slaxdebug, send, target, timeout, trace"
RMAN-01007: at line 1 column 46 file: standard input

hi nick,
i had done that but still its not connecting and its coming to next line pls chk the below output from rman. pls help me
C:\>rman
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Aug 8 10:47:54 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect catalog rman01/rman01@test
connected to recovery catalog database
RMAN> RMAN TARGET / CATALOG RMAN01/RMAN01@ADAPTIME Recovery Manager:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "recovery": expecting one of: "append, at, auxil
iary, catalog, cmdfile, clone, checksyntax, debug, log, msglog, mask, msgno, noc
atalog, pipe, rcvcat, script, slaxdebug, send, target, timeout, trace"
RMAN-01007: at line 1 column 46 file: standard input
RMAN> RMAN TARGET / CATALOG RMAN01/RMAN01@ADAPTIME
2>

RMAN-06172 error when restoring to a DR system

Hello,
I am not a trained DBA, I only have some basic understandings and what I can figure out from the manuals and googling.
I have a production 10G R2 database, on Red Hat 5, that I backup using Backup Exec 2010.
I perform weekly live Full backups followed by 6 days of incrementals. I also perform a month offline backup once a month.
Archive logs are used.
RMAN setting are at the default.
In getting my Disaster Recover site up and tested I performed a restore of the cold last coldl backup and a live full.
Both where successful except for a minor issue that was fixed with restoring the Archive logs
recently I was testing my procedures again and ran into this error
RMAN-03002
RMAN-06172
I have attempted to research this issue but I am having issues understanding what I need to do?
I have looked into these MetaLink articles 351826.1, 735115.1, 369680.1, 274237.1, 261426.1, 292835.1
I am confused as to why I was able to restore one full live backup but not the next one.
Thank you for any insight you can give.

Here is the RMAN log from one of the restore attempts.
All restores are done as if the production server had been lost and I had only the tapes to restore with.
===========================================================
# RMAN command section
RUN {
ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
SEND 'BSA_SERVICE_HOST=10.1.1.35,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={C5D98C8E-5E64-4587-97EB-DDD9351E13B5},NBBSA_DB_DEVICE_NAME=Oracle-Linux::\\server.domain\SID';
RESTORE CONTROLFILE FROM 'BE_bulsuqdc_1_1';
RELEASE CHANNEL ch0;
connected to target database: webct (not mounted)
using target database control file instead of recovery catalog
allocated channel: ch0
channel ch0: sid=483 devtype=SBT_TAPE
channel ch0: Symantec/BackupExec/1.1.0
sent command to channel: ch0
Starting restore at 22-NOV-10
released channel: ch0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/22/2010 15:00:16
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
Recovery Manager complete.
===========================================================
Thanks,
William

Our RMAN Catalog Problem

Hello
We have 7 major oracle instances on 2 servers and we have created a RMAN catalog on another server
Our principal databases are Standard Oracle 10g (10.2.0.2.0) under linux , and the catalog is Enterprise Oracle 10g (10.2.0.2.0) in Windows all the databases are registered in catalog when I query RC_DATABSE view it shows all
instances informations , in all RMAN login commands the "CATALOG" clause has been written
Now my problem is that just two of databases backups are recorded in catalog for example when I query "RC_BACKUP_SET" view it only contains backups of two databases while are backups have been performed completely without any error
Do you know what is problem ?
thank you

select dbid,name from rman_user.rc_database;
DBID        NAME
<h4>----------------  ----------------</h4>
1498968931       SCSDB
4293064263        SSTDB
861276728         SUBDB
2404423160        SAM
3976246282        SFIDB
1760672514    SCEDB
817528985        S900NS1
select t.name,t1.db_id,bs_key
from rman_user.RC_BACKUP_SET t1,rman_user.rc_database t
where t1.db_id=t.dbid;
NAME        DB_ID        BS_KEY
<h4>----------------  ----------------  ----------------</h4>
SUBDB        861276728        14366
SUBDB        861276728        14365
SUBDB        861276728        14364
SAM        2404423160        14491
SAM        2404423160        14490
SAM        2404423160       14489
select name, max(START_TIME)
from rman_user.rc_database d,
rman_user.rc_backup_set s
where db_id(+) = dbid
group by name
order by 2 desc;
NAME        MAX(START_TIME)
<h4>----------------  ----------------</h4>
SCEDB
S900NS1
SCSDB
SFIDB
SSTDB
SAM        6/14/2008 1:06:15 AM
SUBDB        6/13/2008 9:02:43 PM
This date (6/14/2008) is old because I haven't used the catalog for a long time, due to the problem I've mentioned above.
Edited by: TakhteJamshid on Jan 10, 2010 2:49 AM
Edited by: TakhteJamshid on Jan 10, 2010 3:00 AM

RMAN catalog errors

Similar Messages

Maybe you are looking for