恢复报错ORA-01139
恢复报错ORA-01139
从oracle 10g RAC （操作系统Enterprise Linux Enterprise Linux AS release 4 64bit)，数据库版本10.2.0.4环境中将数据备份恢复到相同环境的异机。
向各位大牛请教！
在做完不完全恢复时。
recover database是正常的
RMAN> sql'alter database open resetlogs';
sql statement: alter database open resetlogs
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
ORA-01092: ORACLE instance terminated. Disconnection forced
RMAN-03009: failure of sql command on default channel at 04/28/2013 09:09:05
RMAN-11003: failure during parse/execution of SQL statement: alter database open resetlogs
ORA-01041: internal error. hostdef extension doesn't exist
ORACLE error from target database:
ORA-03114: not connected to ORACLE
接着我
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery。
警告日志如下alter.log
alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47509_8qrwzjdm_.arc'
Sun Apr 28 08:57:23 2013
Media Recovery Log /home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47509_8qrwzjdm_.arc
ORA-279 signalled during: alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47509_8qrwzjdm_.arc'...
Sun Apr 28 08:57:23 2013
alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85650_8qrwz1b1_.arc'
Sun Apr 28 08:57:23 2013
Media Recovery Log /home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85650_8qrwz1b1_.arc
ORA-279 signalled during: alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85650_8qrwz1b1_.arc'...
Sun Apr 28 08:57:31 2013
alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85651_8qrwz1hk_.arc'
Sun Apr 28 08:57:31 2013
Media Recovery Log /home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85651_8qrwz1hk_.arc
ORA-279 signalled during: alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85651_8qrwz1hk_.arc'...
Sun Apr 28 08:57:31 2013
alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47510_8qrwzjm2_.arc'
Sun Apr 28 08:57:31 2013
Media Recovery Log /home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47510_8qrwzjm2_.arc
ORA-279 signalled during: alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47510_8qrwzjm2_.arc'...
Sun Apr 28 08:57:31 2013
alter database recover cancel
Sun Apr 28 08:57:37 2013
Media Recovery Canceled
Completed: alter database recover cancel
Sun Apr 28 09:04:15 2013
alter database rename file '+DATADG/ld/redo01a.log' to '/home/backup/oradata/ld/redo1a.log'
Sun Apr 28 09:04:15 2013
Starting control autobackup
******************** WARNING ***************************
The errors during Server autobackup are not fatal, as it
is attempted after sucessful completion of the command.
However, it is recomended to take an RMAN control file
backup as soon as possible because the Autobackup failed
with the following error:
ORA-00236: snapshot operation disallowed: mounted control file is a backup
with the following error:
ORA-00236: snapshot operation disallowed: mounted control file is a backup
******************** END OF WARNING *******************
Completed: alter database rename file '+DATADG/ld/redo03a.log' to '/home/backup/oradata/ld/redo3a.log'
Sun Apr 28 09:05:32 2013
alter database rename file '+DATADG/ld/redo03b.log' to '/home/backup/oradata/ld/redo3b.log'
Starting control autobackup
******************** WARNING ***************************
The errors during Server autobackup are not fatal, as it
is attempted after sucessful completion of the command.
However, it is recomended to take an RMAN control file
backup as soon as possible because the Autobackup failed
with the following error:
ORA-00236: snapshot operation disallowed: mounted control file is a backup
******************** END OF WARNING *******************
Completed: alter database rename file '+DATADG/ld/redo03b.log' to '/home/backup/oradata/ld/redo3b.log'
Sun Apr 28 09:05:42 2013
alter database rename file '+DATADG/ld/redo04a.log' to '/home/backup/oradata/ld/redo4a.log'
Sun Apr 28 09:05:42 2013
Starting control autobackup
******************** WARNING ***************************
The errors during Server autobackup are not fatal, as it
is attempted after sucessful completion of the command.
However, it is recomended to take an RMAN control file
backup as soon as possible because the Autobackup failed
with the following error:
ORA-00236: snapshot operation disallowed: mounted control file is a backup
******************** END OF WARNING *******************
Completed: alter database rename file '+DATADG/ld/redo04a.log' to '/home/backup/oradata/ld/redo4a.log'
Sun Apr 28 09:05:50 2013
alter database rename file '+DATADG/ld/redo04b.log' to '/home/backup/oradata/ld/redo4b.log'
Starting control autobackup
******************** WARNING ***************************
The errors during Server autobackup are not fatal, as it
is attempted after sucessful completion of the command.
However, it is recomended to take an RMAN control file
backup as soon as possible because the Autobackup failed
with the following error:
ORA-00236: snapshot operation disallowed: mounted control file is a backup
Sun Apr 28 09:10:00 2013
Successful mount of redo thread 1, with mount id 2474343140
Sun Apr 28 09:10:00 2013
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Sun Apr 28 09:10:09 2013
alter database open resetlogs
ORA-1139 signalled during: alter database open resetlogs...
xx_ora_30570.trc日志如下
/opt/app/oracle/admin/ld/udump/xx_ora_30570.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /opt/app/oracle/product/10.2.0/db_1
System name: Linux
Node name: ldTest
Release: 2.6.9-67.0.0.0.1.ELsmp
Version: #1 SMP Sun Nov 18 01:06:10 EST 2007
Machine: x86_64
Instance name: ld
Redo thread mounted by this instance: 1
Oracle process number: 14
Unix process pid: 30570, image: oracle@ldTest (TNS V1-V3)
*** 2013-04-27 20:39:32.112
*** ACTION NAME:(0000005 STARTED124) 2013-04-27 20:39:32.112
*** MODULE NAME:(rman@ldTest (TNS V1-V3)) 2013-04-27 20:39:32.112
*** SERVICE NAME:() 2013-04-27 20:39:32.112
*** SESSION ID:(542.8) 2013-04-27 20:39:32.112
Control file resized from 4322 to 4412 blocks
kccrsd_append: rectype = 13, lbn = 2161, recs = 1000
*** 2013-04-27 22:47:07.275
*** ACTION NAME:(0000139 STARTED60) 2013-04-27 22:47:07.275
2013-04-27 22:47:07.275: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:07.279: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:07.279: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:07.279: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:07.279: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/system01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/system01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000140 STARTED60) 2013-04-27 22:47:07.375
2013-04-27 22:47:07.375: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:07.375: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:07.375: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:07.375: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:07.375: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/undotbs01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/undotbs01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000141 STARTED60) 2013-04-27 22:47:07.462
2013-04-27 22:47:07.462: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:07.462: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:07.462: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:07.462: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:07.462: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/sysaux01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sysaux01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000142 STARTED60) 2013-04-27 22:47:07.538
2013-04-27 22:47:07.538: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:07.538: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:07.538: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:07.538: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:07.538: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/undotbs02.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/undotbs02.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000143 STARTED60) 2013-04-27 22:47:07.603
2013-04-27 22:47:07.603: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:07.604: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:07.604: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:07.604: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:07.604: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/users01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/users01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000144 STARTED60) 2013-04-27 22:47:07.660
2013-04-27 22:47:07.660: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:07.660: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:07.660: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:07.660: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:07.660: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/sale_ix01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale_ix01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000145 STARTED60) 2013-04-27 22:47:07.741
2013-04-27 22:47:07.741: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:07.741: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:07.741: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:07.741: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:07.741: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/sale01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000146 STARTED60) 2013-04-27 22:47:07.829
2013-04-27 22:47:07.829: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:07.829: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:07.829: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:07.829: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:07.829: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/cpc01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/cpc01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000147 STARTED60) 2013-04-27 22:47:07.974
2013-04-27 22:47:07.974: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:07.974: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:07.974: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:07.974: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:07.974: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/cpc_ix01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/cpc_ix01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000148 STARTED60) 2013-04-27 22:47:08.073
2013-04-27 22:47:08.073: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.073: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.073: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.073: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.073: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/sale02.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale02.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000149 STARTED60) 2013-04-27 22:47:08.168
2013-04-27 22:47:08.168: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.168: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.168: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.168: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.168: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/sale_ix02.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale_ix02.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000150 STARTED60) 2013-04-27 22:47:08.295
2013-04-27 22:47:08.295: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.295: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.295: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.295: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.295: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/sale03.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale03.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000151 STARTED60) 2013-04-27 22:47:08.396
2013-04-27 22:47:08.396: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.396: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.396: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.396: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.396: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/sale04.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale04.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000152 STARTED60) 2013-04-27 22:47:08.488
2013-04-27 22:47:08.488: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.488: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.488: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.488: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.488: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/sale05.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale05.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000153 STARTED60) 2013-04-27 22:47:08.587
2013-04-27 22:47:08.587: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.587: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.587: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.587: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.587: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/f_data01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_data01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000154 STARTED60) 2013-04-27 22:47:08.669
2013-04-27 22:47:08.669: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.669: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.669: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.669: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.670: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/f_data02.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_data02.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000155 STARTED60) 2013-04-27 22:47:08.771
2013-04-27 22:47:08.771: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.771: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.771: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.771: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.771: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/f_ix01.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_ix01.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000156 STARTED60) 2013-04-27 22:47:08.886
2013-04-27 22:47:08.886: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.886: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.886: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.886: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.886: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/f_ix02.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_ix02.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000157 STARTED60) 2013-04-27 22:47:08.999
2013-04-27 22:47:08.999: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:08.999: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:08.999: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:08.999: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:08.999: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/f_data03.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_data03.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000158 STARTED60) 2013-04-27 22:47:09.096
2013-04-27 22:47:09.096: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:09.096: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:09.096: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:09.096: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:09.096: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/f_data04.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_data04.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
*** ACTION NAME:(0000159 STARTED60) 2013-04-27 22:47:09.150
2013-04-27 22:47:09.150: [ OCROSD]utgdv:2:ocr loc file cannot be opened
2013-04-27 22:47:09.150: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
2013-04-27 22:47:09.150: [ OCRRAW]proprinit: Could not open raw device
2013-04-27 22:47:09.150: [ default]a_init:7!: Backend init unsuccessful : [33]
2013-04-27 22:47:09.150: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
kgxgncin: CLSS init failed with status 21
ORA-19625: error identifying file +DATADG/users02.dbf
ORA-17503: ksfdopn:2 Failed to open file +DATADG/users02.dbf
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/home/backup/oradata/ld/redo1b.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/home/backup/oradata/ld/redo1a.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/home/backup/oradata/ld/redo1b.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/home/backup/oradata/ld/redo1a.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 1 open failed:313
*** 2013-04-28 09:08:35.897 3950 kcrr.c
Archiving online redo logfile /home/backup/oradata/ld/redo2b.log
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/home/backup/oradata/ld/redo2b.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 2 thread 1: '/home/backup/oradata/ld/redo2a.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/home/backup/oradata/ld/redo2b.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 2 thread 1: '/home/backup/oradata/ld/redo2a.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
logfile 2 open failed:313
*** 2013-04-28 09:08:35.898 3950 kcrr.c
Archiving online redo logfile /home/backup/oradata/ld/redo3b.log
WARNING: Archival will be performed using 2 passes.
The first pass will attempt to determine the end-of-file
of the online redo logfile. The end-of-file is determined
by identifying what is described as a "corrupt" block
header. This will be reported as an ORA-00354 error.
However, this is not really a corrupt block - it is the
end of the redo data.
The second pass will then archive the online redo logfile
using the identified end-of-file information.
请教如何解决ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery。谢谢
Hello Aman,
Sorry couldn't give all information in frustration.
Oracle version is 9.2.0.1.0 running on Red Hat 4
Actually i did TPITR and have to open database with resetlogoption recovery was successful but while opening received this error.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP NOMOUNT PFILE=/oracle/prdtpi/pfile/prdtpi;
ORACLE instance started.
Total System Global Area 798040164 bytes
Fixed Size 454756 bytes
Variable Size 478150656 bytes
Database Buffers 318767104 bytes
Redo Buffers 667648 bytes
SQL> alter database mount clone database;
SQL> RECOVER AUTOMATIC DATABASE UNTIL CHANGE 3997955 USING BACKUP CONTROLFILE;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
SQL> alter database datafile 1 online;
Database altered.
SQL> ed
Wrote file afiedt.buf
1* alter database datafile 12 online
SQL> /
Database altered.
SQL> ed
Wrote file afiedt.buf
1* alter database datafile 13 online
SQL> /
Database altered.
SQL> RECOVER AUTOMATIC DATABASE UNTIL CHANGE 3997955 USING BACKUP CONTROLFILE;
Media recovery complete.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
Similar Messages
-
ORA-27101: shared memory realm does not exist and ORA-01139: RESETLOGS
HI ALL,
After the oracle has installed on a solaries server successfully, i am unable to login into oracle database.
Below are the errors messages :
1) ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
2) Media recovery complete.
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery.
and When i try to login into oracle as root .
this is the error :
sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Feb 12 15:52:49 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ld.so.1: oracle: fatal: libskgxp10.so: open failed: No such file or directory
ERROR:
ORA-12547: TNS:lost contact
my Operating system details :
SunOS Blade3-Chassis2 5.10 Generic_142900-03 sun4v sparc SUNW,Netra-CP3060
Anyone please help me here. waiting for your reply.
Below are the ORACLE_SID Details :
1) echo $ORACLE_SID ----- > ems
2)ps -eaf | grep smon -------> ora_smon_ems
do you need any data?
Edited by: user8959150 on Feb 11, 2010 7:19 PMHi
We mostly receive this error message ( ORA-27101: shared memory realm does not exist and ORA-01139)
When our SGA_MAX_SIZE is greater than 1.7 G.b on
You again configure your sga size
and sga_max_size paramete will not greater than 1.7 G.b
Hope your database will work correctly.
for test purpose you set all your init.ora parameter
db_cache_size=512m
db_keep_cache_size=64m
db_recycle_cache_size=16m
java_pool_size=8m
large_pool_size=16m
shared_pool_size=256m
shared_pool_reserved_size=64m
sga_max_size=1600m
sga_max_size will not be grater than combination of of db_cache_size db_keep_cache_size,db_recycle_cache_sizejava_pool_size+share_pool_size+share_pool_reserved_size
Hope it will work fine.
Regard
Abdul Hameed Malik
[email protected] -
ORA-01139: RESETLOGS option only valid after an incomplete database recover
Hello All,
Can anyone please tell me what could be a reason of this error.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
Regards
VinayHello Aman,
Sorry couldn't give all information in frustration.
Oracle version is 9.2.0.1.0 running on Red Hat 4
Actually i did TPITR and have to open database with resetlogoption recovery was successful but while opening received this error.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP NOMOUNT PFILE=/oracle/prdtpi/pfile/prdtpi;
ORACLE instance started.
Total System Global Area 798040164 bytes
Fixed Size 454756 bytes
Variable Size 478150656 bytes
Database Buffers 318767104 bytes
Redo Buffers 667648 bytes
SQL> alter database mount clone database;
SQL> RECOVER AUTOMATIC DATABASE UNTIL CHANGE 3997955 USING BACKUP CONTROLFILE;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
SQL> alter database datafile 1 online;
Database altered.
SQL> ed
Wrote file afiedt.buf
1* alter database datafile 12 online
SQL> /
Database altered.
SQL> ed
Wrote file afiedt.buf
1* alter database datafile 13 online
SQL> /
Database altered.
SQL> RECOVER AUTOMATIC DATABASE UNTIL CHANGE 3997955 USING BACKUP CONTROLFILE;
Media recovery complete.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery -
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
OS Version : AIX 6.1
DB Version : 11.2.0.1
I am duplicating database and got below error:
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
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-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 02/16/2013 17:20:02
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
Process ID: 44040326
Session ID: 65 Serial number: 3
Error is because in target database undo tablespace is UNDOTBS_NEW and in auxiliary database undo tablespace name in init file is UNDOTBS. I followed the meatlink doc 433992.1 which suggest following steps to recover from above error:
1) edit the parameter UNDO_MANAGEMENT to "MANUAL"
2) start database again
3) drop the UNDO tablespace
4) recreate UNDO tablespace which matches to name in init file.
5) shutdown & start DB again.
Now, i edited init file and tried to start DB and got following error:
oracore@cph-core-db01-s $ sqlplus /nolog
SQL*Plus: Release 11.2.0.1.0 Production on Sat Feb 16 17:22:11 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 822085888 bytes
Database Buffers 3439329280 bytes
Redo Buffers 12152832 bytes
Database mounted.
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/u04/oradata/CORE/CORE_DUP/system01.dbf'I don't want to run duplicate command with correct UNDO tablespace name. Any other work around for this ?STARTUP MOUNT
RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
CANCEL
ALTER DATABASE OPEN RESETLOGS
Above option is not working for CORE_DUP, i am getting very strange error, while trying to recover i am getting very strange error as below:
oracore@cph-core-db01-s $ export ORACLE_SID=CORE_DUP
SQL*Plus: Release 11.2.0.1.0 Production on Mon Feb 18 11:17:25 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 822085888 bytes
Database Buffers 3439329280 bytes
Redo Buffers 12152832 bytes
Database mounted.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> recover database using backup controlfile until cancel;
ORA-00283: recovery session canceled due to errors
ORA-16433: The database must be opened in read/write mode.Primary database initfile:
event="10298 trace name context forever, level 32"
db_block_size=8192
db_file_multiblock_read_count=16
open_cursors=300
db_name=CORE
cursor_sharing='SIMILAR'
global_names=FALSE
diagnostic_dest=/u01/app/oracore/diag/CORE
#background_dump_dest=/u01/app/oracore/diag/rdbms/bdump
#core_dump_dest=/u01/app/oracore/diag/rdbms/cdump
#user_dump_dest=/u01/app/oracore/diag/rdbms/udump
control_files=("/u01/oradata/CORE/control01.ctl", "/u02/oradata/CORE/control02.ctl", "/u03/oradata/CORE/control03.ctl")
log_archive_dest_1='LOCATION=/u05/oradata/CORE/'
log_archive_format='CORE_%s%t%r.ARC'
job_queue_processes=10
compatible=11.2.0.1
processes=150
fast_start_mttr_target=300
filesystemio_options='SETALL'
pga_aggregate_target=500M
recyclebin='OFF'
remote_login_passwordfile='EXCLUSIVE'
session_cached_cursors=100
sga_target=4G
undo_management='AUTO'
undo_tablespace='UNDOTBS_NEW'
nls_date_format='DD-MON-RRRR'
nls_length_semantics='CHAR'initfile for CORE_DUP
event="10298 trace name context forever, level 32"
db_block_size=8192
db_file_multiblock_read_count=16
open_cursors=300
db_name=CORE_DUP
cursor_sharing='SIMILAR'
global_names=FALSE
diagnostic_dest=/u01/app/oracore/diag/CORE/CORE_DUP
control_files=("/u01/oradata/CORE/CORE_DUP/control01.ctl", "/u02/oradata/CORE/CORE_DUP/control02.ctl", "/u03/oradata/CORE/CORE_DUP/control03.ctl")
log_archive_dest_1='LOCATION=/u05/oradata/CORE/CORE_DUP/'
log_archive_format='CORE_DUP%s%t%r.ARC'
job_queue_processes=10
compatible=11.2.0.1
_compression_compatibility="11.2.0"
processes=150
fast_start_mttr_target=300
filesystemio_options='SETALL'
pga_aggregate_target=500M
recyclebin='OFF'
remote_login_passwordfile='EXCLUSIVE'
session_cached_cursors=100
sga_target=4G
undo_management='AUTO'
undo_tablespace='UNDOTBS'
nls_date_format='DD-MON-RRRR'
nls_length_semantics='CHAR'
log_file_name_convert='/CORE','/CORE/CORE_DUP'
db_file_name_convert='/CORE','/CORE/CORE_DUP'Duplicate steps are as:
oracore@cph-core-db01-s $ rman target sys/zzzz@core catalog rmantst10/zzzzz@catdb auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Mon Feb 18 15:50:00 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: CORE (DBID=913972022)
connected to recovery catalog database
connected to auxiliary database: CORE_DUP (not mounted)
RMAN> duplicate target database to CORE_DUP;
Starting Duplicate Db at 18-FEB-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=96 device type=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: SID=127 device type=DISK
contents of Memory Script:
sql clone "create spfile from memory";
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
shutdown clone immediate;
startup clone nomount;
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 838863104 bytes
Database Buffers 3422552064 bytes
Redo Buffers 12152832 bytes
contents of Memory Script:
sql clone "alter system set db_name =
''CORE'' comment=
''Modified by RMAN duplicate'' scope=spfile";
sql clone "alter system set db_unique_name =
''CORE_DUP'' comment=
''Modified by RMAN duplicate'' scope=spfile";
shutdown clone immediate;
startup clone force nomount
restore clone primary controlfile;
alter clone database mount;
executing Memory Script
sql statement: alter system set db_name = ''CORE'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set db_unique_name = ''CORE_DUP'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 838863104 bytes
Database Buffers 3422552064 bytes
Redo Buffers 12152832 bytes
Starting restore at 18-FEB-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=96 device type=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: SID=127 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1 tag=LEVEL1
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/u01/oradata/CORE/CORE_DUP/control01.ctl
output file name=/u02/oradata/CORE/CORE_DUP/control02.ctl
output file name=/u03/oradata/CORE/CORE_DUP/control03.ctl
Finished restore at 18-FEB-13
database mounted
contents of Memory Script:
set until scn 1217601;
set newname for datafile 1 to
"/u04/oradata/CORE/CORE_DUP/system01.dbf";
set newname for datafile 2 to
"/u04/oradata/CORE/CORE_DUP/sysaux01.dbf";
set newname for datafile 4 to
"/u04/oradata/CORE/CORE_DUP/users01.dbf";
set newname for datafile 5 to
"/u04/oradata/CORE/CORE_DUP/users02.dbf";
set newname for datafile 6 to
"/u04/oradata/CORE/CORE_DUP/users03.dbf";
set newname for datafile 9 to
"/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
restore
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 18-FEB-13
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00004 to /u04/oradata/CORE/CORE_DUP/users01.dbf
channel ORA_AUX_DISK_1: restoring datafile 00005 to /u04/oradata/CORE/CORE_DUP/users02.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /u04/oradata/CORE/CORE_DUP/users03.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1
channel ORA_AUX_DISK_2: starting datafile backup set restore
channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_2: restoring datafile 00001 to /u04/oradata/CORE/CORE_DUP/system01.dbf
channel ORA_AUX_DISK_2: restoring datafile 00002 to /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
channel ORA_AUX_DISK_2: restoring datafile 00009 to /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1 tag=LEVEL0
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:01:15
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1 tag=LEVEL0
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:35
Finished restore at 18-FEB-13
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 1 switched to datafile copy
input datafile copy RECID=24 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=25 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=26 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=27 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=28 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=29 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
contents of Memory Script:
set until scn 1217601;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 18-FEB-13
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u04/oradata/CORE/CORE_DUP/system01.dbf
destination for restore of datafile 00002: /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
destination for restore of datafile 00009: /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1
channel ORA_AUX_DISK_2: starting incremental datafile backup set restore
channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
destination for restore of datafile 00004: /u04/oradata/CORE/CORE_DUP/users01.dbf
destination for restore of datafile 00005: /u04/oradata/CORE/CORE_DUP/users02.dbf
destination for restore of datafile 00006: /u04/oradata/CORE/CORE_DUP/users03.dbf
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1 tag=LEVEL1
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1 tag=LEVEL1
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:01
starting media recovery
archived log for thread 1 with sequence 1718 is already on disk as file /u05/oradata/CORE/CORE_17181807276264.ARC
archived log for thread 1 with sequence 1719 is already on disk as file /u05/oradata/CORE/CORE_17191807276264.ARC
archived log for thread 1 with sequence 1720 is already on disk as file /u05/oradata/CORE/CORE_17201807276264.ARC
archived log for thread 1 with sequence 1721 is already on disk as file /u05/oradata/CORE/CORE_17211807276264.ARC
archived log for thread 1 with sequence 1722 is already on disk as file /u05/oradata/CORE/CORE_17221807276264.ARC
archived log for thread 1 with sequence 1723 is already on disk as file /u05/oradata/CORE/CORE_17231807276264.ARC
archived log for thread 1 with sequence 1724 is already on disk as file /u05/oradata/CORE/CORE_17241807276264.ARC
archived log for thread 1 with sequence 1725 is already on disk as file /u05/oradata/CORE/CORE_17251807276264.ARC
archived log for thread 1 with sequence 1726 is already on disk as file /u05/oradata/CORE/CORE_17261807276264.ARC
archived log for thread 1 with sequence 1727 is already on disk as file /u05/oradata/CORE/CORE_17271807276264.ARC
archived log for thread 1 with sequence 1728 is already on disk as file /u05/oradata/CORE/CORE_17281807276264.ARC
archived log for thread 1 with sequence 1729 is already on disk as file /u05/oradata/CORE/CORE_17291807276264.ARC
archived log for thread 1 with sequence 1730 is already on disk as file /u05/oradata/CORE/CORE_17301807276264.ARC
archived log for thread 1 with sequence 1731 is already on disk as file /u05/oradata/CORE/CORE_17311807276264.ARC
archived log for thread 1 with sequence 1732 is already on disk as file /u05/oradata/CORE/CORE_17321807276264.ARC
archived log for thread 1 with sequence 1733 is already on disk as file /u05/oradata/CORE/CORE_17331807276264.ARC
archived log for thread 1 with sequence 1734 is already on disk as file /u05/oradata/CORE/CORE_17341807276264.ARC
archived log for thread 1 with sequence 1735 is already on disk as file /u05/oradata/CORE/CORE_17351807276264.ARC
archived log for thread 1 with sequence 1736 is already on disk as file /u05/oradata/CORE/CORE_17361807276264.ARC
archived log for thread 1 with sequence 1737 is already on disk as file /u05/oradata/CORE/CORE_17371807276264.ARC
archived log for thread 1 with sequence 1738 is already on disk as file /u05/oradata/CORE/CORE_17381807276264.ARC
archived log for thread 1 with sequence 1739 is already on disk as file /u05/oradata/CORE/CORE_17391807276264.ARC
archived log for thread 1 with sequence 1740 is already on disk as file /u05/oradata/CORE/CORE_17401807276264.ARC
archived log for thread 1 with sequence 1741 is already on disk as file /u05/oradata/CORE/CORE_17411807276264.ARC
archived log for thread 1 with sequence 1742 is already on disk as file /u05/oradata/CORE/CORE_17421807276264.ARC
archived log for thread 1 with sequence 1743 is already on disk as file /u05/oradata/CORE/CORE_17431807276264.ARC
archived log for thread 1 with sequence 1744 is already on disk as file /u05/oradata/CORE/CORE_17441807276264.ARC
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=1710
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1
channel ORA_AUX_DISK_2: starting archived log restore to default destination
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1711
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1712
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1713
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1714
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1715
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1716
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1717
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1 tag=ARC_1HR
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC thread=1 sequence=1710
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC RECID=3041 STAMP=807724360
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1 tag=ARC_1HR
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:08
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC thread=1 sequence=1711
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC RECID=3042 STAMP=807724362
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC thread=1 sequence=1712
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC RECID=3043 STAMP=807724363
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC thread=1 sequence=1713
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC RECID=3044 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC thread=1 sequence=1714
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC RECID=3048 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC thread=1 sequence=1715
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC RECID=3046 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC thread=1 sequence=1716
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC RECID=3045 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC thread=1 sequence=1717
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC RECID=3047 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_17181807276264.ARC thread=1 sequence=1718
archived log file name=/u05/oradata/CORE/CORE_17191807276264.ARC thread=1 sequence=1719
archived log file name=/u05/oradata/CORE/CORE_17201807276264.ARC thread=1 sequence=1720
archived log file name=/u05/oradata/CORE/CORE_17211807276264.ARC thread=1 sequence=1721
archived log file name=/u05/oradata/CORE/CORE_17221807276264.ARC thread=1 sequence=1722
archived log file name=/u05/oradata/CORE/CORE_17231807276264.ARC thread=1 sequence=1723
archived log file name=/u05/oradata/CORE/CORE_17241807276264.ARC thread=1 sequence=1724
archived log file name=/u05/oradata/CORE/CORE_17251807276264.ARC thread=1 sequence=1725
archived log file name=/u05/oradata/CORE/CORE_17261807276264.ARC thread=1 sequence=1726
archived log file name=/u05/oradata/CORE/CORE_17271807276264.ARC thread=1 sequence=1727
archived log file name=/u05/oradata/CORE/CORE_17281807276264.ARC thread=1 sequence=1728
archived log file name=/u05/oradata/CORE/CORE_17291807276264.ARC thread=1 sequence=1729
archived log file name=/u05/oradata/CORE/CORE_17301807276264.ARC thread=1 sequence=1730
archived log file name=/u05/oradata/CORE/CORE_17311807276264.ARC thread=1 sequence=1731
archived log file name=/u05/oradata/CORE/CORE_17321807276264.ARC thread=1 sequence=1732
archived log file name=/u05/oradata/CORE/CORE_17331807276264.ARC thread=1 sequence=1733
archived log file name=/u05/oradata/CORE/CORE_17341807276264.ARC thread=1 sequence=1734
archived log file name=/u05/oradata/CORE/CORE_17351807276264.ARC thread=1 sequence=1735
archived log file name=/u05/oradata/CORE/CORE_17361807276264.ARC thread=1 sequence=1736
archived log file name=/u05/oradata/CORE/CORE_17371807276264.ARC thread=1 sequence=1737
archived log file name=/u05/oradata/CORE/CORE_17381807276264.ARC thread=1 sequence=1738
archived log file name=/u05/oradata/CORE/CORE_17391807276264.ARC thread=1 sequence=1739
archived log file name=/u05/oradata/CORE/CORE_17401807276264.ARC thread=1 sequence=1740
archived log file name=/u05/oradata/CORE/CORE_17411807276264.ARC thread=1 sequence=1741
archived log file name=/u05/oradata/CORE/CORE_17421807276264.ARC thread=1 sequence=1742
archived log file name=/u05/oradata/CORE/CORE_17431807276264.ARC thread=1 sequence=1743
archived log file name=/u05/oradata/CORE/CORE_17441807276264.ARC thread=1 sequence=1744
media recovery complete, elapsed time: 00:00:33
Finished recover at 18-FEB-13
contents of Memory Script:
shutdown clone immediate;
startup clone nomount;
sql clone "alter system set db_name =
''CORE_DUP'' comment=
''Reset to original value by RMAN'' scope=spfile";
sql clone "alter system reset db_unique_name scope=spfile";
shutdown clone immediate;
startup clone nomount;
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 838863104 bytes
Database Buffers 3422552064 bytes
Redo Buffers 12152832 bytes
sql statement: alter system set db_name = ''CORE_DUP'' comment= ''Reset to original value by RMAN'' scope=spfile
sql statement: alter system reset db_unique_name scope=spfile
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 838863104 bytes
Database Buffers 3422552064 bytes
Redo Buffers 12152832 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CORE_DUP" RESETLOGS ARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 4
MAXDATAFILES 500
MAXINSTANCES 1
MAXLOGHISTORY 2298
LOGFILE
GROUP 1 ( '/u02/oradata/CORE/CORE_DUP/redo01a.log', '/u03/oradata/CORE/CORE_DUP/redo01b.log' ) SIZE 10 M REUSE,
GROUP 2 ( '/u02/oradata/CORE/CORE_DUP/redo02a.log', '/u03/oradata/CORE/CORE_DUP/redo02b.log' ) SIZE 10 M REUSE,
GROUP 3 ( '/u02/oradata/CORE/CORE_DUP/redo03a.log', '/u03/oradata/CORE/CORE_DUP/redo03b.log' ) SIZE 10 M REUSE
DATAFILE
'/u04/oradata/CORE/CORE_DUP/system01.dbf'
CHARACTER SET AL32UTF8
contents of Memory Script:
set newname for tempfile 1 to
"/u04/oradata/CORE/CORE_DUP/temp01.dbf";
switch clone tempfile all;
catalog clone datafilecopy "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf",
"/u04/oradata/CORE/CORE_DUP/users01.dbf",
"/u04/oradata/CORE/CORE_DUP/users02.dbf",
"/u04/oradata/CORE/CORE_DUP/users03.dbf",
"/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
switch clone datafile all;
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /u04/oradata/CORE/CORE_DUP/temp01.dbf in control file
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf RECID=1 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users01.dbf RECID=2 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users02.dbf RECID=3 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users03.dbf RECID=4 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf RECID=5 STAMP=807724423
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=2 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=3 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=4 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=5 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
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-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 02/18/2013 15:53:50
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
Process ID: 3670170
Session ID: 33 Serial number: 7
oracore@cph-core-db01-s $ -
Recovery Failure in Oracle enterprise manager
Hi ,
When i tried to recover the whole database by selecting "Recover to the current time or a previous point-in-time" in Perform recovery area.
It came up with the error message as shown below.
ERROR :::::
startup mount
shutdown immediate
shutdown immediate
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jun 1 14:45:44 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> SQL> Connected.
SQL> SQL> SQL> Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> SQL> Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning option
startup mount
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jun 1 14:46:45 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> SQL> Connected to an idle instance.
SQL> SQL> ORACLE instance started.
Total System Global Area 2137886720 bytes
Fixed Size 2215064 bytes
Variable Size 1677722472 bytes
Database Buffers 452984832 bytes
Redo Buffers 4964352 bytes
Database mounted.
SQL> Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning option
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Jun 1 14:46:50 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: SPPADEV (DBID=1558297262, not open)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> run {
2> restore database until time "to_date('2010-05-20 20:00:00', 'YYYY-MM-DD HH24:MI:SS')";
3> recover database until time "to_date('2010-05-20 20:00:00', 'YYYY-MM-DD HH24:MI:SS')";
4> }
Starting restore at 01-JUN-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=452 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=3 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=32 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=62 device type=DISK
creating datafile file number=1 name=/u02/oradata/SPPADEV/system01.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/01/2010 14:46:52
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '/u02/oradata/SPPADEV/system01.dbf'
RMAN> exit;
Recovery Manager complete.
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Jun 1 14:46:52 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: SPPADEV (DBID=1558297262, not open)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 06/01/2010 14:46:53
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
RMAN> exit;
Recovery Manager complete.
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Jun 1 14:46:53 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: SPPADEV (DBID=1558297262, not open)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 06/01/2010 14:46:53
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
RMAN> exit;
Recovery Manager complete.
It will be very much grateful if some one can help me with this issue.
Thanks,
HaryI see the error: ORA-01180: can not create datafile 1
ORA-01110: data file 1: '/u02/oradata/SPPADEV/system01.dbf'
Does oracle have the rights to create that file there? -
Cannot open the database, stuck in mount mode
Someone please shed some lights on this problem.
I ran into some media failure, and ended up restoring the database from the offline whole backup.
The database is in the nonarchivelog mode (I know, it is not good), so there is no archive log files and
restore database is the only solution.
. startup mount
. restore database <== ran ok
. ALTER DATABASE CLEAR LOGFILE GROUP 1 <== ran ok
. ALTER DATABASE CLEAR LOGFILE GROUP 2 <== alter failed
ORA-01624: log 2 needed for crash recovery of instance orcl (thread 1)
Alter failed with group 2 and 3 because one was CURRENT,
and one was ACTIVE.
SQL> select group#, sequence#, members, status from v$log;
GROUP# SEQUENCE# MEMBERS STATUS
1 0 2 UNUSED
3 189 2 CURRENT
2 188 2 ACTIVE
I also tried 'alter database open resetlogs', and got:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
I don't think I can recover the datafile since there is no archive log file here.
Besides, if the restore database ran fine, why did I get SYSTEM01.DBF datafile needs media recovery message?
Right now, the database is in mount mode, and I cannot open it. How do I solve the problem with
ALTER DATABASE CLEAR LOGFILE GROUP for group 2 and 3?
Any suggestion? Thank you for the input.
The database is 11G running on Window.I would think the cold backup ran successfully. Here is the backup record:
RMAN> run {
2> shutdown immediate;
3> startup mount;
4> allocate channel c1 type disk;
5> backup as backupset database;
6> alter database open;
7> }
8>
using target database control file instead of recovery catalog
database closed
database dismounted
Oracle instance shut down
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area 535662592 bytes
Fixed Size 1348508 bytes
Variable Size 331353188 bytes
Database Buffers 197132288 bytes
Redo Buffers 5828608 bytes
allocated channel: c1
channel c1: SID=156 device type=DISK
Starting backup at 29-NOV-09
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
input datafile file number=00002 name=C:\APP\DAVECW\ORADATA\ORCL\SYSAUX01.DBF
input datafile file number=00001 name=C:\APP\DAVECW\ORADATA\ORCL\SYSTEM01.DBF
input datafile file number=00003 name=C:\APP\DAVECW\ORADATA\ORCL\UNDOTBS01.DBF
input datafile file number=00005 name=C:\APP\DAVECW\ORADATA\ORCL\EXAMPLE01.DBF
input datafile file number=00006 name=C:\APP\DAVECW\ORADATA\ORCL\INVENTORY01.DBF
input datafile file number=00004 name=C:\APP\DAVECW\ORADATA\ORCL\USERS01.DBF
channel c1: starting piece 1 at 29-NOV-09
channel c1: finished piece 1 at 29-NOV-09
piece handle=C:\APP\DAVECW\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_11_29\O1_MF_NNNDF_TAG20091129T230
632_5K6VQY0W_.BKP tag=TAG20091129T230632 comment=NONE
channel c1: backup set complete, elapsed time: 00:01:55
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel c1: starting piece 1 at 29-NOV-09
channel c1: finished piece 1 at 29-NOV-09
piece handle=C:\APP\DAVECW\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_11_29\O1_MF_NCSNF_TAG20091129T230
632_5K6VVNJR_.BKP tag=TAG20091129T230632 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:03
Finished backup at 29-NOV-09
database opened
released channel: c1
Recovery Manager complete. -
Oracle initialization in progress due to logfile corruption - startup error
Hi All!
I m using Oracle Release 9.2.0.1.0. Due to power outage, it seems that one of its Redo files is corrupt and it is not getting started. My database is running in no archive mode and I donot have any backup for my data.
I have performed the following action but in vain. Please help me to get it started.
Thanks in advance.
Muhammad Bilal
SQL*Plus: Release 9.2.0.1.0 - Production on Mon Jan 4 19:22:16 2010
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> show user
USER is "SYS"
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 135338868 bytes
Fixed Size 453492 bytes
Variable Size 109051904 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes
Database mounted.
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 88880 change 182882946 time 01/04/2010
08:33:19
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
SQL> select group#,sequence#,archived,status from v$log;
GROUP# SEQUENCE# ARC STATUS
1 911 NO CURRENT
2 909 NO INACTIVE
3 910 NO INACTIVE
SQL> alter database clear logfile group 1;
alter database clear logfile group 1
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
SQL> alter database clear unarchived logfile group 1;
alter database clear unarchived logfile group 1
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1;
ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'D:\ORACLE\ORADATA\DB\REDO01.LOG';
ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'D:\ORACLE\ORADATA\DB\REDO01.LOG';
ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
SQL> alter database clear logfile 'D:\ORACLE\ORADATA\DB\REDO01.LOG';
alter database clear logfile 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
SQL> select member,status from v$logfile;
MEMBER STATUS
D:\ORACLE\ORADATA\DB\REDO03.LOG STALE
D:\ORACLE\ORADATA\DB\REDO02.LOG
D:\ORACLE\ORADATA\DB\REDO01.LOG
SQL> alter database clear logfile 'D:\ORACLE\ORADATA\DB\REDO03.LOG';
Database altered.
SQL> alter database clear logfile 'D:\ORACLE\ORADATA\DB\REDO01.LOG';
alter database clear logfile 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
SQL> alter database clear logfile 'D:\ORACLE\ORADATA\DB\REDO02.LOG';
Database altered.
SQL> recover database until cancel;
ORA-00279: change 182763162 generated at 01/03/2010 20:00:21 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORA92\RDBMS\ARC00911.001
ORA-00280: change 182763162 for thread 1 is in sequence #911
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\DB\SYSTEM01.DBF'
ORA-01112: media recovery not started
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\DB\SYSTEM01.DBF'
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 88880 change 182882946 time 01/04/2010 08:33:19
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\DB\REDO01.LOG'
SQL> recover database until cancel;
ORA-00279: change 182882944 generated at 01/04/2010 08:33:10 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORA92\RDBMS\ARC00911.001
ORA-00280: change 182882944 for thread 1 is in sequence #911
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00308: cannot open archived log 'D:\ORACLE\ORA92\RDBMS\ARC00911.001'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00308: cannot open archived log 'D:\ORACLE\ORA92\RDBMS\ARC00911.001'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\DB\SYSTEM01.DBF'
SQL> select group#,sequence#,archived,status from v$log;
GROUP# SEQUENCE# ARC STATUS
1 911 NO CURRENT
2 0 NO UNUSED
3 0 NO UNUSED
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
SQL> ALTER SYSTEM CHECKPOINT GLOBAL;
ALTER SYSTEM CHECKPOINT GLOBAL
ERROR at line 1:
ORA-01109: database not open
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
ORA-00279: change 182763162 generated at 01/03/2010 20:00:21 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORA92\RDBMS\ARC00911.001
ORA-00280: change 182763162 for thread 1 is in sequence #911
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\DB\SYSTEM01.DBF'
ORA-01112: media recovery not started
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\DB\SYSTEM01.DBF'
---------------------------------------------------------------------------------------------------------------------------------Hi Bilal,
1)take a trace of controlfile..the file will be in udump destination
SQL>alter database backup controlfile to trace;
*2)take the whole database cold backup...IMMEDIATLY*
3) bring another pc install the same version oracle software on it
4)copy datafiles,parameterfile.listener.ora,tnsnames.ora from the backup
5)Edit the parameter file and do the necessary changes
-control files new location
-database new name
-backgrounddump destination new location
-userdump destination new location
-coredump destination new location
And save the parameterfile as init<SID>.ora and copy it to ORACLE_HOME\database directory.
5)edit the trace file u got in step one and remove everything above
STARTUP NOMOUNT
and below
CHARACTER SET XXXXXXX
Changes should be done to paths of the datafiles and logfiles(as per physical structure of new database) change reuse to set ,new database name and noresetlogs to resetlogs in that tracefile as we are not using the logs from the source database.
EG:CREATE CONTROLFILE SET DATABASE *"DG9A"* RESETLOGS
and save that file as create_ct.sql
5)Create a oracle service using ora dim utility from command prompt.
c:\ oradim -new -sid SIDNAME -intpwd fbifbi -startmode auto -pfile d:\oracle\ora81\database\initSID.ora--->what ever the name u gave in parameter file and according to your environmetn
6)do the changes in the listener.ora and tnsnames.ora as per the new machine
5)set oracle sid and log into sql
c:\set oracle_sid=sidname
c:\sqlplus “/as sysdba”
SQL>@create_ct.sql
then open database with
SQL>alter database open resetlogs;
check google if ur confused in creating control file and oracle service check for cold database cloning
Hope you will recover
Regards
Edited by: hungry_dba on Jan 5, 2010 9:34 AM -
Whole Database Online + redo log backup: How Long?
Hi gurus,
There's something I want to ask about online backup with redo log.
If i'm correct, redo log file is created everytime there's operation that change datafile right?
If i schedule this type of backup everyday, it means it will backup all datafiles, along with redo log file when transaction take places, at my pre-defined hours, right?
Then here's what i'm confused about. When will this backup process finished? Is it when all the datafiles have been backed up? Then how about the redo log files? If there are users that keep making transaction (therefore make change to datafiles), new redo log files will be created on disk, and that will prevent the backup process to finish. Then when will this cycle come to an end?
Please confirm if my grasp about oracle online backup is correct or not, and provide explanation to satisfy my curiousity.
Thanks gurus,
Edited by: Bobby Gunawan on Jan 6, 2009 10:16 AMHello Fidel,
i am feeling honored
> Keep in mind that the only thing where a DBA cannot make mistakes is restore/recovery and this depends on your backups
In general i would say you are right, but i have seen already one case where this statement is not true.
Some time ago i got a call from a colleague where his database crashed, the online redolog files were corrupted and the recovery was not working.
If you don't look really close at this point you are in trouble and can not continue the recovery. Let explain this on a example.
This demonstration is done on an oracle 10.2.0.4, but it work on every other version too.
Let's simulate a crash
SQL> shutdown abort;
Corrupt/delete a specifc redolog file
SQL> startup
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/TST/oradata/redolog/redo03.log'
ORA-27037: unable to obtain file status
Ok - so far so good, lets check the groups and files
SQL> select GROUP#, STATUS, MEMBER from v$logfile where TYPE = 'ONLINE';
GROUP# STATUS MEMBER
1 /oracle/TST/oradata/redolog/redo01.log
2 /oracle/TST/oradata/redolog/redo02.log
3 /oracle/TST/oradata/redolog/redo03.log
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 95 52428800 1 NO CURRENT 5117817 06-JAN-09
3 1 94 52428800 1 YES ACTIVE 5117814 06-JAN-09
2 1 93 52428800 1 YES ACTIVE 5112855 15-DEC-08
What's the situation?
The online redolog file of group 3 is lost/corrupted and this group is needed to perform a complete recovery (see status ACTIVE).
But you are lucky, because of this group 3 is already archived - so you can perform a complete recovery.
Now let's perform a complete recovery but with UNTIL clause (because we need to jump between the online and archived redologfiles)
SQL> recover database until cancel;
ORA-00279: change 5116194 generated at 01/06/2009 21:06:48 needed for thread 1
ORA-00289: suggestion : /oracle/TST/oraarch/TST_1_93_6b8c0516_666969185.arc
ORA-00280: change 5116194 for thread 1 is in sequence #93
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 5117814 generated at 01/06/2009 21:08:47 needed for thread 1
ORA-00289: suggestion : /oracle/TST/oraarch/TST_1_94_6b8c0516_666969185.arc
ORA-00280: change 5117814 for thread 1 is in sequence #94
ORA-00278: log file '/oracle/TST/oraarch/TST_1_93_6b8c0516_666969185.arc' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 5117817 generated at 01/06/2009 21:08:51 needed for thread 1
ORA-00289: suggestion : /oracle/TST/oraarch/TST_1_95_6b8c0516_666969185.arc
ORA-00280: change 5117817 for thread 1 is in sequence #95
ORA-00278: log file '/oracle/TST/oraarch/TST_1_94_6b8c0516_666969185.arc' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/oracle/TST/oradata/redolog/redo01.log
Log applied.
Media recovery complete.
Now execute an OPEN NORESETLOGS accidentally (maybe the dba think it is not necessary because of the complete recovery) and try an OPEN RESETLOGS after:
SQL> alter database open noresetlogs;
alter database open noresetlogs
ERROR at line 1:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/TST/oradata/redolog/redo03.log'
ORA-27037: unable to obtain file status
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
So now you are lost.. you can't execute an UNTIL CANCEL anymore which would be needed to perform a successful OPEN RESETLOGS.
In this special case you can do mistakes and you have to restore the whole database and perform the same recovery again and end with OPEN RESETLOGS.
Just for information
Regards
Stefan -
How to recover from corrupt redo log file in non-archived 10g db
Hello Friends,
I don't know much about recovering databases. I have a 10.2.0.2 database with corrupt redo file and I am getting following error on startup. (db is non archived and no backup) Thanks very much for any help.
Database mounted.
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 6464 change 9979452011066 time 06/27/2009
15:46:47
ORA-00312: online log 1 thread 1: '/dbfiles/data_files/log3.dbf'
====
SQL> select Group#,members,status from v$log;
GROUP# MEMBERS STATUS
1 1 CURRENT
3 1 UNUSED
2 1 INACTIVE
==
I have tried this so far but no luck
I have tried following commands but no help.
SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 3;
Database altered.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 6464 change 9979452011066 time 06/27/2009
15:46:47
ORA-00312: online log 1 thread 1: '/dbfiles/data_files/log3.dbf'user652965 wrote:
Thanks very much for your help guys. I appreciate it. unfortunately none of these commands worked for me. I kept getting error on clearing logs that redo log is needed to perform recovery so it can't be cleared. So I ended up restoring from earlier snapshot of my db volume. Database is now open.
Thanks again for your input.And now, as a follow-up, at a minimum you should make sure that all redo log groups have at least 3 members. Then, if you lose a single redo log file, all you have to do is shutdown the db and copy one of the good members (of the same group as the lost member) over the lost member.
And as an additional follow-up, if you value your data you will run in archivelog mode and take regular backups of the database and archivelogs. If you fail to do this you are saying that your data is not worth saving. -
Open database if an active online redo log is missing
Hi,
Sorry for the rather long post, but I specified all the steps I performed and couldn't make it shorter :-(
I need an advice on how to open the database if an active online redo log is missing.
For test purposes I intentionally performed a shutdown abort when the redo log group 1 was in active state and then renamed its only member (REDO01.LOG) so that the database couldn't perform crash recovery using it. Then upon startup I obviously got the message:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.Ok, so I checked the state of the logs:
{noformat}
SQL>SELECT a.GROUP#, first_change#, SEQUENCE#, a.status, SUBSTR(b.MEMBER, 1, 40) MEMBER, b.status mem_status, a.archived
2 FROM v$log a, v$logfile b
3 WHERE a.GROUP# = b.GROUP#
4 ORDER BY a.GROUP#, b.MEMBER;
GROUP# FIRST_CHANGE# SEQUENCE# STATUS MEMBER MEM_STA ARC
1 592134 29 ACTIVE H:\ORADATA\TESTDB\REDO01.LOG YES
2 592268 30 CURRENT C:\ORADATA\TESTDB\REDO02.LOG NO
3 592129 28 ACTIVE C:\ORADATA\TESTDB\REDO03.LOG YES
{noformat}Since opening the database to perform a log switch and thus change the status of the redo log group 1 from ACTIVE to INACTIVE to recreate the member isn't possible, I performed database recovery.
SQL>recover database until cancel;
ORA-00279: change 592129 generated at 02/04/2009 10:31:15 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_%U_.ARC
ORA-00280: change 592129 for thread 1 is in sequence #28
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 592134 generated at 02/04/2009 10:31:28 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_%U_.ARC
ORA-00280: change 592134 for thread 1 is in sequence #29
ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_4RLR3JS9_.ARC' no longer needed for this rec
overy
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC'
ORA-00279: change 592268 generated at 02/04/2009 10:32:03 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_30_%U_.ARC
ORA-00280: change 592268 for thread 1 is in sequence #30
ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC' no longer needed for this rec
overy
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'C:\ORADATA\TESTDB\REDO02.LOG'
Log applied.
Media recovery complete.
SQL>So for log sequence #28 I accepted the proposed archived redo log in the FRA, for sequence #29 (that's the online redo log that is missing!) I manually specified its archived copy, and for sequence #30 I specified the CURRENT online redo log. And as it seems the media recovery was successful.
Next I tried to open the database but again got the error:
SQL>alter database open noresetlogs;
alter database open noresetlogs
ERROR at line 1:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
The status of the log groups and its members is exactly as it was in the first query I wrote above, i.e. the redo log group 1 is still ACTIVE, so it's needed for crash recovery (which I had already done manually if I understand correctly how Oracle works!). I also checked if the datafiles are inconsistent (described in metalink doc id 1015544.102):
SQL>SELECT DISTINCT CHECKPOINT_CHANGE#, FUZZY FROM V$DATAFILE_HEADER;
CHECKPOINT_CHANGE# FUZ
592269 NOSo, everything seems ok as far as datafile consistency is concerned.
My question is: how can I rename/drop/clear/whatever the member of redo log group 1 to open the database?
I tried to rename the log file member, to add another member to it, to open the database with resetlogs, to clear the logfile group 1, but all without success:
1)
SQL>alter database clear logfile group 1;
alter database clear logfile group 1
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of instance testdb (thread 1)
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
2)
SQL>alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
3)
SQL>alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG';
alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG'
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01512: error renaming log file H:\ORADATA\TESTDB\REDO01.LOG - new file C:\ORADATA\TESTDB\REDO01.LOG not found
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
4)
SQL>alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1;
alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1
ERROR at line 1:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.Sorry again for the long post and thank you in advance for any suggestion.
Regards,
JureYou could check if the recovery was complete by (re)creating the controlfile with the resetlogs option.
<CREATE CONTROLFILE REUSE DATABASE define_db_name RESETLOGS NOARCHIVELOG
...>Thanks for the hint. If possible, could you only check if the steps I'm going to perform are ok.
I did an "alter database backup controlfile to trace;" and then extracted the create controlfile definition part. So in essence I should run the following statements:
CREATE CONTROLFILE REUSE DATABASE "TESTDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 'C:\ORADATA\TESTDB\REDO01.LOG' SIZE 20M,
GROUP 2 'C:\ORADATA\TESTDB\REDO02.LOG' SIZE 20M,
GROUP 3 'C:\ORADATA\TESTDB\REDO03.LOG' SIZE 20M
-- STANDBY LOGFILE
DATAFILE
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF'
CHARACTER SET EE8MSWIN1250
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\TEMP01.DBF' REUSE;Is that correct?
About the RMAN backups: Wouldn't a 'CATALOG RECOVERY AREA' populate the controlfile with backup information again (I'm not using a recovery catalog in this case)?
Thanks for the help!
Regards,
Jure -
Hello I have 817 database on Solaris and I do not have cold back up of the db. The db is in NOARCHIVE mode. I tried to bounce the db but I cannot open the db as I get the following error:
ORA-00355: change numbers out of order
ORA-00353: log corruption near block 2 change 9224405 time 06/05/2006 18:42:20
ORA-00312: online log 3 thread 1: '/u01/oradata/etpdb1/redo03.log'
Here is more info:
SVRMGR> select * from V$logfile;
GROUP# STATUS MEMBER
1 /u01/oradata/etpdb1/redo01.log
2 /u01/oradata/etpdb1/redo02.log
3 /u01/oradata/etpdb1/redo03.log
SVRMGR> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHAN FIRST_TIM
1 1 0 5242880 1 YES UNUSED 0
2 1 0 5242880 1 YES UNUSED 0
3 1 1401 5120000 1 NO CURRENT 9223256 05-JUN-06
SVRMGR> alter database open resetlogs;
alter database open resetlogs
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
Can anyone advise what can I do not to recover the db. ThanksNO ArchiveLog -- Online Redo Log corrupted.
if you have multiplexing enabled copy the redo log of the other member
and then see if db would open with that.
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14192/strategy002.htm#sthref122
Your case is probably
-> Whether the lost redo log group was current
You have very limited option other than to go back to what ever backups you have.
Engage oracle support is the best option as they may suggest other alternatives, there is a parameter ALLOWRESETLOGS_CORRUPTION but it has serious limitations check with Oracle first.
http://www.sidibe.net/allow_resetlog.html
Good Luck -
Database restore problem with BRTOOLS
Hi Experts,
I am tring to migrate an SAP system from host A to host B.
OS: windows server 2003 DB: oracle 10g
Homogeneous migration.
The database were backed up with BRTOOLS (whole database offline backup) to Location L:\QCO_BCK @hostA
After that I moved folder QCO_BCK together with folder "sapbackup" from hostA to hostB, placed under F:\QCO_BCK
And then start to perform "whole database reset" with BRTOOLS, but BRTOOLS can not verify the datafile/control files since they are under different location(hostA and hostB), So, I modified initQCO.ora and the BRTOOLS log file begprhrg.afd, all the relevant directories were changed from L:\ to F:\, after trying again, BRTOOLS performed well, all datafiles, redo logs, control files were copied to the right location, but problems encountered at step 7 - "open database and post-processing", BRTOOLS returns oracle error message:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'H:\oracle\QCO\sapdata5\system_1\SYSTEM.DATA1'
database can be mounted but can not be open.
I think this is because the control file is the old one which records the old file locations in hostA, in hostA, file SYSTEM.DATA1 actually located under H:\ but in hostB, it is copied under D:\
My question is:
1. Is it obligatory by BRTOOLS that the file structure on hostB(new) must be totally the same as hostA(old)? if the file (for example) SYSTEM.DATA1 is located at H:\ of hostA, then, in new hostB, it must be located at the same directory H:\?
2. Is there any workaround to open the database in this situation? like modifing the control file?
Thank you in advance.
FreshmanHi Sunny and Juan,
Thanks so much for your valuable information for me.
Yes, before restoring the DB, I used oraBRCopy tool to generate CONTROL.SQL and CONTROL.TRC file. But I didn't execute CONTROL.SQL after that. I'd like to know which timepoint should I execute it to generate the new control file? (file directory had already been corrected within CONTROL.SQL). is it before doing step 7: open database and post-processing, I should open a new command windows to enter SQLPlus to execute CONTROL.SQL? I tried to do this:
SQL>conn / as sysdba
Connected to an idle instance.
SQL>@C:\CONTROL.SQL
Oracle instance started
Total system global area xxx bytes
Fixed size xxx
varianble size xxx
Control file created.
SQL>alter database open;
alter database open
Error at line 1
ORA-01589 must use RESETLOGS or NORESETLOGS option for database open.
SQL>alter databse open resetlogs;
Error at line 1
ORA-01092: oracle instance terminated.Disconnected forced.
Strange thing is, in my last trial, when I execute step 7: open database and post processing, BRRECOVER gives me two sub options:
1 ~ Reset logs option (reset_logs) ..[resetlogs]
2 * Open databse command (command) .[alter database open resetlogs]
the final result is:
ORA-01139: Resetlogs option only valid after and incomplete database recovery.
I am not familiar with oracle db and is totally confused/frastrated now... Please kindly help.
Thank you very much
Freshman -
Alter database open resetlogs upgrade ; throwing error
Recently i have cloned a database from 11.2.0.2 to 11.2.0.3 on a new server.... I got the error as fowwos,
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
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-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 07/12/2012 16:19:24
RMAN-05501: aborting duplication of target database
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
Process ID: 29247
Session ID: 200 Serial number: 5
So i have tried
SQL> alter database open resetlogs upgrade;
alter database open resetlogs upgrade
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> alter database open upgrade;
alter database open upgrade
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '+DATA_CMX/cmx/datafile/system.270.788451975'
Any help ?Hi,
Duplicate is not supported using different version of database, so I recommend you don't use duplicate.
Because RMAN "duplicate" attempts to automatically rename (rename required recover) and open the database you may not use RMAN duplicate for this case, only RMAN restore.
Perform this work using normal restore database.
See this example.
On prod database with db_name/db_unique_name dbupg:
Recovery Manager: Release 11.2.0.2.0 - Production on Fri Jul 13 15:15:59 2012
RMAN> backup database plus archivelog delete input;
Starting backup at 13-JUL-12
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=52 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=17 RECID=1 STAMP=788540852
input archived log thread=1 sequence=18 RECID=2 STAMP=788541371
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151612_800shf7w_.bkp tag=TAG20120713T151612 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_17_800rz40y_.arc RECID=1 STAMP=788540852
archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_18_800shcsd_.arc RECID=2 STAMP=788541371
Finished backup at 13-JUL-12
Starting backup at 13-JUL-12
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=00001 name=+DS8000_DG/dbupg/datafile/system.271.788537119
input datafile file number=00002 name=+DS8000_DG/dbupg/datafile/sysaux.272.788537167
input datafile file number=00003 name=+DS8000_DG/dbupg/datafile/undotbs1.273.788537199
input datafile file number=00004 name=+DS8000_DG/dbupg/datafile/users.275.788537229
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:35
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 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncsnf_TAG20120713T151614_800sjm29_.bkp tag=TAG20120713T151614 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 13-JUL-12
Starting backup at 13-JUL-12
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=19 RECID=3 STAMP=788541412
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151652_800sjnf7_.bkp tag=TAG20120713T151652 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_19_800sjn5q_.arc RECID=3 STAMP=788541412
Finished backup at 13-JUL-12
RMAN> backup current controlfile;
Starting backup at 13-JUL-12
using channel ORA_DISK_1
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
channel ORA_DISK_1: starting piece 1 at 13-JUL-12
channel ORA_DISK_1: finished piece 1 at 13-JUL-12
piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp tag=TAG20120713T153435 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 13-JUL-12I used same server to do this work... I really dont recommend that, if yes you must be aware about location of restore... you should use new server:
Create a spfile:
*.control_files='+DS8000_DG/dbclone/controlfile/Current.277.788541913'
*.db_name='dbupg'
*.db_unique_name='dbclone'
*.audit_file_dest='/u01/app/oracle/admin/dbclone/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.db_block_size=8192
*.db_create_file_dest='+MMC'
*.db_domain=''
*.db_recovery_file_dest_size=107374182400
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area01'
*.diagnostic_dest='/u01/app/oracle'
*.log_file_name_convert='+DS8000_DG','+MMC'
*.memory_target=1031798784
*.open_cursors=300Make backup available on new server:
and:
SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:33:24 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 1027182592 bytes
Fixed Size 2227936 bytes
Variable Size 599785760 bytes
Database Buffers 419430400 bytes
Redo Buffers 5738496 bytes
SQL> show parameter db_n
NAME TYPE VALUE
db_name string dbupg
SQL> show parameter db_un
NAME TYPE VALUE
db_unique_name string dbclone
RMAN> restore controlfile from '/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp';
Starting restore at 13-JUL-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=290 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
output file name=+DS8000_DG/dbclone/controlfile/current.277.788541913
Finished restore at 13-JUL-12
RMAN> startup mount
database is already started
database mounted
released channel: ORA_DISK_1
RMAN> run {
2> SET NEWNAME FOR DATABASE TO '+MMC';
3> restore database ;
4> }
executing command: SET NEWNAME
Starting restore at 13-JUL-12
Starting implicit crosscheck backup at 13-JUL-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=290 device type=DISK
Crosschecked 4 objects
Finished implicit crosscheck backup at 13-JUL-12
Starting implicit crosscheck copy at 13-JUL-12
using channel ORA_DISK_1
Crosschecked 2 objects
Finished implicit crosscheck copy at 13-JUL-12
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to +MMC
channel ORA_DISK_1: restoring datafile 00002 to +MMC
channel ORA_DISK_1: restoring datafile 00003 to +MMC
channel ORA_DISK_1: restoring datafile 00004 to +MMC
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp
channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
Finished restore at 13-JUL-12
RMAN> recover database;
Starting recover at 13-JUL-12
using channel ORA_DISK_1
starting media recovery
media recovery complete, elapsed time: 00:00:01
Finished recover at 13-JUL-12So, just startup with upgrade option.
SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:39:31 2012
SQL> alter database open resetlogs upgrade; Now you can upgrade your database.
After upgrade database you can change the database name using NID:
$ nid
DBNEWID: Release 11.2.0.3.0 - Production on Fri Jul 13 15:50:23 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Keyword Description (Default)
TARGET Username/Password (NONE)
DBNAME New database name (NONE)
LOGFILE Output Log (NONE)
REVERT Revert failed change NO
SETNAME Set a new database name only NO
APPEND Append to output log NO
HELP Displays these messages NOHTH,
Levi Pereira
Edited by: Levi Pereira on Jul 13, 2012 4:04 PM -
RMAN-01009: syntax error: found "cancel"
Hi!
I am playing with rman on my test machine and I encountered error that I can't resolve.
I've tried to restore/recover datafiles executing this commands:
$ sqlplus "/as sysdba"
SQL>startup mount
RMAN> restore database
(everything went well)
RMAN> recover database until cancel;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "cancel": expecting one of: "logseq, scn, sequence, time"
RMAN-01007: at line 1 column 24 file: standard input
I've executed this command on several occasions and never had a problem, but now syntax error.
Just don't know why syntax error?!
OS: Centos 5
DB: 11.1.0.7.0
Thanks for any help,
MarkoRMAN> alter database recover database using backup controlfile until cancel;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "recover": expecting one of: "mount, open"
RMAN-01007: at line 1 column 16 file: standard input
RMAN> recover database;
Starting recover at 05-FEB-09
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/05/2009 00:11:30
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oradata/testdb/redo/testdb/onlinelog/o1_mf_3_4qfwj5fn_.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
I am trying to execute:
RMAN> sql 'alter database open resetlogs';
sql statement: alter database open resetlogs
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 02/05/2009 00:09:18
RMAN-11003: failure during parse/execution of SQL statement: alter database open resetlogs
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
This is the reason why I am trying to execute cancel-based recovery. -
I have done a stupid thing, and deleted the online redo logs.
We are running 8.1.6 on Linux RH7, and I managed to reinstate the files and they appear to be OK. That is, I managed to 'undelete' all of the online and archived logs EXCEPT for the current one. When I try to start the DB, the following happens :
SVRMGR> startup force
ORACLE instance started.
Total System Global Area 150523888 bytes
Fixed Size 69616 bytes
Variable Size 133505024 bytes
Database Buffers 16777216 bytes
Redo Buffers 172032 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SVRMGR> alter database open resetlogs;
alter database open resetlogs
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SVRMGR> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: '/u05/tmp/redo_backup_01.log'
SVRMGR> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHAN FIRST_TIM
1 1 2500 512000 1 NO CURRENT 339758 15-DEC-00
2 1 0 512000 1 YES UNUSED 0 15-DEC-00
3 1 2499 512000 1 YES INACTIVE 339048 15-DEC-00
3 rows selected.
The problem is that the current sequence is 2500, but doing a strings on the log file 1 shows that it is still pointing to sequence 2497.
I could not find a sequence 2500 in any of the deleted files.
Instead of attempting recovery, I am now trying to bring the DB up even if the data is corrupt. Is there any way to do this?
Any assistance would be greatly appreciated.
TIA
Dalebecause your database files have a different SCN or fuzzy bit set, the files must be recovered to the last consistent state. because of your witchcraft with the redologfiles, the server cannot find what it wants to do the recovery. There is a way to open the database, but only to make an export and drop the datbase, because consistency can NOT be guaranteed.
** DO THIS AT YOUR OWN RISC **
** THIS IS NOT SUPPORTED BY ORACLE **
put the following line in the init.ora file of your datbase:
allowresetlogs_corruption=true
and start the datbase. the database will open now. make an export of all relevant data, and drop the database (!!)
not only your data can be corrupted, but internal oracle data also. this is why you must drop the database when you've made your export.
null
Maybe you are looking for
-
Digital AV Adapter and iPod Touch
I bought an Apple Digital AV Adapter, and I've been a big disappointment. I connected my iPod Touch 4G with an HDMI cable and my Sony Led TV and ... only see videos from iTunes and my photos and home movies, why not games and other applications? Is i
-
Possible to execute custom SQL query?
Is it possible to execute a custom SQL query and get back a collection of objects with Kodo JDO? Query expression languages like JDOQL are all very well (I actually think JDOQL is pretty messy), but sometimes when you've got a complex query (and you
-
Anyone know what can cause the MXI-3 and PXI-1010 chassis to prevent PC bootup?
Situation: The PC locked up with the display blank. The PC would not bootup (not even POST) after power was cycled (several attempts). Resolution: Simple. The chassis power was cycled and the PC was fully operational. Background: The PC is a Dell Dim
-
When we configure copy controls we have a field "COPY QUANTITY" this is left blank when copying from sales order to another sales order, from QT to OR we make +ve and from contract to Return we make it -ve. Can anybody explain me the logic behind th
-
Raw fine tuning not working in slideshows
Hi, Does anyone know why when I adjust the de-noise level of an image in Raw Fine Tuning and then use that image in a slideshow why the adjustment is not applied to the image shown in the slideshow? I've tried regenerating the preview but it didn't m