数据库open后两秒就自动关闭，附日志

显示全部楼层 · 2012-5-22 15:10:11

Database Characterset is ZHS16GBK
Sun Aug 09 10:48:50 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=32, OS id=2348
Sun Aug 09 10:48:50 2015
ORACLE Instance xcky (pid = 9) - Error 600 encountered while recovering transaction (4, 24).
Sun Aug 09 10:48:50 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Sun Aug 09 10:48:51 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], []
ORACLE Instance xcky (pid = 9) - Error 600 encountered while recovering transaction (6, 45) on object 63710.
Sun Aug 09 10:48:52 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], []
Sun Aug 09 10:48:52 2015
Completed: alter database open
Sun Aug 09 10:48:52 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Sun Aug 09 10:48:53 2015
ORACLE Instance xcky (pid = 9) - Error 600 encountered while recovering transaction (7, 15).
Sun Aug 09 10:48:53 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Sun Aug 09 10:48:53 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [25027], [1], [134972480], [], [], [], [], []
ORACLE Instance xcky (pid = 9) - Error 600 encountered while recovering transaction (10, 9).
Sun Aug 09 10:48:53 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [25027], [1], [134972480], [], [], [], [], []
Sun Aug 09 10:48:54 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []
Sun Aug 09 10:48:56 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_j000_2364.trc:
Sun Aug 09 10:48:57 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_j000_2364.trc:
ORA-12012: 自动执行作业 1 出错
ORA-08102: 未找到索引关键字, 对象号 239, 文件 1, 块 1674 (2)
Sun Aug 09 10:48:57 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_j000_2364.trc:
ORA-12012: 自动执行作业 1 出错
ORA-08102: 未找到索引关键字, 对象号 239, 文件 1, 块 1674 (2)
Sun Aug 09 10:48:57 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_j000_2364.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 239, 文件 1, 块 1674 (2)
ORA-12012: 自动执行作业 1 出错
ORA-08102: 未找到索引关键字, 对象号 239, 文件 1, 块 1674 (2)
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_pmon_3980.trc:
ORA-00474: SMON process terminated with error
Sun Aug 09 10:48:58 2015
PMON: terminating instance due to error 474
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_j003_3620.trc:
ORA-00474: SMON process terminated with error
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_j002_3464.trc:
ORA-00474: SMON process terminated with error
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_j000_2364.trc:
ORA-00474: SMON 进程因错误而终止
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_dbw0_3556.trc:
ORA-00474: SMON process terminated with error
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_psp0_1600.trc:
ORA-00474: SMON process terminated with error
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_mman_2744.trc:
ORA-00474: SMON process terminated with error
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_ckpt_1392.trc:
ORA-00474: SMON process terminated with error
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_lgwr_296.trc:
ORA-00474: SMON process terminated with error
Sun Aug 09 10:48:58 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_dbw1_2616.trc:
ORA-00474: SMON process terminated with error
Sun Aug 09 10:49:04 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_reco_1812.trc:
ORA-00474: SMON process terminated with error
Instance terminated by PMON, pid = 3980

日志.rar(852.51 KB, 下载次数: 9)2015-8-11 16:18 上传点击文件名下载附件

千问 · 2012-5-22 15:10:11

各位大牛帮忙看看，谢谢

千问 · 2012-5-22 15:10:11

顶上去！！！！

千问 · 2012-5-22 15:10:11

本帖最后由 moses0915 于 2015-8-11 17:21 编辑
解决的方法分为两种，
查看数据库的Undo tablespace 里面是否有活动的会话。(通过10015事件）
1、如果没有，可以直接用新的Undo tablespace，然后drop掉这个老的undo tablespace
2、如果有，看看能不能换一个
试试吧，如果好了和我留个言

千问 · 2012-5-22 15:10:11

你这个好几个问题
Sun Aug 09 10:48:52 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [4137], [], [], [], [], [], [], []

Sun Aug 09 10:48:57 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_j000_2364.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 239, 文件 1, 块 1674 (2)
ORA-12012: 自动执行作业 1 出错
ORA-08102: 未找到索引关键字, 对象号 239, 文件 1, 块 1674 (2)

un Aug 09 10:48:53 2015
Errors in file e:\oracle\product\10.2.0\admin\xcky\bdump\xcky_smon_364.trc:
ORA-00600: internal error code, arguments: [25027], [1], [134972480], [], [], [], [], []

1. undo 执行上有问题，有事务无法回滚
2. 有坏块

千问 · 2012-5-22 15:10:11

硬盘坏了么
还是回滚坏了
新建一个切换走
删除老的

千问 · 2012-5-22 15:10:11

dbv 一下 SYSTEM 的数据文件，这个东西坏了，可就麻烦了。

千问 · 2012-5-22 15:10:11

ORA-600 [4137] "XID in Undo and Redo Does Not Match" (文档 ID 43914.1)
FUNCTIONALITY:
Kernel Transaction Undo Recovery

IMPACT:

POSSIBLE PHYSICAL CORRUPTION in Rollback segments
SUGGESTIONS:
Signalled during rollback (also rollback for consistent read).
The consistency check that compares the transaction id of the
transaction being rolled back against the transaction id in
undo block being applied is failing.
A possible cause is a lost write to the undo segment.
The main approach is to identify the file containing the bad undo
segment block and treat it as if the file is corrupt. Consult
the trace file for this information.
If in archivelog mode, restore the file & roll forward.
If in Noarchivelog mode, restore from a cold backup taken before
the error was reported.

Alternatively, you can look at dba_rollback_segs data dictionary view.
If the status column that describes what state the rollback segment is
currently in is "needs recovery" then lookup the following article
for posible solution.
Note:28812.1Rollback Segment Needs Recovery
If the Known Issues section below does not help in terms of identifying
a solution, please submit the trace files and alert.log to Oracle
Support Services for further analysis.
Known Issues

千问 · 2012-5-22 15:10:11

日志哪里看出来是undo问题

千问 · 2012-5-22 15:10:11

确实undo有问题那请问哪句报错看出undo问题，我想学习下，，目前我还看不懂日志