Доброго времени суток.
Начну с предыстории проблемы. Ранее работали на таком софте как METIMAG, затем перешли на Супермаг. С оставшимся наследством от МЕТИ давно не работали, но периодически нужны данные. Так вот в один прекрасный день это "чудо" не запустилось. Начали смотреть что и как.
1. При открытии базы вылетает ошибка, принят конец сигнала по коммуникационному каналу.
2. Начал гуглить смотреть что и как может быть, ошибка весьма размытая и предполагает много исходов
3. полез в алерт лог и трейсы, далее их содержание:
alertme01.log:
Tue Jun 23 17:54:26 2009
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 1564
Tue Jun 23 18:08:14 2009
Starting ORACLE instance (normal)
Tue Jun 23 18:08:14 2009
Running with 1 strand for Non-Enterprise Edition
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
Running with 1 strand for Non-Enterprise Edition
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.5.0.
System parameters with non-default values:
processes = 200
timed_statistics = FALSE
shared_pool_size = 335544320
large_pool_size = 8388608
control_files = D:\METI\oracle\ME01\control01.ctl, e:\meti\oracle\ME01\control02.ctl, f:\meti\oracle\ME01\control03.ctl
db_block_size = 8192
db_cache_size = 536870912
compatible = 9.2.0.5.0
db_file_multiblock_read_count= 16
fast_start_mttr_target = 0
undo_management = AUTO
undo_tablespace = METIUNDO
undo_retention = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = ME01
utl_file_dir = *
job_queue_processes = 1
hash_join_enabled = TRUE
background_dump_dest = d:\meti\orant\rdbms\trace\ME01
user_dump_dest = d:\meti\orant\rdbms\trace\ME01
core_dump_dest = d:\meti\orant\rdbms\trace\ME01
sort_area_size = 524288
sort_area_retained_size = 262144
db_name = ME01
open_cursors = 300
star_transformation_enabled= FALSE
optimizer_index_cost_adj = 10
query_rewrite_enabled = FALSE
pga_aggregate_target = 268435456
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
CJQ0 started with pid=8
Tue Jun 23 18:08:16 2009
Oracle Data Guard is not available in this edition of Oracle.
Tue Jun 23 18:08:17 2009
/* OracleOEM */ ALTER DATABASE MOUNT
Tue Jun 23 18:08:21 2009
Successful mount of redo thread 1, with mount id 1288172625
Tue Jun 23 18:08:21 2009
Database mounted in Exclusive Mode.
Completed: /* OracleOEM */ ALTER DATABASE MOUNT
Tue Jun 23 18:08:21 2009
/* OracleOEM */ ALTER DATABASE OPEN
Tue Jun 23 18:08:22 2009
Beginning crash recovery of 1 threads
Tue Jun 23 18:08:22 2009
Started recovery at
Thread 1: logseq 30345, block 3, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 3 Seq 30345 Reading mem 0
Mem# 0 errs 0: E:\METI\ORACLE\ME01\REDO03A.LOG
Mem# 1 errs 0: F:\METI\ORACLE\ME01\REDO03B.LOG
Tue Jun 23 18:08:22 2009
Completed redo application
Tue Jun 23 18:08:22 2009
Ended recovery at
Thread 1: logseq 30345, block 119, scn 0.1017135717
47 data blocks read, 47 data blocks written, 116 redo blocks read
Crash recovery completed successfully
Tue Jun 23 18:08:23 2009
Thread 1 advanced to log sequence 30346
Thread 1 opened at log sequence 30346
Current log# 1 seq# 30346 mem# 0: E:\METI\ORACLE\ME01\REDO01A.LOG
Current log# 1 seq# 30346 mem# 1: F:\METI\ORACLE\ME01\REDO01B.LOG
Successful open of redo thread 1
Tue Jun 23 18:08:24 2009
SMON: enabling cache recovery
Tue Jun 23 18:08:24 2009
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Tue Jun 23 18:08:24 2009
SMON: enabling tx recovery
Tue Jun 23 18:08:24 2009
Database Characterset is WE8ISO8859P1
Tue Jun 23 18:08:24 2009
ORACLE Instance me01 (pid = 6) - Error 1578 encountered while recovering transaction (5, 41).
Tue Jun 23 18:08:24 2009
Errors in file d:\meti\orant\rdbms\trace\me01\me01_smon_2912.trc:
ORA-01578: ORACLE data block corrupted (file # 2, block # 30468)
ORA-01110: data file 2: 'E:\METI\ORACLE\ME01\METIUNDO_01.ORA'
Tue Jun 23 18:08:26 2009
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: /* OracleOEM */ ALTER DATABASE OPEN
Tue Jun 23 18:08:28 2009
ALTER TABLESPACE METIINDEX COALESCE
Tue Jun 23 18:08:28 2009
Completed: ALTER TABLESPACE METIINDEX COALESCE
Tue Jun 23 18:08:29 2009
Errors in file d:\meti\orant\rdbms\trace\me01\me01_pmon_3048.trc:
ORA-00474: SMON process terminated with error
Tue Jun 23 18:08:29 2009
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 3048
--
содержание трейса:
Dump file d:\meti\orant\rdbms\trace\me01\me01_pmon_3048.trc
Tue Jun 23 18:08:29 2009
ORACLE V9.2.0.5.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 4, CPU type 586
Oracle9i Release 9.2.0.5.0 - Production
JServer Release 9.2.0.5.0 - Production
Windows 2000 Version 5.0 Service Pack 4, CPU type 586
Instance name: me01
Redo thread mounted by this instance: 1
Oracle process number: 2
Windows thread id: 3048, image: ORACLE.EXE
*** 2009-06-23 18:08:29.203
*** SESSION ID:(1.1) 2009-06-23 18:08:29.187
error 474 detected in background process
ORA-00474: SMON process terminated with error
---
по поводу ORA-00474 прочитал прогнозы неутешительные для базы. Проблема в том что поддержки нет, а дамп базы тоже уже битый.
Прошу помощи и совета, можно за эту базу побороться или оставить тщетные попытки если нет бэкапа, особо с какой стороны к этой базе подходить не знаю. Если есть способы ее завести подскажите пожалуйста как, файлы БД все лежат по местам.