ORA-00600[4193]/[4194]处理记录

2020年5月19日 1113点热度 0人点赞 0条评论

一、问题描述

1、数据库情况

版本11.2.0.4;未开启归档

2、问题详情

数据库打开时报错如下。

Tue May 19 11:04:39 2020
alter database open resetlogs
RESETLOGS is being done without consistancy checks. This may result
in a corrupted database. The database should be recreated.
RESETLOGS after incomplete recovery UNTIL CHANGE 16669337385202
Clearing online redo logfile 4 E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG
Clearing online log 4 of thread 1 sequence number 0
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_ora_3220.trc:
ORA-00367: ?????????????
ORA-00318: ?? 4 (???? 1) ??????? 512 ? 512 ???
ORA-00312: ???? 4 ?? 1: 'E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG'
Tue May 19 11:04:56 2020
Checker run found 10 new persistent data failures
Tue May 19 11:07:00 2020
Clearing online redo logfile 4 complete
Clearing online redo logfile 5 E:\APP\ADMINROOT\ORADATA\WYDB\REDO05.LOG
Clearing online log 5 of thread 1 sequence number 0
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_ora_3220.trc:
ORA-00367: ?????????????
ORA-00318: ?? 5 (???? 1) ??????? 512 ? 512 ???
ORA-00312: ???? 5 ?? 1: 'E:\APP\ADMINROOT\ORADATA\WYDB\REDO05.LOG'
Tue May 19 11:30:52 2020
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Tue May 19 12:09:03 2020
Clearing online redo logfile 5 complete
Clearing online redo logfile 6 E:\APP\ADMINROOT\ORADATA\WYDB\REDO06.LOG
Clearing online log 6 of thread 1 sequence number 0
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_ora_3220.trc:
ORA-00367: ?????????????
ORA-00318: ?? 6 (???? 1) ??????? 512 ? 512 ???
ORA-00312: ???? 6 ?? 1: 'E:\APP\ADMINROOT\ORADATA\WYDB\REDO06.LOG'
Tue May 19 12:11:31 2020
Clearing online redo logfile 6 complete
Online log E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG: Thread 1 Group 4 was previously cleared
Online log E:\APP\ADMINROOT\ORADATA\WYDB\REDO05.LOG: Thread 1 Group 5 was previously cleared
Online log E:\APP\ADMINROOT\ORADATA\WYDB\REDO06.LOG: Thread 1 Group 6 was previously cleared
Tue May 19 12:11:34 2020
Setting recovery target incarnation to 2
Initializing SCN for created control file
Database SCN compatibility initialized to 3
Tue May 19 12:11:37 2020
Assigning activation ID 1283227263 (0x4c7c7e7f)
Thread 1 opened at log sequence 1
  Current log# 4 seq# 1 mem# 0: E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue May 19 12:11:40 2020
SMON: enabling cache recovery
Tue May 19 12:11:45 2020
[3220] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:302630239 end:302631893 diff:1654 (16 seconds)
Dictionary check beginning
Tablespace 'TEMP' #3 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Tablespace 'TEMP2' #8 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Dictionary check complete
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
---
Tue May 19 12:11:51 2020
SMON: enabling tx recovery
*********************************************************************
WARNING: The following temporary tablespaces contain no files.
         This condition can occur when a backup controlfile has
         been restored.  It may be necessary to add files to these
         tablespaces.  That can be done using the SQL statement:

         ALTER TABLESPACE  ADD TEMPFILE

         Alternatively, if these temporary tablespaces are no longer
         needed, then they can be dropped.
           Empty temporary tablespace: TEMP
           Empty temporary tablespace: TEMP2
*********************************************************************
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_smon_2032.trc  (incident=227724):
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Updating character set in controlfile to ZHS16GBK
Incident details in: E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\incident\incdir_227724\wydb_smon_2032_i227724.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
No Resource Manager plan active
**********************************************************
WARNING: Files may exists in db_recovery_file_dest
that are not known to the database. Use the RMAN command
CATALOG RECOVERY AREA to re-catalog any such files.
If files cannot be cataloged, then manually delete them
using OS command.
One of the following events caused this:
1. A backup controlfile was restored.
2. A standby controlfile was restored.
3. The controlfile was re-created.
4. db_recovery_file_dest had previously been enabled and
   then disabled.
**********************************************************
Block recovery from logseq 1, block 52 to scn 16669344602820
---
Tue May 19 12:11:55 2020
Dumping diagnostic data in directory=[cdmp_20200519121155], requested by (instance=1, osid=2032 (SMON)), summary=[incident=227724].
replication_dependency_tracking turned off (no async multimaster replication found)
Recovery of Online Redo Log: Thread 1 Group 4 Seq 1 Reading mem 0
  Mem# 0: E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG
Block recovery completed at rba 1.60.16, scn 3881.576527045
Block recovery from logseq 1, block 52 to scn 16669344602820
Recovery of Online Redo Log: Thread 1 Group 4 Seq 1 Reading mem 0
  Mem# 0: E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG
Tue May 19 12:11:57 2020
Sweep [inc][227724]: completed
Sweep [inc2][227724]: completed
Block recovery completed at rba 1.60.16, scn 3881.576527045
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_smon_2032.trc:
ORA-01595: error freeing extent (8) of rollback segment (2))
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Tue May 19 12:11:58 2020
Starting background process QMNC
Tue May 19 12:11:58 2020
QMNC started with pid=20, OS id=7056 
LOGSTDBY: Validating controlfile with logical metadata
LOGSTDBY: Validation complete
Tue May 19 12:12:01 2020
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_mmon_2696.trc  (incident=227740):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\incident\incdir_227740\wydb_mmon_2696_i227740.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Dumping diagnostic data in directory=[cdmp_20200519121205], requested by (instance=1, osid=2696 (MMON)), summary=[incident=227740].
Block recovery from logseq 1, block 60 to scn 16669344602831
Recovery of Online Redo Log: Thread 1 Group 4 Seq 1 Reading mem 0
  Mem# 0: E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG
Block recovery stopped at EOT rba 1.64.16
Block recovery completed at rba 1.64.16, scn 3881.576527053
Block recovery from logseq 1, block 60 to scn 16669344602824
Recovery of Online Redo Log: Thread 1 Group 4 Seq 1 Reading mem 0
  Mem# 0: E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG
Block recovery completed at rba 1.62.16, scn 3881.576527050
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_mmon_2696.trc  (incident=227741):
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Incident details in: E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\incident\incdir_227741\wydb_mmon_2696_i227741.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Tue May 19 12:12:10 2020
Completed: alter database open resetlogs
Tue May 19 12:12:13 2020
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_q001_6668.trc  (incident=227796):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\incident\incdir_227796\wydb_q001_6668_i227796.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Tue May 19 12:12:13 2020
Dumping diagnostic data in directory=[cdmp_20200519121213], requested by (instance=1, osid=2696 (MMON)), summary=[incident=227741].
Tue May 19 12:12:15 2020
Block recovery from logseq 1, block 64 to scn 16669344602856
Recovery of Online Redo Log: Thread 1 Group 4 Seq 1 Reading mem 0
  Mem# 0: E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG
Block recovery stopped at EOT rba 1.68.16
Block recovery completed at rba 1.68.16, scn 3881.576527079
Block recovery from logseq 1, block 64 to scn 16669344602836
Recovery of Online Redo Log: Thread 1 Group 4 Seq 1 Reading mem 0
  Mem# 0: E:\APP\ADMINROOT\ORADATA\WYDB\REDO04.LOG
Block recovery completed at rba 1.66.16, scn 3881.576527062
Flush retried for xcb 0xd2b34998, pmd 0xd3017f88
Dumping diagnostic data in directory=[cdmp_20200519121217], requested by (instance=1, osid=6668 (Q001)), summary=[incident=227796].
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_q001_6668.trc  (incident=227797):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\incident\incdir_227797\wydb_q001_6668_i227797.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Dumping diagnostic data in directory=[cdmp_20200519121220], requested by (instance=1, osid=6668 (Q001)), summary=[incident=227797].
Flush retried for xcb 0xd2b34998, pmd 0xd3017f88
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_q001_6668.trc  (incident=227798):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\incident\incdir_227798\wydb_q001_6668_i227798.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Tue May 19 12:12:23 2020
Flush retried for xcb 0xd2b34998, pmd 0xd3017f88
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_q001_6668.trc  (incident=227799):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\incident\incdir_227799\wydb_q001_6668_i227799.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Flush retried for xcb 0xd2b34998, pmd 0xd3017f88
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_q001_6668.trc  (incident=227800):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Flush retried for xcb 0xd2b34998, pmd 0xd3017f88
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_q001_6668.trc  (incident=227801):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Flush retried for xcb 0xd2b34998, pmd 0xd3017f88
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_q001_6668.trc  (incident=227802):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Flush retried for xcb 0xd2b34998, pmd 0xd3017f88
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_q001_6668.trc  (incident=227803):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
opidrv aborting process Q001 ospid (6668) as a result of ORA-600
Tue May 19 12:12:34 2020
Flush retried for xcb 0xd2b34998, pmd 0xd3017f88
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_pmon_6592.trc  (incident=227636):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_pmon_6592.trc:
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
PMON (ospid: 6592): terminating the instance due to error 472
Tue May 19 12:12:35 2020
System state dump requested by (instance=1, osid=6592 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file E:\APP\ADMINROOT\diag\rdbms\wydb\wydb\trace\wydb_diag_3780_20200519121235.trc
Dumping diagnostic data in directory=[cdmp_20200519121235], requested by (instance=1, osid=6592 (PMON)), summary=[abnormal instance termination].
Tue May 19 12:12:44 2020
Instance terminated by PMON, pid = 6592

二、问题分析、处理思路

经过网搜,得知ORA-600[4193]/[4194]错误解决思路
1.修改参数
undo_management= MANUAL
undo_tablespace= SYSTEM
2.打开数据库,删除当前undo空间,重建新undo空间
3.修改参数
undo_management= AUTO
undo_tablespace= UNDOTBSNEW
4.重新启动数据库

三、处理步骤

startup mount
--先把之前设置的参数_allow_resetlogs_corruption改回正常状态
alter system set "_allow_resetlogs_corruption" = false scope=spfile;
alter system set "_allow_terminal_recovery_corruption" = false scope=spfile;
alter system set undo_management=MANUAL scope=spfile;
alter system set undo_tablespace=SYSTEM scope=spfile;
shutdown immediate
startup mount
alter database open;
create undo tablespace UNDOTBS2 datafile 'E:\APP\ADMINROOT\ORADATA\WYDB\undo01.dbf' size 2000m autoextend on;
alter system set undo_tablespace=UNDOTBS2 scope=spfile;
alter system set undo_management=auto scope=spfile;
drop tablespace UNDOTBS1 including contents and datafiles;
shutdown immediate
startup mount
alter database open;

目前的报错是临时表空间问题:
*********************************************************************
WARNING: The following temporary tablespaces contain no files.
         This condition can occur when a backup controlfile has
         been restored.  It may be necessary to add files to these
         tablespaces.  That can be done using the SQL statement:

         ALTER TABLESPACE  ADD TEMPFILE

         Alternatively, if these temporary tablespaces are no longer
         needed, then they can be dropped.
           Empty temporary tablespace: TEMP
           Empty temporary tablespace: TEMP2
*********************************************************************

create temporary tablespace temp3 tempfile 'E:\APP\ADMINROOT\ORADATA\WYDB\TEMP03.DBF' size 5000M extent management local;
drop tablespace temp including contents and datafiles;
目前默认temp2
alter database default temporary tablespace temp3;
drop tablespace temp2 including contents and datafiles;

liking

这个人很懒,什么都没留下

文章评论