RMAN-06208
Hi,
we are in 9.2.0 version of DB.
1-I have this RMAN-06208 in RMAN backup output :
RMAN-06207: WARNING: 5 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:\DOCUMENTS\RMAN\C_5DI0IHIO_1_1
Backup Piece D:\DOCUMENTS\RMAN\C_5FI0IIMU_1_1
Backup Piece D:\DOCUMENTS\RMAN\C_5MI1CTAJ_1_1
Backup Piece D:\DOCUMENTS\RMAN\C_5PI1T0BR_1_1
Backup Piece D:\DOCUMENTS\RMAN\C_5QI1VKON_1_1
What should I exactly do ? Just CROSSCHECK would be enough ? Or I should add some arguments etc ...
2-How to make sure that backup is already safe ?
Many thanks.
Hello,
Try this:
crosscheck backup;
This will then list all the invalid and valid backup that are in the o/s.
Then you can do
list expired backup;
which will give you all the files that are in the controlfile / catalog but don't
exist within the o/s.
then if you want to you can delete these, which will remove it from the catalog (if you are using rman catalog) or the controlfie.
delete obsolete backup;
hope this helps.
Similar Messages
-
RMAN-06207 when DELETE NOPROMPT OBSOLETE;
Hello all
I want to backup and delete backuped archivelogs on a standby instance using the following script:
RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE sbt PARMS='ENV=......';
BACKUP ARCHIVELOG ALL DELETE INPUT;
DELETE NOPROMPT OBSOLETE;
RELEASE CHANNEL ch1;
When deleting all obsolete backup pieces, I receive the following error:
RMAN-06207: WARNING: 1 objects could not be deleted for SBT_TAPE channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06214: Backup Piece c-2414804385-20080820-02
As a workaround, I then manually delete obsolete backup pieces using:
delete force noprompt obsolete device type sbt_tape
What is the cause for rman-06207 ? How can I change my rman script to safely delete backuped archivelogs?
I work with Oracle 10G release 10.2.0.3 both on standby and catalog DB.
CasiDid you try using the CROSSCHECK command to verify the backup files status?
From your comments, it doesn't seem like you did. CROSSCHECK checks the status of the RMAN backups against the disk/tape and updates the RMAN repository. CROSSCHECK does not remove any files just updates the status. The status options are - expired, available, and unavailable. -
We had database which used regular hot backup scripts. I am in process of configure this database to use RMAN as backup tool.
After first couple backup runs (with delete obsolete) I am getting this warning error:
RMAN-06207: WARNING: 2 objects could not be deleted for DISK channel(s) d
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06213: --------------- ---------------------------------------------
RMAN-06214: Datafile Copy /u10/oraback/DPDEVUG/HOT/control1DPDEVUG.ctl
RMAN-06214: Datafile Copy /u10/oraback/DPDEVUG/HOT/control2DPDEVUG.ctl
I executed : crosscheck archivelog all and stll getting this warning.
Any ideas?You are having a problems on datafile copies.
You need to
crosscheck copy of controlfile;
as far as I know.
Sybrand Bakker
Senior Oracle DBA -
Hi,
I have these warninigs :
RMAN-06207: WARNING: 3 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 /mars/Backup/DB1/bck_DB1_LV0_tqhvdrb4_1_1
Backup Piece /mars/Backup/DB2/bck_DB2_LV0_u8i024sc_1_1
Backup Piece /mars/Backup/DB2/bck_DB2_LV0_uai025vg_1_1
Any solution ?
It says CROSSCHECK, but CRROSSCHECK what, which parameter ?
Many thanks beforewhat actually you are doing with RMAN?
please specify version of database.
for oracle 9i
RMAN>crosscheck backup; -
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. -
I am testing creating a RMAN duplicate for standby. I running into a situation where RMAN looking at old control files but I can't get clean them out.
deleted from OS, delete obsolete tells me to crosscheck but when I crosscheck RMAN says not found in catalog. any suggestions? Thanks
RMAN-06207: WARNING: 2 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Datafile Copy /convdb/oradata/PROD/PROD_stdby.ctl
RMAN-06214: Datafile Copy /convdb/oradata/PROD/backup/rman/prod_stbycntr.ctl
RMAN> crosscheck datafilecopy '/convdb/oradata/PROD/PROD_stdby.ctl';
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=197 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 02/12/2008 10:56:07
RMAN-20230: datafile copy not found in the recovery catalog
RMAN-06015: error while looking up datafile copy name: /convdb/oradata/PROD/PROD_stdby.ctl
RMAN> crosscheck datafilecopy '/convdb/oradata/PROD/backup/rman/prod_stbycntr.ctl';
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=197 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 02/12/2008 10:56:24
RMAN-20230: datafile copy not found in the recovery catalog
RMAN-06015: error while looking up datafile copy name: /convdb/oradata/PROD/backup/rman/prod_stbycntr.ctlTry to issue:
RMAN> crosscheck controlfilecopy '/convdb/oradata/PROD/PROD_stdby.ctl';
RMAN> crosscheck controlfilecopy '/convdb/oradata/PROD/backup/rman/prod_stbycntr.ctl';and then:
RMAN> delete expired controlfilecopy '/convdb/oradata/PROD/PROD_stdby.ctl';
RMAN> delete expired controlfilecopy '/convdb/oradata/PROD/backup/rman/prod_stbycntr.ctl'; -
Hi All,
we have hot backups of DB scheduled(DB Full backup) thru RMAN for all prod DBs.. but since some days all the backups are failing with similar error.. the sample output of one of the backup job run is given below:
set command id to 'BACKUP_PRSAL41_FUL_091007040002';
echo set on
executing command: SET COMMAND ID
connected to recovery catalog database
connected to target database: PRSAL41 (DBID=3043389771)
input datafile fno=00002 name=/prddb02/u12/oradata/prsal41/undotbs01.dbf
input datafile fno=00007 name=/prddb02/u12/oradata/prsal41/autodba8601dat0101.dbf
input datafile fno=00008 name=/prddb02/u12/oradata/prsal41/autodba8601idx0101.dbf
input datafile fno=00004 name=/prddb02/u12/oradata/prsal41/users01.dbf
channel ORA_DISK_1: starting piece 1 at 10-SEP-07
input datafile fno=00006 name=/prddb02/u12/oradata/prsal41/IIS_INDEX_01.dbf
input datafile fno=00005 name=/prddb02/u12/oradata/prsal41/IIS_DATA_01.dbf
input datafile fno=00003 name=/prddb02/u12/oradata/prsal41/sysaux01.dbf
input datafile fno=00001 name=/prddb02/u12/oradata/prsal41/system01.dbf
channel ORA_DISK_1: specifying datafile(s) in backupset
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: sid=147 devtype=DISK
allocated channel: ORA_DISK_1
Starting backup at 10-SEP-07
backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' da
Starting Control File and SPFILE Autobackup at 10-SEP-07
Finished backup at 10-SEP-07
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:25
piece handle=/back01/prsal41/5oiricui_1_1 tag=BACKUP_PRSAL41_FUL_091007040002 comment=NONE
channel ORA_DISK_1: finished piece 1 at 10-SEP-07
Finished Control File and SPFILE Autobackup at 10-SEP-07
piece handle=/back01/prsal41/c-3043389771-20070910-00 comment=NONE
backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' ar
Starting backup at 10-SEP-07
current log archived
released channel: ORA_DISK_1
allocated channel: ORA_MAINT_DISK_1
channel ORA_MAINT_DISK_1: sid=147 devtype=DISK
delete noprompt obsolete device type disk;
allocate channel for maintenance type disk;
Additional information: 3
Linux-x86_64 Error: 2: No such file or directory
ORA-27037: unable to obtain file status
ORA-19625: error identifying file /hubudorap1/arch01/prsal41/1_132_626515083.arc
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
RMAN-03002: failure of backup command at 09/10/2007 04:02:55
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 2 days
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Archive Log 275349 18-JUL-07 /hubudorap1/arch01/prsal41/1_132_626515083.arc
Archive Log 275350 18-JUL-07 /hubudorap1/arch01/prsal41/1_133_626515083.arc
Backup Set 383337 15-AUG-07
Backup Piece 383340 15-AUG-07 /back01/prsal41/44ipdr6h_1_1
Backup Set 383353 15-AUG-07
Backup Piece 383362 15-AUG-07 /back01/prsal41/c-3043389771-20070815-00
Backup Set 500971 07-SEP-07
Backup Piece 500974 07-SEP-07 /back01/prsal41/5iirafql_1_1
Archive Log 501025 07-SEP-07 /hubudorap1/arch01/prsal41/1_404_626515083.arc
Backup Set 500987 07-SEP-07
Backup Piece 500996 07-SEP-07 /back01/prsal41/c-3043389771-20070907-00
Archive Log 505768 07-SEP-07 /hubudorap1/arch01/prsal41/1_405_626515083.arc
Archive Log 505769 07-SEP-07 /hubudorap1/arch01/prsal41/1_406_626515083.arc
Archive Log 505770 07-SEP-07 /hubudorap1/arch01/prsal41/1_407_626515083.arc
Archive Log 505771 08-SEP-07 /hubudorap1/arch01/prsal41/1_408_626515083.arc
deleted backup piece
backup piece handle=/back01/prsal41/5iirafql_1_1 recid=178 stamp=632635222
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_404_626515083.arc recid=373 stamp=632635334
archive log filename=/hubudorap1/arch01/prsal41/1_405_626515083.arc recid=374 stamp=632661717
deleted archive log
backup piece handle=/back01/prsal41/c-3043389771-20070907-00 recid=179 stamp=632635329
deleted backup piece
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_408_626515083.arc recid=377 stamp=632718235
Deleted 7 objects
RMAN-06207: WARNING: 4 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
archive log filename=/hubudorap1/arch01/prsal41/1_407_626515083.arc recid=376 stamp=632705451
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_406_626515083.arc recid=375 stamp=632685605
deleted archive log
RMAN-06212: Object Type Filename/Handle
RMAN-06214: Backup Piece /back01/prsal41/c-3043389771-20070815-00
RMAN-06214: Backup Piece /back01/prsal41/44ipdr6h_1_1
RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_133_626515083.arc
RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_132_626515083.arc
RMAN-06213: --------------- ---------------------------------------------------
release channel;
exit;
released channel: ORA_MAINT_DISK_1
I am not able to detect why the archive log is missing... can anyone help me on this please..?
btw, DBs are oracle 10g R2 non-rac
Backup type : DB Full via RMAN.
ThanksHi,
Have you used the CROSSCHECK command?
I am not able to detect why the archive log is missing... can anyone help me on this please..?Could someone removed them through O/S commands (manually) ?
Adith -
The DB version is 11.1.0.7.
The "CATALOG START WITH" not only catalog backup set that are not in the RMAN catalog, but also catalog a second copy for files that are already in the catalog.
Files are not a second copy; they are the same file in the same directory.
Having two copies in the catalog, through an error when deleting explicitly the backups.
We have to add the force clause to avoid the error.
RMAN> delete FORCE backup tag 'offsite-1';
The force clause ignores any I/O error.
The delete is part of our scheduled offsite backup script, which returns a false positive error when the force clause is ommited.
I don't want the force clause, in order to be notify if the backup set that are expected to be on disk are no more there, e.g., if someone had deleted files manually at the OS level bypassing rman.
Is there a way to only catalog backup set not in the catalog?
or May be remove the copy #2 entry from the catalog?
Find bellow a test case example:
RMAN> list backup summary TAG 'OFFSITE-1';
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
12 B F A DISK 11-JUN-13 09:41:45 1 1 NO OFFSITE-1
13 B F A DISK 11-JUN-13 09:43:31 1 1 NO OFFSITE-1
14 B A A DISK 11-JUN-13 09:43:33 1 1 NO OFFSITE-1
15 B F A DISK 11-JUN-13 09:43:34 1 1 NO OFFSITE-1
RMAN> CATALOG START WITH 'C:\backups\offsite_disk\IBISdatabase\scheduled_offsite';
searching for all files that match the pattern C:\backups\offsite_disk\IBISdatabase\scheduled_offsite
cataloging done
List of Cataloged Files
=======================
File Name: C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\scheduled_offsite\06OBTJEP_1_1
File Name: C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\scheduled_offsite\07OBTJI3_1_1
File Name: C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\scheduled_offsite\08OBTJI5_1_1
File Name: C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\scheduled_offsite\09OBTJI6_1_1
RMAN> list backup summary TAG 'OFFSITE-1';
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
12 B F A DISK 11-JUN-13 09:41:45 1 2 NO OFFSITE-1
13 B F A DISK 11-JUN-13 09:43:31 1 2 NO OFFSITE-1
14 B A A DISK 11-JUN-13 09:43:33 1 2 NO OFFSITE-1
15 B F A DISK 11-JUN-13 09:43:34 1 2 NO OFFSITE-1
RMAN> DELETE BACKUP TAG 'OFFSITE-1';
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
24 18 1 1 AVAILABLE DISK C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\06OBTJEP_1_1 <<--- same file
30 18 1 2 AVAILABLE DISK C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\06OBTJEP_1_1 <<--- same file
25 19 1 1 AVAILABLE DISK C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\07OBTJI3_1_1
31 19 1 2 AVAILABLE DISK C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\07OBTJI3_1_1
26 20 1 1 AVAILABLE DISK C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\08OBTJI5_1_1
32 20 1 2 AVAILABLE DISK C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\08OBTJI5_1_1
27 21 1 1 AVAILABLE DISK C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\09OBTJI6_1_1
33 21 1 2 AVAILABLE DISK C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\09OBTJI6_1_1
deleted backup piece
backup piece handle=C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\06OBTJEP_1_1 RECID=24 STAMP=821470356
deleted backup piece
backup piece handle=C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\07OBTJI3_1_1 RECID=25 STAMP=821470356
deleted backup piece
backup piece handle=C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\08OBTJI5_1_1 RECID=26 STAMP=821470356
deleted backup piece
backup piece handle=C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\09OBTJI6_1_1 RECID=27 STAMP=821470357
Deleted 6 objects
RMAN-06207: WARNING: 4 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\06OBTJEP_1_1
RMAN-06214: Backup Piece C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\07OBTJI3_1_1
RMAN-06214: Backup Piece C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\08OBTJI5_1_1
RMAN-06214: Backup Piece C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\09OBTJI6_1_1Hi JM,
Your demo with Oracle 10.2.0.5
At line 36 you answered "No" to "Do you really want to catalog the above files (enter YES or NO)?".
Just repeate your demo and answer Yes.
Even if he might have replied with "YES" then also, the RMAN search for the files which it can recognize as a valid rman backup file. Else it would show the list of files which are not recognized by RMAN as a valid file.
RMAN> catalog start with '/home/oracle/scripts';
using target database control file instead of recovery catalog
searching for all files that match the pattern /home/oracle/scripts
List of Files Unknown to the Database
=====================================
File Name: /home/oracle/scripts/RMAN_BACKUP.sh
File Name: /home/oracle/scripts/rman_clone.log
File Name: /home/oracle/scripts/Db_Refresh.sh
File Name: /home/oracle/scripts/rman_erp.scr
File Name: /home/oracle/scripts/RMAN_14FEB.log
File Name: /home/oracle/scripts/nid.sh
File Name: /home/oracle/scripts/Full_Clone.sh
File Name: /home/oracle/scripts/rman_staging.scr
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
no files cataloged
List of Files Which Where Not Cataloged
=======================================
File Name: /home/oracle/scripts/RMAN_BACKUP.sh
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/rman_clone.log
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/Db_Refresh.sh
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/rman_erp.scr
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/RMAN_14FEB.log
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/nid.sh
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/Full_Clone.sh
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/rman_staging.scr
RMAN-07517: Reason: The file header is corrupted
About the RMAN catalog, it will not catalog the same file twice. It will only catalog the files which are not known to the database.
See this demo. (/backup/RMAN/STAGING/ is the location where all the backup pieces are.)
RMAN> catalog start with '/backup/RMAN/STAGING/';
searching for all files that match the pattern /backup/RMAN/STAGING/
no files found to be unknown to the database
This was the location based test, Another demo showing piece by piece catalogging .
RMAN> list backuppiece '/backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00';
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
1323 1321 1 1 AVAILABLE DISK /backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00
RMAN> catalog backuppiece '/backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00';
cataloged backup piece
backup piece handle=/backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00 RECID=1324 STAMP=821717283
RMAN> list backuppiece '/backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00';
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
1324 1321 1 1 AVAILABLE DISK /backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00
Hope its understandable, if any query please revert.
Happy to Help.
Thanks and Regards,
Prashant -
Problem to open the oracle XE Database
Log file name : oxe_backup_current.log
XE Backup Log
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Sep 12 04:26:21 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: XE (DBID=2619028465, not open)
RMAN>
echo set on
RMAN> shutdown immediate;
using target database control file instead of recovery catalog
database dismounted
Oracle instance shut down
RMAN> startup mount;
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area 805306368 bytes
Fixed Size 1261444 bytes
Variable Size 213909628 bytes
Database Buffers 587202560 bytes
Redo Buffers 2932736 bytes
RMAN> configure retention policy to redundancy 2;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters are successfully stored
RMAN> configure controlfile autobackup format for device type disk clear;
RMAN configuration parameters are successfully reset to default value
RMAN> configure controlfile autobackup on;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
RMAN> sql "create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile";
sql statement: create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile
RMAN> backup as backupset device type disk database;
Starting backup at 12-SEP-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=102 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/usr/lib/oracle/xe/oradata/XE/sysaux.dbf
input datafile fno=00005 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_log01.dbf
input datafile fno=00006 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_lrg01.dbf
input datafile fno=00001 name=/usr/lib/oracle/xe/oradata/XE/system.dbf
input datafile fno=00009 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_log01.dbf
input datafile fno=00010 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_lrg01.dbf
input datafile fno=00002 name=/usr/lib/oracle/xe/oradata/XE/undo.dbf
input datafile fno=00004 name=/usr/lib/oracle/xe/oradata/XE/users.dbf
input datafile fno=00008 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_sml01.dbf
input datafile fno=00012 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_sml01.dbf
input datafile fno=00011 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_mdm01.dbf
input datafile fno=00007 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_mdm01.dbf
channel ORA_DISK_1: starting piece 1 at 12-SEP-11
channel ORA_DISK_1: finished piece 1 at 12-SEP-11
piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_09_12/o1_mf_nnndf_TAG20110912T042633_76vjksws_.bkp tag=TAG20110912T042633 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
Finished backup at 12-SEP-11
Starting Control File and SPFILE Autobackup at 12-SEP-11
piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_09_12/o1_mf_s_761631122_76vjl97m_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 12-SEP-11
RMAN> configure controlfile autobackup off;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
new RMAN configuration parameters are successfully stored
RMAN> alter database open;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 09/12/2011 04:26:51
ORA-00322: log 1 of thread 1 is not current copy
ORA-00312: online log 1 thread 1: '/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/onlinelog/o1_mf_1_6jmmyqk8_.log'
RMAN> delete noprompt obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 3 12-SEP-11
Backup Piece 3 12-SEP-11 /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_09_12/o1_mf_nnndf_TAG20110912T040202_76vh3v58_.bkp
Backup Set 4 12-SEP-11
Backup Piece 4 12-SEP-11 /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_09_12/o1_mf_s_761630513_76vh4yjx_.bkp
Backup Set 5 12-SEP-11
Backup Piece 5 12-SEP-11 /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_09_12/o1_mf_nnndf_TAG20110912T040908_76vhk4n6_.bkp
Backup Set 6 12-SEP-11
Backup Piece 6 12-SEP-11 /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_09_12/o1_mf_s_761630513_76vhkmyg_.bkp
RMAN-06207: WARNING: 4 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_09_12/o1_mf_nnndf_TAG20110912T040202_76vh3v58_.bkp
RMAN-06214: Backup Piece /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_09_12/o1_mf_s_761630513_76vh4yjx_.bkp
RMAN-06214: Backup Piece /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_09_12/o1_mf_nnndf_TAG20110912T040908_76vhk4n6_.bkp
RMAN-06214: Backup Piece /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_09_12/o1_mf_s_761630513_76vhkmyg_.bkp
RMAN>
Recovery Manager complete.
RMAN error: See log for details.
An error also comes out while opening the database through SQL statement
SQL> connect sys as sysdba
Enter password:
Connected.
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 805306368 bytes
Fixed Size 1261444 bytes
Variable Size 213909628 bytes
Database Buffers 587202560 bytes
Redo Buffers 2932736 bytes
Database mounted.
ORA-00322: log 1 of thread 1 is not current copy
ORA-00312: online log 1 thread 1:
*'/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/onlinelog/o1_mf_1_6jmmyqk8_.log'*
SQL>
Its an error (problem) of our DC ( Primary) Sever so Please reply back with suitable answer as soon as possible
Regards,
Niraj Prasad Karn
Edited by: 870614 on Sep 14, 2011 10:38 AMI suggest you transfer this threat to a different forum, as this is the OEM GC forum.
I guess you want to post in the Database forum.
Regards
Rob
http://oemgc.wordpress.com -
Restore archivelogs from backupset
STEP-1
RMAN> backup archivelog all;
Starting backup at 13-MAR-13
current log archived
using channel ORA_DISK_1
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=6 recid=61 stamp=809960486
channel ORA_DISK_1: starting piece 1 at 13-MAR-13
channel ORA_DISK_1: finished piece 1 at 13-MAR-13
piece handle=F:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2013_03_13\O1_MF_ANNNN_TAG20130313T130126_8N0BTHKN_.BKP tag=TAG20130313T130126 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 13-MAR-13
STEP-2
RMAN> list archivelog all;
List of Archived Log Copies
Key Thrd Seq S Low Time Name
61 1 6 A 13-MAR-13 F:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_03_13\O1_MF_1_6_8N0BTFLF_.ARC
STEP -3
RMAN> delete archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
List of Archived Log Copies
Key Thrd Seq S Low Time Name
61 1 6 A 13-MAR-13 F:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_03_13\O1_MF_1_6_8N0BTFLF_.ARC
Do you really want to delete the above objects (enter YES or NO)? yes
RMAN-06207: WARNING: 1 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Archivelog F:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_03_13\O1_MF_1_6_8N0BTFLF_.ARC
STEP-4
RMAN> crosscheck archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
validation failed for archived log
archive log filename=F:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_03_13\O1_MF_1_6_8N0BTFLF_.ARC recid=61 stamp=809960486
Crosschecked 1 objects
RMAN>
what i done after step 1 , is i delete (or moved ) archivelog from its original destination.
NOW, as i have a backup of archivelog in backupset , how do i restore archivelogs from there??
10.2.0
win 7 prof
Thanks
Edited by: O0O0O0O0O on Mar 13, 2013 1:10 PMSalman Qureshi wrote:
Hi,
what i done after step 1 , is i delete (or moved ) archivelog from its original destination.No, you took backup in sirts step. You deleted your archived redo logs in 3rd stepNO, After 1st step i deleted /moved archivelog , thats why @ 3rd step its giving error that Oracle Cant Find Archivelog to delete ( i guess it dsnt matter )
NOW, as i have a backup of archivelog in backupset , how do i restore archivelogs from there??Following should help you in restoration of archive redo logs. Simplest way is to use "restore archivelog all" to restore all archived redo logs from your backups which are available.
when i do this , its giving error
RMAN> restore archivelog all;
Starting restore at 13-MAR-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/13/2013 13:25:48
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of log thread 1 seq 5 lowscn 2065032 found to restore
RMAN-06025: no backup of log thread 1 seq 4 lowscn 2061724 found to restore
RMAN-06025: no backup of log thread 1 seq 3 lowscn 2038915 found to restore
RMAN-06025: no backup of log thread 1 seq 2 lowscn 2015492 found to restore
RMAN-06025: no backup of log thread 1 seq 1 lowscn 1990741 found to restore
RMAN-06025: no backup of log thread 1 seq 19 lowscn 1986423 found to restore
RMAN-06025: no backup of log thread 1 seq 18 lowscn 1959113 found to restore
RMAN-06025: no backup of log thread 1 seq 17 lowscn 736604 found to restore
RMAN-06025: no backup of log thread 1 seq 16 lowscn 694859 found to restore
RMAN-06025: no backup of log thread 1 seq 15 lowscn 654358 found to restore
RMAN-06025: no backup of log thread 1 seq 14 lowscn 631019 found to restore
RMAN-06025: no backup of log thread 1 seq 13 lowscn 630977 found to restore
RMAN-06025: no backup of log thread 1 seq 12 lowscn 628120 found to restore
RMAN-06025: no backup of log thread 1 seq 11 lowscn 627821 found to restore
RMAN-06025: no backup of log thread 1 seq 10 lowscn 624694 found to restore
RMAN-06025: no backup of log thread 1 seq 9 lowscn 624184 found to restore
RMAN-06025: no backup of log thread 1 seq 8 lowscn 620379 found to restore
RMAN-06025: no backup of log thread 1 seq 7 lowscn 619730 found to restore
RMAN-06025: no backup of log thread 1 seq 6 lowscn 619728 found to restore
RMAN-06025: no backup of log thread 1 seq 5 lowscn 619725 found to restore
RMAN-06025: no backup of log thread 1 seq 4 lowscn 619722 found to restore
RMAN-06025: no backup of log thread 1 seq 3 lowscn 617154 found to restore
RMAN-06025: no backup of log thread 1 seq 2 lowscn 608546 found to restore
RMAN>
Edited by: O0O0O0O0O on Mar 13, 2013 1:28 PM -
hi am trying to do backup using rman but database fail
C:\>rman target sys/pswd@sid NOCATALOG
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Nov 7 17:47:34 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SMSDEV (DBID=3638300981, not open)
using target database control file instead of recovery catalog
RMAN> backup database;
Starting backup at 07-NOV-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=133 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00010 name=C:\APP\TSHIFHIWA\PRODUCT\11.2.0\DBHOME_1\DATABASE\TEST
input datafile file number=00008 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\GATEWAY_TBS.DBF
input datafile file number=00001 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\SYSTEM01.DBF
input datafile file number=00002 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\SYSAUX01.DBF
input datafile file number=00003 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\UNDOTBS01.DBF
input datafile file number=00004 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\USERS01.DBF
input datafile file number=00007 name=C:\APP\TSHIFHIWA\PRODUCT\11.2.0\DBHOME_1\DATABASE\TEMP09
input datafile file number=00009 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\ECADASTRE_TBS.DBF
input datafile file number=00005 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\TEMP06.DBF
input datafile file number=00006 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\TEMP05.DBF
channel ORA_DISK_1: starting piece 1 at 07-NOV-13
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/07/2013 17:51:55
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 5218762752 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 07-NOV-13
channel ORA_DISK_1: finished piece 1 at 07-NOV-13
piece handle=C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSET\2013_11_07\O1_MF_NCSNF_TAG2013110
t=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/07/2013 17:51:55
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 5218762752 limiti did this still geting error
SQL> connect /as sysdba
Connected.
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=4294967296 SCOPE=BOTH;
System altered.
SQL> commit;
Commit complete.
SQL> shutdown abort;
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1375792 bytes
Variable Size 373293520 bytes
Database Buffers 155189248 bytes
Redo Buffers 5804032 bytes
Database mounted.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Pr
oduction
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:\>rman target sys/pswd@SID NOCATALOG
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Nov 7 19:16:33 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SMSDEV (DBID=3638300981, not open)
using target database control file instead of recovery catalog
RMAN> delete backup;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=133 device type=DISK
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
3 3 1 1 AVAILABLE DISK C:\APP\TSHIFHIWA\FLASH_RECOVERY_
AREA\SMSDEV\BACKUPSET\2013_11_07\O1_MF_NCSNF_TAG20131107T182444_97QHXTTS_.BKP
4 4 1 1 AVAILABLE DISK C:\APP\TSHIFHIWA\FLASH_RECOVERY_
AREA\SMSDEV\BACKUPSET\2013_11_07\O1_MF_NCSNF_TAG20131107T183949_97QJSS14_.BKP
7 7 1 1 AVAILABLE DISK C:\APP\TSHIFHIWA\FLASH_RECOVERY_
AREA\SMSDEV\BACKUPSET\2013_11_07\O1_MF_NCSNF_TAG20131107T191006_97QLKMYL_.BKP
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSET\2013_1
1_07\O1_MF_NCSNF_TAG20131107T191006_97QLKMYL_.BKP RECID=7 STAMP=830891603
Deleted 1 objects
RMAN-06207: WARNING: 2 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSE
T\2013_11_07\O1_MF_NCSNF_TAG20131107T182444_97QHXTTS_.BKP
RMAN-06214: Backup Piece C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSE
T\2013_11_07\O1_MF_NCSNF_TAG20131107T183949_97QJSS14_.BKP
RMAN> backup database;
Starting backup at 07-NOV-13
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=00010 name=C:\APP\TSHIFHIWA\PRODUCT\11.2.0\DBHOME_1\D
ATABASE\TEST
input datafile file number=00008 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\GATEWAY_TB
S.DBF
input datafile file number=00001 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\SYSTEM01.D
BF
input datafile file number=00002 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\SYSAUX01.D
BF
input datafile file number=00003 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\UNDOTBS01.
DBF
input datafile file number=00004 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\USERS01.DB
F
input datafile file number=00007 name=C:\APP\TSHIFHIWA\PRODUCT\11.2.0\DBHOME_1\D
ATABASE\TEMP09
input datafile file number=00009 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\ECADASTRE_
TBS.DBF
input datafile file number=00005 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\TEMP06.DBF
input datafile file number=00006 name=C:\APP\TSHIFHIWA\ORADATA\SMSDEV\TEMP05.DBF
channel ORA_DISK_1: starting piece 1 at 07-NOV-13
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/07/2013 19:20:
10
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 4294967296 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 07-NOV-13
channel ORA_DISK_1: finished piece 1 at 07-NOV-13
piece handle=C:\APP\TSHIFHIWA\FLASH_RECOVERY_AREA\SMSDEV\BACKUPSET\2013_11_07\O1
_MF_NCSNF_TAG20131107T191653_97QLYCJK_.BKP tag=TAG20131107T191653 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/07/2013 19:20:
10
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk
space from 4294967296 limit -
Database backup with lost archive logs
How can I get a database backup when all the archive logs have been lost?
here's the full test of the backup:
Recovery Manager: Release 9.2.0.7.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to target database: ESKHDEV1 (DBID=4075873486)
using target database controlfile instead of recovery catalog
RMAN>
echo set on
RMAN> run {
2> allocate channel oem_backup_disk1 type disk format '/sbdbarc/backups/eskhdev1/%U' maxpiecesize 2000 M;
3> backup filesperset = 3 tag 'BACKUP_ESKHDEV1_00_101008022533' database;
4> backup filesperset = 3 tag 'BACKUP_ESKHDEV1_00_101008022533' archivelog all not backed up;
5> release channel oem_backup_disk1;
6> }
allocated channel: oem_backup_disk1
channel oem_backup_disk1: sid=18 devtype=DISK
Starting backup at 10-OCT-08
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00013 name=/spte/oracle/oradata/ESKHDEV1/leafdat02.dbf
input datafile fno=00011 name=/spte/oracle/oradata/ESKHDEV1KLXTEMP.dbf
input datafile fno=00001 name=/spte/oracle/oradata/ESKHDEV1/system01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2jjsq87q_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:00:45
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00002 name=/spte/oracle/oradata/ESKHDEV1/undotbs01.dbf
input datafile fno=00008 name=/spte/oracle/oradata/ESKHDEV1/tools01.dbf
input datafile fno=00005 name=/spte/oracle/oradata/ESKHDEV1/example01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2kjsq897_1_1 comment=NONE
channel oem_backup_disk1: starting piece 2 at 10-OCT-08
channel oem_backup_disk1: finished piece 2 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2kjsq897_2_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:20
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00017 name=/spte/oracle/oradata/ESKHDEV1/parentidx01.dbf
input datafile fno=00015 name=/spte/oracle/oradata/ESKHDEV1/lral3201.dbf
input datafile fno=00010 name=/spte/oracle/oradata/ESKHDEV1/xdb01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2ljsq8bn_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:05
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00012 name=/spte/oracle/oradata/ESKHDEV1/leafdat01.dbf
input datafile fno=00006 name=/spte/oracle/oradata/ESKHDEV1/indx01.dbf
input datafile fno=00003 name=/spte/oracle/oradata/ESKHDEV1/cwmlite01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2mjsq8dp_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:15
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00014 name=/spte/oracle/oradata/ESKHDEV1/leafidx.dbf
input datafile fno=00009 name=/spte/oracle/oradata/ESKHDEV1/users01.dbf
input datafile fno=00004 name=/spte/oracle/oradata/ESKHDEV1/drsys01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2njsq8g4_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:15
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00016 name=/spte/oracle/oradata/ESKHDEV1/parentdat01.dbf
input datafile fno=00007 name=/spte/oracle/oradata/ESKHDEV1/odm01.dbf
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2ojsq8if_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:01:35
Finished backup at 10-OCT-08
Starting backup at 10-OCT-08
current log archived
channel oem_backup_disk1: starting archive log backupset
channel oem_backup_disk1: specifying archive log(s) in backup set
input archive log thread=1 sequence=1260 recid=1236 stamp=667755183
channel oem_backup_disk1: starting piece 1 at 10-OCT-08
channel oem_backup_disk1: finished piece 1 at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/2pjsq8lf_1_1 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:00:02
Finished backup at 10-OCT-08
Starting Control File and SPFILE Autobackup at 10-OCT-08
piece handle=/sbdbarc/backups/eskhdev1/c-4075873486-20081010-02 comment=NONE
Finished Control File and SPFILE Autobackup at 10-OCT-08
released channel: oem_backup_disk1
RMAN> delete noprompt obsolete device type disk;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=18 devtype=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 2 17-MAR-08
Backup Piece 2 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_10_1_649591917.rbp
Backup Set 6 17-MAR-08
Backup Piece 6 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_14_1_649594217.rbp
Backup Set 7 17-MAR-08
Backup Piece 7 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_16_1_649594217.rbp
Backup Set 8 17-MAR-08
Backup Piece 8 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_17_1_649594353.rbp
Backup Set 9 17-MAR-08
Backup Piece 9 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_19_1_649595236.rbp
Backup Set 10 17-MAR-08
Backup Piece 10 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_18_1_649595236.rbp
Backup Set 11 17-MAR-08
Backup Piece 11 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_20_1_649595236.rbp
Backup Set 12 17-MAR-08
Backup Piece 12 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_21_1_649595381.rbp
Backup Set 13 17-MAR-08
Backup Piece 13 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_24_1_649595445.rbp
Backup Set 14 17-MAR-08
Backup Piece 14 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_22_1_649595445.rbp
Backup Set 15 17-MAR-08
Backup Piece 15 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_23_1_649595445.rbp
Backup Set 16 17-MAR-08
Backup Piece 16 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_25_1_649595471.rbp
Backup Set 17 17-MAR-08
Backup Piece 17 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_27_1_649604714.rbp
Backup Set 18 17-MAR-08
Backup Piece 18 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_26_1_649604714.rbp
Backup Set 19 17-MAR-08
Backup Piece 19 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_28_1_649604714.rbp
Backup Set 20 17-MAR-08
Backup Piece 20 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_29_1_649604850.rbp
Backup Set 21 17-MAR-08
Backup Piece 21 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_31_1_649604923.rbp
Backup Set 22 17-MAR-08
Backup Piece 22 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_30_1_649604923.rbp
Backup Set 23 17-MAR-08
Backup Piece 23 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_33_1_649606774.rbp
Backup Set 24 17-MAR-08
Backup Piece 24 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_32_1_649606774.rbp
Backup Set 25 17-MAR-08
Backup Piece 25 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_34_1_649606774.rbp
Backup Set 26 17-MAR-08
Backup Piece 26 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_35_1_649606900.rbp
Backup Set 27 17-MAR-08
Backup Piece 27 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_37_1_649606970.rbp
Backup Set 28 17-MAR-08
Backup Piece 28 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_36_1_649606970.rbp
Backup Set 29 17-MAR-08
Backup Piece 29 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_39_1_649607591.rbp
Backup Set 30 17-MAR-08
Backup Piece 30 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_38_1_649607591.rbp
Backup Set 31 17-MAR-08
Backup Piece 31 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_40_1_649607591.rbp
Backup Set 32 17-MAR-08
Backup Piece 32 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_41_1_649607707.rbp
Backup Set 33 17-MAR-08
Backup Piece 33 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_43_1_649607785.rbp
Backup Set 34 17-MAR-08
Backup Piece 34 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_42_1_649607785.rbp
Backup Set 35 17-MAR-08
Backup Piece 35 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_45_1_649609650.rbp
Backup Set 36 17-MAR-08
Backup Piece 36 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_44_1_649609650.rbp
Backup Set 37 17-MAR-08
Backup Piece 37 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_46_1_649609650.rbp
Backup Set 38 17-MAR-08
Backup Piece 38 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_47_1_649609777.rbp
Backup Set 39 17-MAR-08
Backup Piece 39 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_49_1_649609840.rbp
Backup Set 40 17-MAR-08
Backup Piece 40 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_48_1_649609840.rbp
Backup Set 41 17-MAR-08
Backup Piece 41 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_51_1_649611229.rbp
Backup Set 42 17-MAR-08
Backup Piece 42 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_50_1_649611229.rbp
Backup Set 43 17-MAR-08
Backup Piece 43 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_52_1_649611229.rbp
Backup Set 44 17-MAR-08
Backup Piece 44 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_53_1_649611355.rbp
Backup Set 45 17-MAR-08
Backup Piece 45 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_55_1_649611419.rbp
Backup Set 46 17-MAR-08
Backup Piece 46 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_54_1_649611419.rbp
Backup Set 47 17-MAR-08
Backup Piece 47 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_57_1_649612920.rbp
Backup Set 48 17-MAR-08
Backup Piece 48 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_56_1_649612920.rbp
Backup Set 49 17-MAR-08
Backup Piece 49 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_58_1_649612920.rbp
Backup Set 50 17-MAR-08
Backup Piece 50 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_59_1_649613075.rbp
Backup Set 51 17-MAR-08
Backup Piece 51 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_61_1_649613158.rbp
Backup Set 52 17-MAR-08
Backup Piece 52 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_60_1_649613158.rbp
Backup Set 66 10-OCT-08
Backup Piece 68 10-OCT-08 /sbdbarc/backups/eskhdev1/2bjsppct_1_1
Backup Set 67 10-OCT-08
Backup Piece 69 10-OCT-08 /sbdbarc/backups/eskhdev1/2cjsppea_1_1
Backup Piece 70 10-OCT-08 /sbdbarc/backups/eskhdev1/2cjsppea_2_1
Backup Set 68 10-OCT-08
Backup Piece 71 10-OCT-08 /sbdbarc/backups/eskhdev1/2djsppgq_1_1
Backup Set 69 10-OCT-08
Backup Piece 72 10-OCT-08 /sbdbarc/backups/eskhdev1/2ejsppir_1_1
Backup Set 70 10-OCT-08
Backup Piece 73 10-OCT-08 /sbdbarc/backups/eskhdev1/2fjsppl6_1_1
Backup Set 71 10-OCT-08
Backup Piece 74 10-OCT-08 /sbdbarc/backups/eskhdev1/2gjsppnh_1_1
Backup Set 72 10-OCT-08
Backup Piece 75 10-OCT-08 /sbdbarc/backups/eskhdev1/c-4075873486-20081010-00
Backup Set 73 10-OCT-08
Backup Piece 76 10-OCT-08 /sbdbarc/backups/eskhdev1/c-4075873486-20081010-01
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2bjsppct_1_1 recid=68 stamp=667739549
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2cjsppea_1_1 recid=69 stamp=667739594
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2cjsppea_2_1 recid=70 stamp=667739639
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2djsppgq_1_1 recid=71 stamp=667739674
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2ejsppir_1_1 recid=72 stamp=667739739
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2fjsppl6_1_1 recid=73 stamp=667739814
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/2gjsppnh_1_1 recid=74 stamp=667739889
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/c-4075873486-20081010-00 recid=75 stamp=667739965
deleted backup piece
backup piece handle=/sbdbarc/backups/eskhdev1/c-4075873486-20081010-01 recid=76 stamp=667742372
Deleted 9 objects
RMAN-06207: WARNING: 48 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 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_10_1_649591917.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_14_1_649594217.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_16_1_649594217.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_17_1_649594353.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_19_1_649595236.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_18_1_649595236.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_20_1_649595236.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_21_1_649595381.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_24_1_649595445.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_22_1_649595445.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_23_1_649595445.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_25_1_649595471.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_27_1_649604714.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_26_1_649604714.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_28_1_649604714.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_29_1_649604850.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_31_1_649604923.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_30_1_649604923.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_33_1_649606774.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_32_1_649606774.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_34_1_649606774.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_35_1_649606900.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_37_1_649606970.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_36_1_649606970.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_39_1_649607591.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_38_1_649607591.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_40_1_649607591.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_41_1_649607707.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_43_1_649607785.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_42_1_649607785.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_45_1_649609650.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_44_1_649609650.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_46_1_649609650.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_47_1_649609777.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_49_1_649609840.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_48_1_649609840.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_51_1_649611229.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_50_1_649611229.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_52_1_649611229.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_53_1_649611355.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_55_1_649611419.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_54_1_649611419.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_57_1_649612920.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_56_1_649612920.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_58_1_649612920.rbp
Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_59_1_649613075.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_61_1_649613158.rbp
Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_60_1_649613158.rbp
RMAN> release channel;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of release command at 10/10/2008 15:33:09
RMAN-06474: maintenance channels are not allocated
RMAN> exit;
Recovery Manager complete. -
How can i do a RMAN backup of my database from the network ?
i'm using oracle 8i.1.7.3 with win server 2003
i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
i'd like to save the backup in another machine (the same LAN, the same OS ).
to do that i've mapped a logical device in my comptur (z):
when i run rman command i got this error:
channel ORA_DISK_1: starting piece 1 at .......
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
00
ORA-19504: failed TO CREATE file "\\remote\save\"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
rrect.Hi,
ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
also make sure that oracle user has permission to write to this direcotry (chmod command)
hope this helps
cheers, walrus -
Issue in configuring Standby Database from Active database in 11g by RMAN
POSTED THE SAME IN DATA GUARD CATEGORY UNABLE TO DELETE
Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.
Edited by: 895188 on Dec 21, 2012 5:50 PM
Edited by: 895188 on Dec 21, 2012 6:09 PM
Edited by: 895188 on Dec 21, 2012 6:22 PMHello;
Script has to be run from auxiliary.
Great details, but what I don't see is how you connect in RMAN.
Example
Start RMAN
$ORACLE_HOME/bin/rman target=sys/@recover2 auxiliary=sys/@reclone
Recovery Manager: Release 11.2.0.2.0 - Production on Wed Feb 22 14:50:31 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RECOVER2 (DBID=3806912436)
connected to auxiliary database: RECLONE (not mounted)Nothing in your tnsnames or listener jumps out as wrong. I copied them into my text editor and compared against my working ones.
Generally for active duplication I start the future standby on a pfile NOMOUNT.
Auxiliary Instance Initialization Parameters Needed :
DB_NAME
CONTROL_FILES
DB_BLOCK_SIZE
( add extra parameters like DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT instead of using the SET command - clean up standby spfile right after duplication )
Then start RMAN and finally run a single line duplication command.
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
RMAN>duplicate target database for standby from active database NOFILENAMECHECK;Best Regards
mseberg -
Issue in creating the standby database from Active database using RMAN
Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.Pl do not post duplicates - Issue in configuring Standby Database from Active database in 11g by RMAN
Maybe you are looking for
-
I have an iMac G3 333 - tray load. I've got 256mb of ram in it and I just received a set of 10.3 installation disks - the black label ones - 4 in the set. My firmware is also at least v3.0, if not 3.0.1 or something like that. The original HDD was 6g
-
URGENT *** Hierarchical Tree in Forms 9i *** URGENT
Hello everybody, for my company I need to build a hierarchical tree item, that will display static data over three levels. Let's say: departments, employees and employee projects. How do I fill the Item? When do I fill the Item? Where do I fill the I
-
How to handle carriage return/linefeed embedded in text field as first char
Hi, I am trying to use sqlldr to import text that is comma-separated and double quote-enclosed, but contains embedded carriage return/linefeed pairs. I have a control file which works for most cases and looks like this: LOAD DATA INFILE './foo.new' A
-
2960x - stack cables connected while switches power on. SFP ports - status unknown
Connected 2960x uplink using SFP ports both stacks and all 4 ports worked good. Remote tech connected last stack cable between first and last switch, in 2 different 2960x stacks of switches, while switches were powered on. A longer stack cable was n
-
Rename 'Organize Entries' in 'Portal Favorites' menu
I like to rename standard text 'Organize Entries' in Portal Favorites menu to something else. Does anyone have any suggestions to this problem? Thanks, Thomas