RMAN-06091 error

I've searched the forums, but am still not sure what action to take on this. Please see the error in my output, below -- why am I getting this, and is it actually preventing the "cleanup" of my archivelog files?
HERE'S WHAT I ENTERED AS RMAN COMMANDS:
RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'd:\DB-BackupS\RMAN\%d_%T-%s.rbk';
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'd:\DB-BackupS\RMAN\%d_%F';
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS;
RMAN> CONFIGURE BACKUP OPTIMIZATION ON;
RMAN> backup database;
RMAN> delete force noprompt obsolete recovery window of 4 days;
RMAN> delete force noprompt copy of archivelog all completed before 'sysdate-4';
RMAN> crosscheck backup;
RMAN> crosscheck archivelog all;
RMAN> exit
HERE'S THE RESULTS:
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: P2KLIVE (DBID=2051172780)
using target database controlfile instead of recovery catalog
RMAN>
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'd:\DB-BackupS\RMAN\%d_%T-%s.rbk';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'd:\DB-BackupS\RMAN\%d_%T-%s.rbk';
new RMAN configuration parameters are successfully stored
RMAN>
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'd:\DB-BackupS\RMAN\%d_%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'd:\DB-BackupS\RMAN\%d_%F';
new RMAN configuration parameters are successfully stored
RMAN>
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS;
new RMAN configuration parameters are successfully stored
RMAN>
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
RMAN>
Starting backup at 29-JUN-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=14 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\P2KLIVE\P2K_DATA01.DBF
input datafile fno=00005 name=E:\ORACLE\ORADATA\P2KLIVE\P2K_INDX01.DBF
input datafile fno=00008 name=\\HRIS\E$\ORACLE\ORADATA\P2KLIVE\UNDOTBS02.DBF
input datafile fno=00001 name=E:\ORACLE\ORADATA\P2KLIVE\SYSTEM01.DBF
input datafile fno=00007 name=E:\ORACLE\ORADATA\P2KLIVE\XDB01.DBF
input datafile fno=00003 name=E:\ORACLE\ORADATA\P2KLIVE\DRSYS01.DBF
input datafile fno=00006 name=E:\ORACLE\ORADATA\P2KLIVE\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 29-JUN-07
channel ORA_DISK_1: finished piece 1 at 29-JUN-07
piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070629-287.RBK comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:45
Finished backup at 29-JUN-07
Starting Control File and SPFILE Autobackup at 29-JUN-07
piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070629-05 comment=NONE
Finished Control File and SPFILE Autobackup at 29-JUN-07
RMAN>
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 244 25-JUN-07
Backup Piece 244 25-JUN-07 D:\DB-BACKUPS\RMAN\P2KLIVE_20070625-257.RBK
Backup Set 245 25-JUN-07
Backup Piece 245 25-JUN-07 D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070625-00
Backup Set 248 25-JUN-07
Backup Piece 248 25-JUN-07 BE_85il57nn_1_1
Archive Log 308 25-JUN-07 D:\ORACLE\ORA920\RDBMS\ARC00410.001
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 06/29/2007 10:20:13
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
RMAN>
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=14 devtype=DISK
List of Archived Log Copies
Key Thrd Seq S Low Time Name
308 1 410 A 22-JUN-07 D:\ORACLE\ORA920\RDBMS\ARC00410.001
309 1 411 A 25-JUN-07 D:\ORACLE\ORA920\RDBMS\ARC00411.001
deleted archive log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00410.001 recid=308 stamp=626171155
deleted archive log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00411.001 recid=309 stamp=626171708
Deleted 2 objects
RMAN>
using channel ORA_DISK_1
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070625-257.RBK recid=244 stamp=626148299
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070625-00 recid=245 stamp=626148374
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070627-265.RBK recid=252 stamp=626321096
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070627-00 recid=253 stamp=626321180
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070627-267.RBK recid=254 stamp=626353277
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070627-01 recid=255 stamp=626353363
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070628-269.RBK recid=256 stamp=626407499
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070628-00 recid=257 stamp=626407583
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070629-275.RBK recid=262 stamp=626493868
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070629-00 recid=263 stamp=626493963
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070629-281.RBK recid=268 stamp=626517547
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070629-02 recid=269 stamp=626517652
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070629-283.RBK recid=270 stamp=626519017
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070629-03 recid=271 stamp=626519112
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070629-285.RBK recid=272 stamp=626519863
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070629-04 recid=273 stamp=626519958
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070629-287.RBK recid=274 stamp=626523108
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070629-05 recid=275 stamp=626523214
Crosschecked 18 objects
RMAN>
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=14 devtype=DISK
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00412.001 recid=310 stamp=626449016
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00413.001 recid=311 stamp=626449031
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00414.001 recid=312 stamp=626449097
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00415.001 recid=313 stamp=626449113
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00416.001 recid=314 stamp=626449333
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00417.001 recid=315 stamp=626449434
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00418.001 recid=316 stamp=626449464
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00419.001 recid=317 stamp=626449525
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00420.001 recid=318 stamp=626449551
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00421.001 recid=319 stamp=626449609
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00422.001 recid=320 stamp=626451732
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00423.001 recid=321 stamp=626451741
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00424.001 recid=322 stamp=626451812
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00425.001 recid=323 stamp=626451841
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00426.001 recid=324 stamp=626451885
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00427.001 recid=325 stamp=626451965
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00428.001 recid=326 stamp=626451976
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00429.001 recid=327 stamp=626455769
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00430.001 recid=328 stamp=626463508
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00431.001 recid=329 stamp=626463801
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00432.001 recid=330 stamp=626501782
validation succeeded for archived log
archive log filename=D:\ORACLE\ORA920\RDBMS\ARC00433.001 recid=331 stamp=626501975
Crosschecked 22 objects
RMAN>
Recovery Manager complete.

Thanks for the suggestion but, unless I'm not understanding correctly, it's not working.
Here's my current RMAN file:
========================================
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'd:\DB-BackupS\RMAN\%d_%T-%s.rbk';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'd:\DB-BackupS\RMAN\%d_%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
backup database;
delete obsolete device type disk;
allocate channel for delete device type DISK;
run {delete force noprompt obsolete recovery window of 4 days;}
delete force noprompt copy of archivelog all completed before 'sysdate-4';
crosscheck backup;
crosscheck archivelog all;
sql "alter database backup controlfile to ''d:\DB-backupS\SystemFiles\P2KLIVE.ctrl'' reuse";
sql "create pfile=''d:\DB-backupS\SystemFiles\initP2KLIVE.ora'' from spfile";
exit;
========================================
and the new results:
========================================
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: P2KLIVE (DBID=2051172780)
using target database controlfile instead of recovery catalog
RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'd:\DB-BackupS\RMAN\%d_%T-%s.rbk';
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'd:\DB-BackupS\RMAN\%d_%F';
3>
4> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS;
5>
6> CONFIGURE BACKUP OPTIMIZATION ON;
7>
8> # NO MORE SHUTDOWN shutdown immediate;
9>
10> # NO MORE SHUTDOWN startup mount;
11>
12> backup database;
13>
14> # TAPE allocate channel for maintenance device type SBT;
15> #NEW 7/6/07
16> delete obsolete device type disk;
17> allocate channel for delete device type DISK;
18> run {delete force noprompt obsolete recovery window of 4 days;}
19> delete force noprompt copy of archivelog all completed before 'sysdate-4';
20>
21> crosscheck backup;
22> crosscheck archivelog all;
23>
24> # NO MORE SHUTDOWN alter database open;
25>
26> sql "alter database backup controlfile to ''d:\DB-backupS\SystemFiles\P2KLIVE.ctrl'' reuse";
27>
28> sql "create pfile=''d:\DB-backupS\SystemFiles\initP2KLIVE.ora'' from spfile";
29>
30> exit;
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'd:\DB-BackupS\RMAN\%d_%T-%s.rbk';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'd:\DB-BackupS\RMAN\%d_%T-%s.rbk';
new RMAN configuration parameters are successfully stored
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'd:\DB-BackupS\RMAN\%d_%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'd:\DB-BackupS\RMAN\%d_%F';
new RMAN configuration parameters are successfully stored
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS;
new RMAN configuration parameters are successfully stored
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
Starting backup at 09-JUL-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=22 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\P2KLIVE\P2K_DATA01.DBF
input datafile fno=00005 name=E:\ORACLE\ORADATA\P2KLIVE\P2K_INDX01.DBF
input datafile fno=00002 name=E:\ORACLE\ORADATA\P2KLIVE\UNDOTBS01.DBF
input datafile fno=00001 name=E:\ORACLE\ORADATA\P2KLIVE\SYSTEM01.DBF
input datafile fno=00007 name=E:\ORACLE\ORADATA\P2KLIVE\XDB01.DBF
input datafile fno=00003 name=E:\ORACLE\ORADATA\P2KLIVE\DRSYS01.DBF
input datafile fno=00006 name=E:\ORACLE\ORADATA\P2KLIVE\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-JUL-07
channel ORA_DISK_1: finished piece 1 at 09-JUL-07
piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_20070709-342.RBK comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
Finished backup at 09-JUL-07
Starting Control File and SPFILE Autobackup at 09-JUL-07
piece handle=D:\DB-BACKUPS\RMAN\P2KLIVE_C-2051172780-20070709-01 comment=NONE
Finished Control File and SPFILE Autobackup at 09-JUL-07
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 4 days
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=22 devtype=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 244 25-JUN-07
Backup Piece 244 25-JUN-07 D:\DB-BACKUPS\RMAN\P2KLIVE_20070625-257.RBK
<snip long list>
RMAN-06207: WARNING: 18 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
List of Mismatched objects
==========================
Object Type Filename/Handle
Backup Piece D:\DB-BACKUPS\RMAN\P2KLIVE_20070625-257.RBK
<snip long list>
released channel: ORA_DISK_1
allocated channel: ORA_MAINT_DISK_1
channel ORA_MAINT_DISK_1: sid=22 devtype=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 244 25-JUN-07
Backup Piece 244 25-JUN-07 D:\DB-BACKUPS\RMAN\P2KLIVE_20070625-257.RBK
<snip long list>
Archive Log 399 05-JUL-07 D:\ORACLE\ORA920\RDBMS\ARC00501.001
Archive Log 398 05-JUL-07 D:\ORACLE\ORA920\RDBMS\ARC00500.001
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 07/09/2007 11:13:58
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
Recovery Manager complete.

Similar Messages

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

RMAN Restore Error - media recovery requesting unknown log: thread 1 seq 7

Im using RMAN to copy a database to another server. The new server is IDENTICAL to the old one. By identical I mean it has the same sever name, ip address, operating system, Oracle version and directory structure.
The new server already has the instance created, (same name as the old server instance, paths etc)
The backup files have been manually restored to the new server, same locations as they were on the old one. ( RMAN did an automatic controlfile backup and also the archivelogs on the old server ).
Ive restored the control file on the new server from the RMAN backup pieces.
Ive catalogued the RMAN backup pieces on the new server.
I know the last sequence available in the archivelogs backup by running on the new server :
list backup of archivelog all;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
5 14.43M DISK 00:00:03 11-MAY-11
BP Key: 9 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163502
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
011_05_11\O1_MF_ANNNN_TAG20110511T163502_6WOC5833_.BKP
List of Archived Logs in backup set 5
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2 550217 10-MAY-11 556559 11-MAY-11
1 3 556559 11-MAY-11 559776 11-MAY-11
1 4 559776 11-MAY-11 560093 11-MAY-11
1 5 560093 11-MAY-11 560794 11-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
7 15.50K DISK 00:00:01 11-MAY-11
BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163653
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
List of Archived Logs in backup set 7
Thrd Seq Low SCN Low Time Next SCN Next Time
1 6 560794 11-MAY-11 560851 11-MAY-11
So far its all going swimmingly well.
Now I want to restore the datafiles and recover. So I ran :
RMAN run { restore database; recover database; alter database open resetlogs; }
This gave me the output below which goes great but I get a final error, I think the error is because its looking for an archive log thats not in the backup set, but it should be. However, I think SCN 560851 is for a log that hadnt been created yet on the old server when the backup was ran ?
How do I address resolving the error ? Its worth pointing out log, "archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
\2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741" isnt on the old server either which is why its not in the backup set.
I can do a alter database open reset logs but Id prefer to know why its failing.
Any help would be much appreciated.
RMAN> run { restore database; recover database; alter database open resetlogs; }
Starting restore at 11-MAY-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSTEM01.DBF
restoring datafile 00002 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\UNDOTBS01.DBF
restoring datafile 00003 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSAUX01.DBF
restoring datafile 00004 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\USERS01.DBF
channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP tag=TAG20110511T163507
channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
Finished restore at 11-MAY-11
Starting recover at 11-MAY-11
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=6
channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP tag=TAG20110511T163653
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
\2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC thread=1 sequence=6
channel default: deleting archive log(s)
archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
\2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741
unable to find archive log
archive log thread=1 sequence=7
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/11/2011 18:15:42
RMAN-06054: media recovery requesting unknown log: thread 1 seq 7 lowscn 560851
RMAN>
Edited by: user12173666 on 11-May-2011 10:28

You need to do incomplete recovery i.e. to ask RMAN to restore/recover to some specific point in time. This is usually done with some UNTIL clause or SET UNTIL statement. Example in your case:
SET UNTIL SEQUENCE 7;See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta065.htm#RCMRF160.

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.

RMAN-03015: error occurred in stored script Memory Script

getting this error during
target db is 10202 & aux is 10204 ?
duplicate target database to dcxt;
RMAN> connect TARGET SYS/spurs_04@capq;
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: CAPQ (DBID=2420849281)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel clone_default
RMAN-10006: error running SQL statement: select action from gv$session where sid=:1 and serial#=:2 and inst_id=:3
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 05/21/2010 15:32:29
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
oracle:tuldcorpadb01:dcxt$
Edited by: DBA2008 on May 21, 2010 3:37 PM

never mind, i resolved this by switching duplicate db to 10203....and adjusting log_arch_dest .....

RMAN duplicate errors

Hi:
I was doing a 11g database clone on linux using rman duplicate. After runing 40min, it stopped and got the following errors. All the file permission are the same 777, one third of files have been copied.
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
failover to previous backup
released channel: aux1
released channel: aux2
released channel: aux3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/30/2012 08:28:07
RMAN-05501: aborting duplication of target database
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 12312 and starting SCN of 23167256063 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 12311 and starting SCN of 23167250994 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 12310 and starting SCN of 23167245674 found to restore
Thanks and regards.

Files from source database:
-rwxrwSrwx 1 root root 48653824 May 29 20:57 db_t784587134_s1208_p1
-rwxrwSrwx 1 root root 48594944 May 29 20:57 db_t784587149_s1209_p1
-rwxrwSrwx 1 root root 7761920 May 29 20:57 db_t784587150_s1210_p1
-rwxrwSrwx 1 root root 4062945280 May 29 21:23 db_t784587170_s1211_p1
-rwxrwSrwx 1 root root 1124147200 May 29 21:07 db_t784587170_s1212_p1
-rwxrwSrwx 1 root root 2049015808 May 29 21:16 db_t784587725_s1213_p1
-rwxrwSrwx 1 root root 4012630016 May 29 21:36 db_t784588310_s1214_p1
-rwxrwSrwx 1 root root 4620419072 May 29 21:43 db_t784588726_s1215_p1
-rwxrwSrwx 1 root root 3724255232 May 29 21:52 db_t784589461_s1216_p1
-rwxrwSrwx 1 root root 1818624 May 29 21:43 db_t784589896_s1217_p1
-rwxrwSrwx 1 root root 2071040 May 29 21:52 db_t784590427_s1218_p1
There are about 30 dbf files on source database, 10 dbf files on target database now.

RMAN Clone Errors

Hello,
We use Commvault for our backup software. I can successfully clone one application's PROD instance on server1 to TEST on server2.
However, for another application, attempting the same process of cloning the app's PROD instance on server1 to TEST on server2, I'm getting RMAN errors.
The prod database is ISLP and test database is ISLT. I've set the parameters:
o alter system set db_file_name_convert = '/u02/oradata/ISLP', '/u02/oradata/ISLT'
o alter system set log_file_name_convert= '/u01/oradata/ISLP', '/data/oracle/ISLT'
Again the destination is on a second server.
The error message I receive is:
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/09/2013 12:48:55
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary file name /u02/oradata/ISLP/redo_ISLP_2b.log conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u02/oradata/ISLP/redo_ISLP_1b.log conflicts with a file used by the target database
RMAN>
Recovery Manager complete.
I don't understand why RMAN keeps trying to create new redo log files in a directory that is not specified by the log_file_name_convert parameter. I also don't understand why this exact same process works for cloning one applications database but not this application. I would appreciate any help. Thank you. Here is the RMAN script being executed by Commvault.
Rman Script:
[run {
set newname for datafile '/u02/oradata/ISLP/infosilem_ISLP_01.dbf' to '/u02/oradata/ISLT/infosilem_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/sysaux_ISLP_01.dbf' to '/u02/oradata/ISLT/sysaux_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/system_ISLP_01.dbf' to '/u02/oradata/ISLT/system_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/tools_ISLP_01.dbf' to '/u02/oradata/ISLT/tools_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/undo_ISLP_01.dbf' to '/u02/oradata/ISLT/undo_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/users_ISLP_01.dbf' to '/u02/oradata/ISLT/users_ISLP_01.dbf';
allocate auxiliary channel ch1 type 'sbt_tape'
PARMS="SBT_LIBRARY=/opt/galaxy/Base64/libobk.so,BLKSIZE=262144,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1,ThreadCommandLine= RESTORE -jm 142 -a 2:0 -cl 137 -ins 150 -at 22 -j 700481 -jt 700481:3:1 -bal 0 -rcp 0 -ms 1 -p 2 -cn s-dbint -vm Instance001)"
TRACE 0;
set until time = "TO_DATE('05/08/2013 09:00:00','MM/DD/YYYY HH24:MI:SS')" ;
duplicate target database to 'ISLT'
exit;
]

You haven't defined a log_file_name_convert for /u02/oradata/ISLP/
Possibly, the database has multiplexed redo log files, one member each in /u01/oradata/ISLP and one member each in /u02/oradata/ISLP.
Hemant K Chitale

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-00558: error encountered while parsing input commands

Hi,
on 12C on Win 2008
as said in documentation :
@ (at sign)
Example 2-2 Running a Command File Within RMAN
This example shows how you can execute a command file from the RMAN prompt and from within a RUN command. User-entered text appears in bold.
RMAN> @backup_db.rman
I do as follows to run a script to back up :
RMAN> @C:\scripts\RMAN\al_backup_full_cdb.rman LOG=C:\scripts\logs\al_backup_full_log
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "log": expecting one of: "double-quoted-string, identifier, integer, single-quoted-string"
RMAN-01007: at line 1 column 1 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "@": expecting one of: "double-quoted-string, identifier, integer, single-quoted-string"
RMAN-01007: at line 0 column 1 file: standard input
Thank you.

user10274093 wrote:
yes thank you. Like this :
@C:\scripts\RMAN\al_backup_full_cdb.rman
But how to have a log file ?
You can not use the log= clause *inside* rman, you can only use it on the shell prompt *outside* rman.

RMAN-10006: error running SQL statement: alter session set remote_dependenc

Backups are failing with following error
RMAN-00554: initialization of internal recovery manager package failed
RMAN-12001: could not open channel default
RMAN-10008: could not create channel context
RMAN-10002: ORACLE error: ORA-00096: invalid value SIGNATURE for parameter remote_dependencies_mode, must be from among MANUAL, AUTO
RMAN-10006: error running SQL statement: alter session set remote_dependencies_mode = signature
Not able to change to signature
SQL> alter session set remote_dependencies_mode=signature;
ERROR:
ORA-00096: invalid value SIGNATURE for parameter remote_dependencies_mode, must
be from among MANUAL, AUTO
I dont see MANUAL or AUTO as valid value for this parameter (http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch1175.htm#1023124) DB version is 9.2.0
Parameter type
String
Syntax
REMOTE_DEPENDENCIES_MODE = {TIMESTAMP | SIGNATURE}
Default value
TIMESTAMP
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
=======================================
I believe it could be because of following bug
"A PRE-PATCHED ORACLE IMAGE CAN BE INSTALLED IN MEMORY "
Refer: "https://metalink2.oracle.com/metalink/plsql/f?p=130:15:1613505143885559758::::p15_database_id,p15_docid,p15_show_header,p15_show_help,p15_black_frame,p15_font:BUG,4610411,1,1,1,helvetica"
I appreciate your effort in fixing this issue.
Edited by: user10610722 on Nov 25, 2008 4:37 PM

Hi:
It seems when you are starting RMAN it's executing some commands (one 'ALTER SESSION...'. It's seems to be a batch which has a bad value for SORT_AREA_SIZE. Find it and modify to a proper value as message shows. If you can't find start RMAN by calling directly the executable ($ORACLE_HOME/bin/rman or %ORACLE_HOME%/bin/rman.exe).

RMAN DUPLICATE ERROR

I was executing RMAN DUPLICATE and received this error?
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/08/2007 13:41:22
RMAN-03015: error occurred in stored script Memory Script
RMAN-04014: startup failed: ORA-01078: failure in processing system parameters
RMAN-04017: startup error description: LRM-00109: could not open parameter file
'/u01/app/oracle/product/10.2.0/dbs/initDPDEVUG.ora'
Anybody knows how to fix this error?

I had this file only in CLONED databae $ORACLE_HOME/dbs. I copy this file into SOURCE database $ORACLE_HOME/dbs. Since duplicate initiation going from SOURCE to CLONED. May this is problem?
I am going to re start Clone process and let you know if this was the case

RMAN SBT_TAPE error

When I am trying to delete the obsolete backups I get this error .
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ch1 channel at 11/08/2007 15:21:08
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
need help !
Thanks,

Hi,
Looks like you had done the "TAPE" backup earlier and trying to delete obsolete backup from the "TAPE".
Then, you need to allocate "SBT_TAPE" channel for deleting obsolete backup as like you did for the tape backup.
Right now, default rman uses disk type channels.
HTH.
- Nirmal

Error in duplicating dataguard, RMAN-04006: error from auxiliary,ORA-12514

Hi All,
Trying to duplicate using rman and facing below issue
rman TARGET sys/oracle@pawsdb AUXILIARY sys/oracle@adpaws
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Jun 19 20:47:09 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: PAWSDB (DBID=3014417093)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
TNS on aux looks like this
ADPAWS =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.210.23.227)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = adpaws)
Listener under grid home (ASM) on aux looks like this
# listener.ora Network Configuration File: /home/oracle/app/oracle/product/11.2.0/grid/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /home/oracle/app/oracle/product/11.2.0/grid)
(SID_NAME = adpaws)
(GLOBAL_DBNAME= adpaws.example.com)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = cuscmetl.hillscte.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
ADR_BASE_LISTENER = /home/oracle/app/oracle
output of lsnrctl on aux looks like this
LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 19-JUN-2012 20:53:49
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=cuscmetl.hillscte.com)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.3.0 - Production
Start Date 19-JUN-2012 20:53:42
Uptime 0 days 0 hr. 0 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /home/oracle/app/oracle/product/11.2.0/grid/network/admin/listener.ora
Listener Log File /home/oracle/app/oracle/diag/tnslsnr/cuscmetl/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=cuscmetl.hillscte.com)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "adpaws.example.com" has 1 instance(s).
Instance "adpaws", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
TNS on target is also configured properly, both are tnsping successful from each other, running this command from aux server results in failure
Please help
thanks

Thanks for reply, below are the last 50 lines from listener log
<msg time='2012-06-19T21:10:13.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:13 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56363)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:13.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:13 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56364)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:18.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:18 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56366)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:18.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:18 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56367)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:23.126-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:23 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56368)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:23.159-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:23 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56369)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:28.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:28 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56371)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:28.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:28 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56372)) * establish * etldb * 0
</txt>
</msg>

RMAN-06091 error

Similar Messages

Maybe you are looking for