Oracle数据库系统回滚段异常处理-ORA-600 4137/4193---惜分飞-港品优选

最初是由于数据库sysaux文件无法正常恢复,重建ctl抛弃sysaux文件,然后打开数据库,但是无法expdp导出数据

Export: Release 12.2.0.1.0 - Production on Wed Jun 24 17:18:04 2026

Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

ORA-31626: job does not exist

ORA-31637: cannot create job SYS_EXPORT_SCHEMA_02foruser SYS

ORA-06512: at"SYS.KUPV$FT", line 1140

ORA-06512: at"SYS.KUPV$FT", line 1741

ORA-06512: at"SYS.DBMS_SYS_ERROR", line 95

ORA-06512: at"SYS.KUPV$FT_INT", line 823

ORA-39080: failed to create queues"KUPC$C_1_20260624171804"and""forData Pump job

ORA-06512: at"SYS.DBMS_SYS_ERROR", line 95

ORA-06512: at"SYS.KUPC$QUE_INT", line 1541

ORA-00376:file3 cannot bereadat thistime

ORA-06512: at"SYS.DBMS_AQADM", line 742

ORA-06512: at"SYS.DBMS_AQADM_SYS", line 8060

ORA-01110: datafile3:'/u01/app/oracle/product/12.2.0.1/dbhome_2/dbs/MISSING00003'

ORA-06512: at"SYS.DBMS_AQADM_SYSCALLS", line 912

ORA-06512: at"SYS.DBMS_AQADM_SYS", line 8036

ORA-06512: at"SYS.DBMS_AQADM", line 737

ORA-06512: at"SYS.KUPC$QUE_INT", line 1461

ORA-06512: at line 1

ORA-06512: at"SYS.KUPC$QUEUE_INT", line 158

ORA-06512: at"SYS.KUPV$FT_INT", line 758

ORA-06512: at"SYS.KUPV$FT", line 1645

ORA-06512: at"SYS.KUPV$FT", line 1101

然后通过各方人员一顿操作猛如虎,导致数据库启动报ORA-600 4137和ORA-600 4193错误,数据库无法open成功

2026-06-24T18:38:50.158906+08:00

alter databaseopen

2026-06-24T18:38:50.182720+08:00

Ping without log force is disabled:

instance mountedinexclusive mode.

2026-06-24T18:38:50.219449+08:00

…………

2026-06-24T18:38:50.514016+08:00

ARC3: Archival started

ARCH: STARTING ARCH PROCESSES COMPLETE

Errorsinfile/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_48840.trc (incident=304968):

ORA-00600: internal error code, arguments: [4137], [0.77.1546], [0], [0], [], [], [], [], [], [], [], []

Incident detailsin:/u01/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_304968/orcl1_ora_48840_i304968.trc

Use ADRCI or Support Workbench to package the incident.

ORACLE Instance orcl1 (pid = 53) - Error 600 encounteredwhilerecovering transaction (0, 77).

2026-06-24T18:38:51.313973+08:00

Errorsinfile/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_48840.trc:

ORA-00600: internal error code, arguments: [4137], [0.77.1546], [0], [0], [], [], [], [], [], [], [], []

2026-06-24T18:38:51.649361+08:00

Errorsinfile/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_48840.trc (incident=304969):

ORA-00600: internal error code, arguments: [4193], [1112], [1122], [], [], [], [], [], [], [], [], []

Incident detailsin:/u01/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_304969/orcl1_ora_48840_i304969.trc

2026-06-24T18:38:53.412782+08:00

opiodr aborting process unknown ospid (48840) as a result of ORA-603

需要open故障库,并且正常导出数据,需要处理两个问题
1. 被抛弃的sysaux文件需要正常online起来，不然expdp无法正常导出用户或者全库数据
2. 需要解决open过程的ORA-600 4137/ORA-600 4193错误
对于sysaux文件进行检查，由于重建ctl没有包含异常的sysaux文件，因此无法直接从库中查询到当前各种文件头相关情况,通过obet直接解析文件头获取相关信息(Oracle数据块编辑工具( Oracle Block Editor Tool)-obet)

对于这种情况，可以使用obet的修改文件头checkpoint scn和resetlogs scn功能进行快速修复

OBET>setfile2

filenamesetto:/u02/app/oracle/oradata/PYJHYSYS/PYJHYSYS/datafile/o1_mf_sysaux_go991cmw_.dbf (file#2)

OBET> backup

Created backup directory: backup_blk

Successfully backed up block 1 from currentfileto/tmp/backup_blk/o1_mf_sysaux_go991cmw_.dbf_1.20260624191357

OBET> copy chkscnfile1 tofile2

Error: Edit mode not enabled. Use'set mode edit'first.

OBET>setmode edit

modesetto: edit

OBET> copy chkscnfile1 tofile2

Confirm Modify chkscn:

Source:file#1 (/u02/app/oracle/oradata/PYJHYSYS/PYJHYSYS/datafile/o1_mf_system_go990lcg_.dbf)

Target:file#2 (/u02/app/oracle/oradata/PYJHYSYS/PYJHYSYS/datafile/o1_mf_sysaux_go991cmw_.dbf)

Proceed? (Y/YESto confirm):yes

Successfully copied checkpoint SCN information fromfile#1 to file#2.

OBET> copy resetlogscnfile1 tofile2

Confirm Modify resetlogscn:

Source:file#1 (/u02/app/oracle/oradata/PYJHYSYS/PYJHYSYS/datafile/o1_mf_system_go990lcg_.dbf)

Target:file#2 (/u02/app/oracle/oradata/PYJHYSYS/PYJHYSYS/datafile/o1_mf_sysaux_go991cmw_.dbf)

Proceed? (Y/YESto confirm):yes

Successfully copied resetlog SCN information fromfile#1 to file#2.

OBET>sum

Check valueforFile/u02/app/oracle/oradata/PYJHYSYS/PYJHYSYS/datafile/o1_mf_sysaux_go991cmw_.dbf, Block 1:

current = 0xF21B, required = 0x6651

OBET>sumapply

Confirm applying checksum:

File:/u02/app/oracle/oradata/PYJHYSYS/PYJHYSYS/datafile/o1_mf_sysaux_go991cmw_.dbf

Block: 1

Offsetinblock: 16 (fileoffset: 0x00002010)

Original value: 0xF21B

New value: 0x6651

Confirm? (Y/YESto proceed): y

Verification successful: Stored checksum matches calculated value (0x6651).

Checksum applied successfully.

OBET> tailchk

Check tailchkforFile/u02/app/oracle/oradata/PYJHYSYS/PYJHYSYS/datafile/o1_mf_sysaux_go991cmw_.dbf, Block 1:

current = 0x010B0000, required = 0x010B0000

OBET>

然后重建ctl，包含该sysaux，尝试打开数据库,报ORA-600 4193错误

SYS@ORCL>alterdatabaseopen;

alterdatabaseopen

*

ERRORatline 1:

ORA-00603: ORACLE server session terminatedbyfatal error

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00607: Internal error occurred while making a changetoa data block

ORA-00600: internal error code, arguments: [4193], [1112], [1122], [], [], [], [], [], [], [], [], []

Process ID: 93550

Session ID: 1123 Serial number: 55884

进一步跟踪启动过程，确认报错在update undo$上

PARSING IN CURSOR

#140446136869016

len=160 dep=1 uid=0 oct=6 lid=0 tim=3161302405543 hv=1292341136 ad='9bbd4828'sqlid='8vyjutx6hg3wh'

update /*+ rule */ undo$setname=:2,file#=:3,block#=:4,status$=:5,user#=:6,undosqn=:7,

xactsqn=:8,scnbas=:9,scnwrp=:10,inst#=:11,ts#=:12,spare1=:13 where us#=:1

END OF STMT

PARSE

#140446136869016

:c=11966,e=11918,p=18,cr=94,cu=0,mis=1,r=0,dep=1,og=3,plh=0,tim=3161302405542

BINDS

#140446136869016

:

Bind

#0

oacdty=01 mxl=32(21) mxlc=00 mal=00 scl=00 pre=00

oacflg=18 fl2=0001 frm=01 csi=852 siz=32 off=0

kxsbbbfp=9bbdac32 bln=32 avl=21 flg=09

value="_SYSSMU12_3861134380$"

Bind

#1