ORA-00600 [4194] 故障处理

最新推荐文章于 2023-04-25 16:05:56 发布

数据和云

最新推荐文章于 2023-04-25 16:05:56 发布

阅读量745

点赞数

文章标签：数据库 oracle mysql 区块链知识图谱

本文链接：https://blog.csdn.net/enmotech/article/details/118686794

版权

本文详细介绍了在遇到ORA-00600 [4194] 错误时，如何通过分析问题、调整初始化参数、重建undo表空间等步骤来恢复Oracle数据库。处理过程中涉及到启动数据库到nomount状态、创建和修改pfile、限制模式启动、查询回滚段状态以及调整undo_tablespace参数等关键操作。

摘要由CSDN通过智能技术生成

点击上方"蓝字"

关注我们，享更多干货！

客户有一套测试库主机宕机，主机启动后，数据库启动报ORA-00600 [4194]，本文介绍处理过程。

1. 问题现象

启动数据库，数据进行实例恢复完成后，能成功open，但数据库在几分钟后自动宕掉，通过alert日志，可以看到宕库前报错是ORA-00600 arguments: [4194]。

alter database open
Beginning crash recovery of 1 threads
 parallel recovery started with 3 processes
Started redo scan     -----> 扫描redo，进行实例恢复
Completed redo scan
 read 149 KB redo, 107 data blocks need recovery
Started redo application at
 Thread 1: logseq 84918, block 3
Recovery of Online Redo Log: Thread 1 Group 3 Seq 84918 Reading mem 0
  Mem# 0: /data/orauser01/app/oradata/orcl/redo03.log
Completed redo application of 0.12MB      -----> 进行实例恢复完成
Completed crash recovery at
 Thread 1: logseq 84918, block 302, scn 13343268733370
 107 data blocks read, 107 data blocks written, 149 redo k-bytes read
Wed Mar 24 18:10:56 2021
Thread 1 advanced to log sequence 84919 (thread open)
Thread 1 opened at log sequence 84919
  Current log# 1 seq# 84919 mem# 0: /data/orauser01/app/oradata/orcl/redo01.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Mar 24 18:10:56 2021
SMON: enabling cache recovery
[3151] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:30524 end:30584 diff:60 (0 seconds)
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Wed Mar 24 18:10:56 2021
QMNC started with pid=23, OS id=3405 
Completed: alter database open                  -----> open成功
Wed Mar 24 18:10:57 2021
db_recovery_file_dest_size of 4182 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Wed Mar 24 18:10:57 2021
Errors in file /data/orauser01/app/oracle/diag/rdbms/orcl/chnldev/trace/chnldev_m001_3409.trc  (incident=1905820):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /data/orauser01/app/oracle/diag/rdbms/orcl/chnldev/incident/incdir_1905820/chnldev_m001_3409_i1905820.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Wed Mar 24 18:10:57 2021
Starting background process CJQ0
Wed Mar 24 18:10:57 2021
CJQ0 started with pid=26, OS id=3422 
Wed Mar 24 18:10:59 2021
Dumping diagnostic data in directory=[cdmp_20210324181059], requested by (instance=1, osid=3409 (M001)), summary=[incident=1905820].
Block recovery from logseq 84919, block 115 to scn 13343268734123
Recovery of Online Redo Log: Thread 1 Group 1 Seq 84919 Reading mem 0
  Mem# 0: /data/orauser01/app/oradata/orcl/redo01.log
Block recovery completed at rba 84919.3699.16, scn 31