 Database crash during opening [message #148234] |
Wed, 23 November 2005 04:03  |
shadow22
Messages: 2
Registered: November 2005
|
Junior Member |
|
|
Hi, i have a big problem. My database can not start after a database crash. How can i fix the database? Which steps are nessesary? It will be no problem if there are some datas missing. I need the database working again.
Thanks for your help
The alertlog shows me the following informations:
Wed Nov 23 09:42:18 2005
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
LICENSE_MAX_USERS = 0
Starting up ORACLE RDBMS Version: 8.1.7.4.0.
System parameters with non-default values:
processes = 250
timed_statistics = TRUE
shared_pool_size = 104857600
control_files = /oracle/oradata/ABST/control01.ctl, /oracle/admin/A
BST/control02.ctl, /oracle/oradata/ABST/control03.ctl
db_block_buffers = 8192
db_block_size = 16384
compatible = 8.1.7
log_archive_start = FALSE
log_archive_dest_1 = location=/oracle/oradata/ABST/archive
log_archive_format = %t_%s.dbf
log_buffer = 163840
log_checkpoint_interval = 100000
log_checkpoint_timeout = 1800
rollback_segments = rs0, rs3, rs4, rs2, rs1, rsbig
remote_login_passwordfile= EXCLUSIVE
db_domain = world
global_names = FALSE
instance_name = ABST
service_names = ABST.world, ABST
db_name = ABST
open_cursors = 255
utl_file_dir = /oracle/utl_file_dir/ABST
job_queue_processes = 10
background_dump_dest = /oracle/admin/ABST/bdump
user_dump_dest = /oracle/admin/ABST/udump
core_dump_dest = /oracle/admin/ABST/cdump
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
SNP0 started with pid=8
SNP1 started with pid=9
SNP2 started with pid=10
SNP3 started with pid=11
SNP4 started with pid=12
SNP5 started with pid=13
SNP6 started with pid=14
SNP7 started with pid=15
SNP8 started with pid=16
SNP9 started with pid=17
Wed Nov 23 09:42:19 2005
ALTER DATABASE MOUNT
Wed Nov 23 09:42:23 2005
Successful mount of redo thread 1, with mount id 1766104063.
Wed Nov 23 09:42:23 2005
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Wed Nov 23 09:42:23 2005
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
Wed Nov 23 09:42:23 2005
Thread recovery: start rolling forward thread 1
Recovery of Online Redo Log: Thread 1 Group 5 Seq 105 Reading mem 0
Mem# 0 errs 0: /oracle/oradata/ABST/redo05a.dbf
Mem# 1 errs 0: /oracle/oradata/ABST/redo05b.dbf
Wed Nov 23 09:42:24 2005
Thread recovery: finish rolling forward thread 1
Thread recovery: 0 data blocks read, 0 data blocks written, 1 redo blocks read
Crash recovery completed successfully
Wed Nov 23 09:42:24 2005
Thread 1 advanced to log sequence 106
Thread 1 opened at log sequence 106
Current log# 1 seq# 106 mem# 0: /oracle/oradata/ABST/redo01a.dbf
Current log# 1 seq# 106 mem# 1: /oracle/oradata/ABST/redo01b.dbf
Successful open of redo thread 1.
Wed Nov 23 09:42:24 2005
SMON: enabling cache recovery
***
Corrupt block relative dba: 0x00400033 (file 1, block 51)
Bad check value found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x00400033
last change scn: 0x0000.0c5b13fb seq: 0x1 flg: 0x06
consistency value in tail: 0x13fb0601
check value in block header: 0x4d04, computed block checksum: 0x40
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of rdba: 0x00400033 (file 1, block 51) found same corrupted data
Wed Nov 23 09:42:24 2005
Errors in file /oracle/admin/ABST/udump/abst_ora_18429.trc:
ORA-00604: error occurred at recursive SQL level 2
ORA-01578: ORACLE data block corrupted (file # 1, block # 51)
ORA-01110: data file 1: '/oracle/oradata/ABST/system01.dbf'
Error 604 happened during db open, shutting down database
USER: terminating instance due to error 604
Instance terminated by USER, pid = 18429
ORA-1092 signalled during: ALTER DATABASE OPEN...
|
|
|
|
| Re: Database crash during opening [message #148263 is a reply to message #148234] |
Wed, 23 November 2005 05:42  |
ndefontenay
Messages: 14
Registered: November 2005
Location: Thailand
|
Junior Member |
|
|
Hi.
I hope you are under archive mode. I guess yes (even though it didn't start in your report).
I would try the following:
startup mount pfile= [init file path]
set autorecovery on
recover database
alter database open
I'm using oracle 8i. I don't think the changes are huge.
So try this and let me know. It worked for me after a similar crash (corrupted data) due to a bad disk.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
