联系：手机/微信(+86 17813235971) QQ(107644445)
作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]
有客户数据库,异常断电之后,数据库运行不稳定（经常性的重启）,通过分析发现
Wed Jun 29 01:04:39 2022 Completed: alter database open Wed Jun 29 01:04:42 2022 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j000_3284.trc: ORA-12012: error on auto execute of job 1 ORA-01578: ORACLE data block corrupted (file # 2, block # 552) ORA-01110: data file 2: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA_2\ORCL\UNDOTBS01.DBF' ………… Wed Jun 29 01:13:28 2022 Non-fatal internal error happenned while SMON was doing logging scn->time mapping. SMON encountered 1 out of maximum 100 non-fatal internal errors. Wed Jun 29 01:15:34 2022 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_m000_5488.trc: ORA-00600: internal error code, arguments: [6002], [6], [48], [5], [0], [], [], [] Wed Jun 29 01:20:54 2022 Non-fatal internal error happenned while SMON was doing logging scn->time mapping. SMON encountered 2 out of maximum 100 non-fatal internal errors. Wed Jun 29 01:20:55 2022 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_6956.trc: ORA-00600: internal error code, arguments: [2032], [8389160], [8389160], [8192], [2], [255], [0], [767] Non-fatal internal error happenned while SMON was doing flushing of monitored table stats. SMON encountered 3 out of maximum 100 non-fatal internal errors. Wed Jun 29 01:20:57 2022 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_6956.trc: ORA-00600: internal error code, arguments: [2032], [8389160], [8389160], [8192], [2], [255], [0], [767] ……………… Wed Jun 29 01:21:41 2022 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_q001_2124.trc: ORA-00474: SMON process terminated with error Wed Jun 29 01:21:42 2022 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_dbw0_3376.trc: ORA-00474: SMON process terminated with error Wed Jun 29 01:21:42 2022 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_reco_2412.trc: ORA-00474: SMON process terminated with error Instance terminated by PMON, pid = 7160
对ora-600 2032进行分析
*** 2022-06-29 01:13:26.907
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [2032], [8389160], [8389160], [8192], [2], [255], [0], [767]
Current SQL statement for this session:
insert into smon_scn_time (thread, time_mp, time_dp, scn, scn_wrp, scn_bas, num_mappings,
tim_scn_map) values (0, :1, :2, :3, :4, :5, :6, :7)
check trace file e:\oracle\product\10.2.0\db_2\rdbms\trace\orcl_ora_0.trc for preloading .sym file messages
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp+663 CALL??? ksedst+55 003C878B8 000000000 00FF57178
000000000
ksfdmp+19 CALL??? ksedmp+663 000000003 00ED07680 010453DA8
003CACC80
kgeriv+184 CALL??? ksfdmp+19 7FF2378C000 7FF5E2F81D8
7FF5EBB9300 7FF5EBB92F0
kgesiv+102 CALL??? kgeriv+184 000000002 00ED07040 000000002
00FF59110
ksesic7+125 CALL??? kgesiv+102 7FFFFFFF00800228 100000002
200000001 00FF59328
kcopcv+1014 CALL??? ksesic7+125 0000007F0 000000000 000800228
000000000
kcbchg1_main+3115 CALL??? kcopcv+1014 00001E778 7FF00000001
00001E980 00001E650
kcbchg1+238 CALL??? kcbchg1_main+3115 00ED07040 00ED07040 000040013
000000000
ktuchg+1331 CALL??? kcbchg1+238 7FF00000000 000000003
00FF597C8 00FF59780
ktbchg2+341 CALL??? ktuchg+1331 000000000 000000401 000000046
000BB5D21
kdtchg+916 CALL??? ktbchg2+341 000000001 000000000 000000240
000000000
kdtwrp+2582 CALL??? kdtchg+916 01077A268 01044404C 010444054
010441710
kdtInsRow+705 CALL??? kdtwrp+2582 01077A268 7FF5E2F8510
003CB3358 0009C20C4
insrowFastPath+125 CALL??? kdtInsRow+705 00ED07040 7FF55A86E30
7FF58E87918 00001F318
insdrvFastPath+478 CALL??? insrowFastPath+125 000000067 000000000 000000000
000000000
inscovexe+434 CALL??? insdrvFastPath+478 01077A268 000000000 010440070
00521E0C9
insExecStmtExecIniE CALL??? inscovexe+434 7FF55A88FD8 7FF55A86E30
ngine+99 00FF5BAD8 0009FA3EC
insexe+453 CALL??? insExecStmtExecIniE 8B2D554D9623 000000006
ngine+99 000000006 0000000C0
opiexe+4991 CALL??? insexe+453 7FF55A885A0 00FF5BAD8
000000102 000000000
opiall0+1931 CALL??? opiexe+4991 7FF00000049 000000003
00FF5C160 000000020
opikpr+660 CALL??? opiall0+1931 000000065 000000022 00FF5C638
000000000
opiodr+1136 CALL??? opikpr+660 000000065 000000017 01044B798
07EEF1FCF
rpidrus+230 CALL??? opiodr+1136 000000065 000000017 01044B798
80005900000000
rpidru+112 CALL??? rpidrus+230 00FF5D3F0 000000003 01078D4A0
7FF5B6F1A80
rpiswu2+517 CALL??? rpidru+112 7FF5DA52BB8 000000000
000000000 000000008
kprball+1446 CALL??? rpiswu2+517 7FF5E408820 000000000
00FF5DAD0 000000002
ktf_scn_time+4951 CALL??? kprball+1446 01044B798 8B2D00000140
000000000 000000005
ktmmon+4107 CALL??? ktf_scn_time+4951 000000000 000000001 07FFFFFFF
00521A3C2
ktmSmonMain+26 CALL??? ktmmon+4107 0049CBAC0 000000004
8B2D554D9623 00001E768
ksbrdp+903 CALL??? ktmSmonMain+26 003CC2A18 0049CBADC 000000008
000000004
opirip+700 CALL??? ksbrdp+903 726F77740000001E 003C8B000
00FF5FA30 000000000
opidrv+860 CALL??? opirip+700 000000032 000000004 00FF5FD50
000000000
sou2o+52 CALL??? opidrv+860 000000032 000000004 00FF5FD50
000000003
opimai_real+272 CALL??? sou2o+52 000000000 000000000 000000000
000000000
opimai+96 CALL??? opimai_real+272 000000000 000000000 000000000
000000000
BackgroundThreadSta CALL??? opimai+96 00FF5FEA8 000000001 000000000
rt+633 000000000
000000007738F56D CALL??? BackgroundThreadSta 0069E4590 000000000 000000000
rt+633 000000000
0000000077703021 CALL??? 000000007738F56D 000000000 000000000 000000000
000000000
--------------------- Binary Stack Dump ---------------------
通过该trace和alert日志信息可以确认是由于smon_scn_time的操作需要使用到undo,但是对应的undo block异常,从而使得该操作失败,进而引起数据库smon进程异常从而引起ORA-00474,数据库自动crash.处理问题比较简单：
1. 对异常undo进行处理,创建新undo,删除老undo
2. 对于smon_scn_time异常数据进行处理