Oracle database not starting
- Get link
- X
- Other Apps
I have an Oracle database(Oracle 9.2.0.1.0) running on RedHat Linux 7.2. The server has 1GB ram. The service was running in Archivelog mode.Service is set to autostart.
Recently I found on restarting the server the listener started by the service did not.
I started the service using STARTUP MOUNT and using ALTER DATABASE I stopped the archivelogs. I have posted my next few commands, kindly help me.... SQL> startup mount
ORACLE instance started.
Total System Global Area 426316116 bytes
Fixed Size 450900 bytes
Variable Size 268435456 bytes
Database Buffers 157286400 bytes
Redo Buffers 143360 bytes
Database mounted.
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: '/oracle/oradata/testdb/testdb_system01.dbf'
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 12589066 generated at 08/16/2004 20:06:55 needed for thread 1
ORA-00289: suggestion : /oracle/oradata/testdb/archive/arch_431387338_9446_1.dbf
ORA-00280: change 12589066 for thread 1 is in sequence #9446
Specify log: {=suggested | filename | AUTO | CANCEL}
/oracle/oradata/testdb/archive/arch_431387338_9446_1.dbf
ORA-00308: cannot open archived log
'/oracle/oradata/testdb/archive/arch_431387338_9446_1.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Specify log: {=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/oracle/oradata/testdb/archive/arch_431387338_9446_1.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
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: '/oracle/oradata/testdb/cstdb_system01.dbf'
Now the only thing I have not done is '_allow_resetlogs_corruption' trick, but then that is the last step, unless someone thinks up something.
Thanks in advance.
Recently I found on restarting the server the listener started by the service did not.
I started the service using STARTUP MOUNT and using ALTER DATABASE I stopped the archivelogs. I have posted my next few commands, kindly help me.... SQL> startup mount
ORACLE instance started.
Total System Global Area 426316116 bytes
Fixed Size 450900 bytes
Variable Size 268435456 bytes
Database Buffers 157286400 bytes
Redo Buffers 143360 bytes
Database mounted.
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: '/oracle/oradata/testdb/testdb_system01.dbf'
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 12589066 generated at 08/16/2004 20:06:55 needed for thread 1
ORA-00289: suggestion : /oracle/oradata/testdb/archive/arch_431387338_9446_1.dbf
ORA-00280: change 12589066 for thread 1 is in sequence #9446
Specify log: {
/oracle/oradata/testdb/archive/arch_431387338_9446_1.dbf
ORA-00308: cannot open archived log
'/oracle/oradata/testdb/archive/arch_431387338_9446_1.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Specify log: {
ORA-00308: cannot open archived log
'/oracle/oradata/testdb/archive/arch_431387338_9446_1.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
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: '/oracle/oradata/testdb/cstdb_system01.dbf'
Now the only thing I have not done is '_allow_resetlogs_corruption' trick, but then that is the last step, unless someone thinks up something.
Thanks in advance.
Sameer
Question1: did you copy your dbf after you shutdown the database?
1.Put test in archive log mode and dont forget about the arch log destination:
2. copy your redo logs from PROD server to your test databse's arch log mountpoint
3.then at svrmgr"
"recover database using backup controlfile until cancel:
when it prompts you for the arch give the current redo.
then type "cancel"
that should fix the problem
then alter database open resetlogs
if you get same error apply more redos.
1.Put test in archive log mode and dont forget about the arch log destination:
2. copy your redo logs from PROD server to your test databse's arch log mountpoint
3.then at svrmgr"
"recover database using backup controlfile until cancel:
when it prompts you for the arch give the current redo.
then type "cancel"
that should fix the problem
then alter database open resetlogs
if you get same error apply more redos.
ORA-01194: | file string needs more recovery to be consistent |
Cause: | An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file was not closed cleanly when it was last opened by the database. It must be recovered to a time when it was not being updated. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery. |
Action: | Either apply more logs until the file is consistent or restore the file from an older backup and repeat recovery. |
Comments