首页 > 应用开发 > IT综合 > 当前日志文件坏了的处理办法
数据库当前日志坏了,强制打开不能成功,求救??
处理结果
1、执行以下语句报错
SQL> alter session set events 'IMMEDIATE trace name ADJUST_SCN level 1';
ERROR:
ORA-00600: internal error code, arguments: [kcsadjn1], [], [], [], [], [], [],
[]
这个错误在metalink上查了查没有找到。
直接打开数据库还是报错
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [2662], [0], [1186518378], [0],
[1186662232], [12582914], [], []
再执行一次,还是报错
SQL> alter session set events 'IMMEDIATE trace name ADJUST_SCN level 1';
ERROR:
ORA-00600: internal error code, arguments: [2662], [0], [1186518378], [0],
[1186662232], [12582914], [], []
SQL> alter database open;
ERROR:
ORA-03113: end-of-file on communication channel
2、shutdown 和s
http://www.itpub.net/455413,1.html
环境:solaris8 ,oracle 8.1.6
没有备份和归档
机器突然掉电,数据库重新启动报错
有三个日志组,每组一个日志文件
1、
报错:
SVRMGR> alter database open;
alter database open
*
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 237640 change 1186662514 time 11/09/2005 19:58:10
ORA-00312: online log 3 thread 1: '/ora_expredo1/redo03.log'
2、
因为没有备份和归档,只有清空日志组,执行如下命令,但不能成功。
SQL> ALTER DATABASE CLEAR UNARCHIVEDLOGFILE GROUP 3 ;
*
ERROR at line 1:
ORA-01624: log 3 needed for crash recovery of thread 1
ORA-00312: online log 3 thread 1: '/ora_expredo1/redo03.log'
3、使用隐含参数_allow_resetlogs_corruption=true,强制打开
startup mount
recover database until cancel;
alter database open resetlogs;
报错:
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00603: ORACLE server session terminated by fatal error
4、重新启动数据库
SQL> startup restrict
ORACLE instance started.
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/7916042/viewspace-897784/ ,如需转载,请注明出处,否则将追究法律责任。