-
加我微信(17813235971)
加我QQ(107644445)
标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-00742 ORA-01110 ORA-01555 ORA-01578 ORA-01595 ORA-08103 ORA-600 2131 ORA-600 2662 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 Oracle 恢复 ORACLE恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (103)
- 数据库 (1,769)
- DB2 (22)
- MySQL (77)
- Oracle (1,610)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (166)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (69)
- Oracle Bug (8)
- Oracle RAC (54)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (592)
- Oracle安装升级 (97)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (86)
- PostgreSQL (30)
- pdu工具 (6)
- PostgreSQL恢复 (9)
- SQL Server (32)
- SQL Server恢复 (13)
- TimesTen (7)
- 达梦数据库 (3)
- 达梦恢复 (1)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (39)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (22)
-
最近发表
- 2025年的Oracle 8.0.5数据库恢复
- ORA-600 kokiasg1故障分析(obj$中核心字典序列全部被恶意删除)
- ORA-00756 ORA-10567故障数据0丢失恢复
- 数据库文件变成32k故障恢复
- tcp连接过多导致监听TNS-12532 TNS-12560 TNS-00502错误
- 文件系统格式化MySQL数据库恢复
- .sstop勒索加密数据库恢复
- 解决一次硬件恢复之后数据文件0kb的故障恢复case
- Error in invoking target ‘libasmclntsh19.ohso libasmperl19.ohso client_sharedlib’问题处理
- ORA-01171: datafile N going offline due to error advancing checkpoint
- linux环境oracle数据库被文件系统勒索加密为.babyk扩展名溯源
- ORA-600 ksvworkmsgalloc: bad reaper
- ORA-600 krccfl_chunk故障处理
- Oracle Recovery Tools恢复案例总结—202505
- ORA-600 kddummy_blkchk 数据库循环重启
- 记录一次asm disk加入到vg通过恢复直接open库的案例
- CHECKDB 发现了 N 个分配错误和 M 个一致性错误
- 达梦数据库dm.ctl文件异常恢复
- Oracle Recovery Tools修复ORA-00742、ORA-600 ktbair2: illegal inheritance故障
- 可能是 tempdb 空间用尽或某个系统表不一致故障处理
分类目录归档：ORA-xxxxx
重现ORA-600 4000异常
对于数据库恢复感兴趣的人,一定对于ORA-600[4000]这个著名的错误记忆犹新,这里通过试验重现ORA-600[4000]
查询数据库obj$.con$记录
[oracle@xifenfei ~]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Nov 4 06:32:36 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 318767104 bytes
Fixed Size 1219160 bytes
Variable Size 92276136 bytes
Database Buffers 218103808 bytes
Redo Buffers 7168000 bytes
Database mounted.
Database opened.
SQL> select OBJ#,dbms_rowid.rowid_relative_fno(rowid) rel_fno,
2 dbms_rowid.rowid_block_number(rowid) block_num from obj$
3 where name='CON$';
OBJ# REL_FNO BLOCK_NUM
---------- ---------- ----------
28 1 122
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
bbed修改数据块
根据催华的研究,当OBJ$中部分数据块中的csc和itl的scn都大于header scn的时候,数据库启动就会报ORA-600[4000]
[oracle@xifenfei ~]$ bbed listfile=list mode=edit password=blockedit
BBED: Release 2.0.0.0.0 - Limited Production on Fri Nov 4 06:47:09 2011
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
************* !!! For Oracle Internal Use only !!! ***************
BBED> info
File# Name Size(blks)
----- ---- ----------
1 /u01/oracle/oradata/XFF/system01.dbf 0
2 /u01/oracle/oradata/XFF/undotbs01.dbf 0
3 /u01/oracle/oradata/XFF/sysaux01.dbf 0
4 /u01/oracle/oradata/XFF/users01.dbf 0
5 /u01/oracle/oradata/XFF/datfttuser.dbf 0
BBED> set block 1
BLOCK# 1
BBED> set file 1 block 1
FILE# 1
BLOCK# 1
BBED> p kcvfhckp.kcvcpscn
struct kcvcpscn, 8 bytes @484
ub4 kscnbas @484 0x00210f97
ub2 kscnwrp @488 0x0000
BBED> set block 122
BLOCK# 122
BBED> p ktbbh
struct ktbbh, 48 bytes @20
ub1 ktbbhtyp @20 0x01 (KDDBTDATA)
union ktbbhsid, 4 bytes @24
ub4 ktbbhsg1 @24 0x00000012
ub4 ktbbhod1 @24 0x00000012
struct ktbbhcsc, 8 bytes @28 <==csc(SCN of the last block cleanout)
ub4 kscnbas @28 0x0020770d
ub2 kscnwrp @32 0x0000
sb2 ktbbhict @36 1
ub1 ktbbhflg @38 0x02 (NONE)
ub1 ktbbhfsl @39 0x00
ub4 ktbbhfnx @40 0x00000000
struct ktbbhitl[0], 24 bytes @44
struct ktbitxid, 8 bytes @44
ub2 kxidusn @44 0x0005 <==回滚段序号
ub2 kxidslt @46 0x0029
ub4 kxidsqn @48 0x0000029a
struct ktbituba, 8 bytes @52
ub4 kubadba @52 0x00802381
ub2 kubaseq @56 0x01f9
ub1 kubarec @58 0x03
ub2 ktbitflg @60 0x2001 (KTBFUPB)
union _ktbitun, 2 bytes @62
sb2 _ktbitfsc @62 0
ub2 _ktbitwrp @62 0x0000
ub4 ktbitbas @64 0x0020770e <==itl commit scn
BBED> set count 16
COUNT 16
BBED> m /x 0d772010 offset 28
Warning: contents of previous BIFILE will be lost. Proceed? (Y/N) y
File: /u01/oracle/oradata/XFF/system01.dbf (1)
Block: 122 Offsets: 28 to 60 Dba:0x0040007a
------------------------------------------------------------------------
0d772010 00000000 01000200 00000000
<32 bytes per line>
BBED> m /x 0e772010 offset 64
File: /u01/oracle/oradata/XFF/system01.dbf (1)
Block: 122 Offsets: 64 to 96 Dba:0x0040007a
------------------------------------------------------------------------
0e772010 00016c00 ffffea00 53046903
<32 bytes per line>
BBED> p ktbbh
struct ktbbh, 48 bytes @20
ub1 ktbbhtyp @20 0x01 (KDDBTDATA)
union ktbbhsid, 4 bytes @24
ub4 ktbbhsg1 @24 0x00000012
ub4 ktbbhod1 @24 0x00000012
struct ktbbhcsc, 8 bytes @28
ub4 kscnbas @28 0x1020770d
ub2 kscnwrp @32 0x0000
sb2 ktbbhict @36 1
ub1 ktbbhflg @38 0x02 (NONE)
ub1 ktbbhfsl @39 0x00
ub4 ktbbhfnx @40 0x00000000
struct ktbbhitl[0], 24 bytes @44
struct ktbitxid, 8 bytes @44
ub2 kxidusn @44 0x0005
ub2 kxidslt @46 0x0029
ub4 kxidsqn @48 0x0000029a
struct ktbituba, 8 bytes @52
ub4 kubadba @52 0x00802381
ub2 kubaseq @56 0x01f9
ub1 kubarec @58 0x03
ub2 ktbitflg @60 0x2001 (KTBFUPB)
union _ktbitun, 2 bytes @62
sb2 _ktbitfsc @62 0
ub2 _ktbitwrp @62 0x0000
ub4 ktbitbas @64 0x1020770e
BBED> sum apply
Check value for File 1, Block 122:
current = 0xc902, required = 0xc902
启动数据库
SQL> startup ORACLE instance started. Total System Global Area 318767104 bytes Fixed Size 1219160 bytes Variable Size 92276136 bytes Database Buffers 218103808 bytes Redo Buffers 7168000 bytes Database mounted. ORA-01092: ORACLE instance terminated. Disconnection forced
查看日志
Fri Nov 4 06:50:38 2011 Database mounted in Exclusive Mode Completed: ALTER DATABASE MOUNT Fri Nov 4 06:50:38 2011 ALTER DATABASE OPEN Fri Nov 4 06:50:38 2011 LGWR: STARTING ARCH PROCESSES ARC0 started with pid=16, OS id=7048 Fri Nov 4 06:50:38 2011 ARC0: Archival started ARC1: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC1 started with pid=17, OS id=7050 ARC1: STARTING ARCH PROCESSES Fri Nov 4 06:50:38 2011 ARC0: Becoming the 'no FAL' ARCH ARC0: Becoming the 'no SRL' ARCH Fri Nov 4 06:50:38 2011 Thread 1 opened at log sequence 38 Current log# 3 seq# 38 mem# 0: /u01/oracle/oradata/XFF/redo03.log Successful open of redo thread 1 Fri Nov 4 06:50:38 2011 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Fri Nov 4 06:50:38 2011 SMON: enabling cache recovery Fri Nov 4 06:50:38 2011 ARC2: Archival started ARC1: STARTING ARCH PROCESSES COMPLETE ARC1: Becoming the heartbeat ARCH ARC2 started with pid=18, OS id=7052 Fri Nov 4 06:50:38 2011 Errors in file /u01/oracle/admin/XFF/udump/xff_ora_7046.trc: ORA-00600: internal error code, arguments: [4000], [5], [], [], [], [], [], [] Fri Nov 4 06:50:40 2011 Errors in file /u01/oracle/admin/XFF/udump/xff_ora_7046.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [4000], [5], [], [], [], [], [], [] Fri Nov 4 06:50:40 2011 Error 704 happened during db open, shutting down database USER: terminating instance due to error 704 Instance terminated by USER, pid = 7046 ORA-1092 signalled during: ALTER DATABASE OPEN...
在ORACL 11.2的版本中,同样的方法无法重新该错误,数据库依然能够正常打开,所以如果要测试的朋友请选择11G以下版本进行.
TOAD导致ORA-00600[17281]
alert日志报ORA-00600[17281]
Thu Aug 2 01:49:39 2012 Errors in file /oracle9/app/admin/acc/udump/acc2_ora_647350.trc: ORA-00600: internal error code, arguments: [17281], [1001], [0x7000007AB9F0A30], [], [], [], [], [] ORA-01001: invalid cursor Thu Aug 2 01:49:39 2012 Errors in file /oracle9/app/admin/acc/udump/acc2_ora_647350.trc: ORA-00600: internal error code, arguments: [17281], [1001], [0x7000007AB9F0A30], [], [], [], [], [] ORA-01001: invalid cursor ORA-00600: internal error code, arguments: [17281], [1001], [0x7000007AB9F0A30], [], [], [], [], [] ORA-01001: invalid cursor
分析trace文件
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
ORACLE_HOME = /oracle9/app/product/9.2.0
System name: AIX
Node name: zwq_acc2
Release: 3
Version: 5
Machine: 00CFFB554C00
Instance name: acc2
Redo thread mounted by this instance: 2
Oracle process number: 1598
Unix process pid: 647350, image: oracle@zwq_acc2 (TNS V1-V3)
*** SESSION ID:(1643.29233) 2012-08-02 00:01:44.423
*** 2012-08-02 00:01:44.423
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [17281], [1001], [0x7000007AB9F0A30], [], [], [], [], []
ORA-01001: invalid cursor
Current SQL statement for this session:
DECLARE
CURSOR NlsParamsCursor
IS
SELECT * FROM nls_session_parameters;
BEGIN
SELECT NVL (LENGTHB (CHR (65536)), NVL (LENGTHB (CHR (65536)), 1))
INTO :CharLength
FROM DUAL;
FOR NlsRecord IN NlsParamsCursor
LOOP
IF NlsRecord.parameter = 'NLS_DATE_LANGUAGE'
THEN
:NlsDateLanguage := NlsRecord.VALUE;
ELSIF NlsRecord.parameter = 'NLS_DATE_FORMAT'
THEN
:NlsDateFormat := NlsRecord.VALUE;
ELSIF NlsRecord.parameter = 'NLS_NUMERIC_CHARACTERS'
THEN
:NlsNumericCharacters := NlsRecord.VALUE;
ELSIF NlsRecord.parameter = 'NLS_TIMESTAMP_FORMAT'
THEN
:NlsTimeStampFormat := NlsRecord.VALUE;
ELSIF NlsRecord.parameter = 'NLS_TIMESTAMP_TZ_FORMAT'
THEN
:NlsTimeStampTZFormat := NlsRecord.VALUE;
END IF;
END LOOP;
END;
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp+0148 bl ksedst 1029746FC ?
ksfdmp+0018 bl 01FD4014
kgeriv+0118 bl _ptrgl
kgeasi+00cc bl kgeriv 000000000 ? 110347AE0 ?
1101A1738 ? 110380110 ?
110380420 ?
kgicli+0164 bl kgeasi 110006308 ? 110386088 ?
438100004381 ? 200000002 ?
200000002 ? 000000000 ?
0000003E9 ? 000000002 ?
kgidlt+03a0 bl kgicli 110287AA0 ? 000000168 ?
kgidel+0018 bl kgidlt 11003DD08 ? 110062138 ?
000000069 ? 000000000 ?
000000000 ?
perabo+00cc bl kgidel 000000000 ? 000000000 ?
perdcs+0038 bl perabo 000000120 ? 000000012 ?
70000000005C390 ?
peidcs+00ac bl perdcs 110002A20 ? 70000000007A450 ?
kkxcls+00bc bl peidcs FFFFFFFFFFFA298 ? 110349708 ?
kxscln+0048 bl kkxcls 1031628A8 ?
kkscls+0268 bl kxscln 110349F60 ?
opicca+00f0 bl kkscls 1009E8034 ? FFFFFFFFFFFA4C0 ?
opiclo+0020 bl opicca FFFFFFFFFFFA810 ?
kpoclsa+004c bl opiclo 000000002 ?
opiodr+08cc bl _ptrgl
ttcpip+0cc4 bl _ptrgl
opitsk+0d60 bl ttcpip 11000CF90 ? 000000000 ?
000000000 ? 000000000 ?
000000000 ? 000000000 ?
000000000 ? 000000000 ?
opiino+0758 bl opitsk 000000000 ? 000000000 ?
opiodr+08cc bl _ptrgl
opidrv+032c bl opiodr 3C00000018 ? 4101FAF78 ?
FFFFFFFFFFFF7A0 ? 0A000F000 ?
sou2o+0028 bl opidrv 3C0C000000 ? 4A02C3B50 ?
FFFFFFFFFFFF7A0 ?
main+0138 bl 01FD3A28
__start+0098 bl main 000000000 ? 000000000 ?
--------------------- Binary Stack Dump ---------------------
SO: 70000067d802e90, type: 2, owner: 0, flag: INIT/-/-/0x00
(process) Oracle pid=1598, calls cur/top: 7000006f50c45f0/7000006f50c45f0, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 0
last post received-location: No post
last process to post me: 70000067d5eedf8 2 6
last post sent: 0 0 0
last post sent-location: No post
last process posted by me: none
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 7000006815fe518
O/S info: user: oraacc, term: UNKNOWN, ospid: 647350
OSD pid info: Unix process pid: 647350, image: oracle@zwq_acc2 (TNS V1-V3)
----------------------------------------
SO: 70000068169e7b8, type: 4, owner: 70000067d802e90, flag: INIT/-/-/0x00
(session) trans: 0, creator: 70000067d802e90, flag: (41) USR/- BSY/-/-/-/-/-
DID: 0000-0000-00000000, short-term DID: 0000-0000-00000000
txn branch: 0
oct: 0, prv: 0, sql: 700000980c32508, psql: 700000980c32508, user: 44/DBRPT
O/S info: user: wusp9, term: AHMWUSP9, ospid: 2812:1900, machine: AH\AHMWUSP9
program:
last wait for 'SQL*Net message from client' blocking sess=0x0 seq=13 wait_time=3647540
driver id=54435000, #bytes=1, =0
temporary object counter: 0
这里可以看出当前执行的sql是一种框架中发生,但是从PROCESS STATE未找到登录客户端名称,但是从machine中大概可以估算出来是windows机器.通过查询V$sql找出MODULE
SQL> select module,last_load_time from V$sql where sql_text like 'declare cursor NlsParamsCursor is%'; MODULE LAST_LOAD_TIME --------------- ---------------------------------- Toad.exe 2012-08-02/00:01:44
从这里可以确定,是因为TOAD登录数据库出现该错误,查询MOS发现相关内容ORA-600 [17281] using TOAD [ID 329531.1]
解决方法
You can also overcome this by patching the Oracle Client software as follows.: 1. Fix unpublished Bug 4359111, if the Oracle software is 10.1.0.4 or below. Patches for this bug can be found on My Oracle Support under Patch:4359111. 2. Fix unpublished bug 5910901 by applying Patch:5910901 if the Oracle software is 10.1.0.5 or above, 3. Apply the 10.2.0.4 patch set or above on the client. 4. You can change the non-Oracle client software being used, 5. You can just ignore the error as it is non-corruptive. 6. Run the queries directly through SQLPLUS instead of using TOAD. **Ensure that your version of TOAD is compatible with the version of the database as well. If the errors continue when using TOAD, but not with SQL*Plus, contact TOAD support to request a fix.**
ORA-00600[kgscLogOff-notempty]
在查看一网友alert日志时发现很多ORA-00600[kgscLogOff-notempty]记录,通过查询MOS分析记录结果如下:
alert日志出现ORA-00600[kgscLogOff-notempty]
Wed Aug 1 10:28:35 2012 Errors in file /vgdata/oracle/admin/orcl1/udump/orcl1_ora_18430.trc: ORA-00600: internal error code, arguments: [kgscLogOff-notempty], [1], [], [], [], [], [], [] Wed Aug 1 10:28:38 2012 Errors in file /vgdata/oracle/admin/orcl1/udump/orcl1_ora_18508.trc: ORA-00600: internal error code, arguments: [kgscLogOff-notempty], [3], [], [], [], [], [], []
trace结合MOS分析原因
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /vgdata/oracle/product
System name: HP-UX
Node name: hpdc1
Release: B.11.31
Version: U
Machine: ia64
Instance name: orcl1
Redo thread mounted by this instance: 1
Oracle process number: 230
Unix process pid: 18430, image: oracleorcl1@hpdc1
*** SERVICE NAME:(orcl1) 2012-08-01 10:28:35.937
*** SESSION ID:(191.141) 2012-08-01 10:28:35.937
*** 2012-08-01 10:28:35.937
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kgscLogOff-notempty], [1], [], [], [], [], [], []
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst()+64 call _etext_f()+23058430 000000000 ? 000000001 ?
09017233648
ksedmp()+1680 call _etext_f()+23058430 000000000 ?
09017233648 C000000000000D20 ?
40000000052C8C90 ?
000000000 ? 000000000 ?
000000000 ?
ksfdmp()+48 call _etext_f()+23058430 000000003 ?
09017233648
kgerinv()+400 call _etext_f()+23058430 40000000093F4370 ?
09017233648 000000003 ?
C000000000000612 ?
000008F07 ? 000000000 ?
000000000 ?
kgeasnmierr()+144 call _etext_f()+23058430 6000000000015190 ?
09017233648 6000000000016248 ?
6000000000013770 ?
600000000009C808 ?
60000000000165B0 ?
$cold_kgscLogOff()+ call _etext_f()+23058430 6000000000015190 ?
144 09017233648 9FFFFFFFBF562160 ?
9FFFFFFFBF562170 ?
60000000000165C0 ?
000000000 ? 000000001 ?
kkslof()+320 call _etext_f()+23058430 6000000000015190 ?
09017233648
opifcs()+592 call _etext_f()+23058430 C000000360365908 ?
09017233648 C000000000000E21 ?
4000000002E1BF20 ?
000000000 ? 000000000 ?
ksuxds()+1568 call _etext_f()+23058430 C000000360365908 ?
09017233648 4000000002EBA7A0 ?
000008F9F ? 000004810 ?
9FFFFFFFBF56BEF6 ?
C000000360365908 ?
4000000001354140 ?
00000003F ?
ksudel()+128 call _etext_f()+23058430 60000000000A7B54 ?
09016643752 60000000000A7CF8 ?
9FFFFFFFFFFF6C20 ?
600000000009D8A0 ?
opilof()+3664 call _etext_f()+23058430 60000000000A7B54 ?
09016643752 60000000000A7CF8 ?
4000000003D681E0 ?
C00000000000122A ?
00000814F ?
60000000000A7CE0 ?
opiodr()+2016 call opilof()+3664 60000000002BE7B0 ?
60000000002BE7B8 ?
000000001 ?
9FFFFFFFFFFF71B0 ?
600000000009D8A0 ?
60000000002BE7E0 ?
ttcpip()+1824 call _etext_f()+23058430 60000000000AA0BC ?
09017243504 000000001 ?
6000000000015310 ?
6000000000015310 ?
9FFFFFFFFFFF8250 ?
600000000009D8A0 ?
9FFFFFFFFFFF8250 ?
6000000000020D88 ?
opitsk()+2224 call _etext_f()+23058430 6000000000020D80 ?
09017192128 9FFFFFFFFFFFA3D4 ?
6000000000020EE8 ?
000000001 ?
9FFFFFFFFFFFAA90 ?
9FFFFFFFFFFFA884 ?
6000000000020E88 ?
000000000 ?
opiino()+2144 call _etext_f()+23058430 000000000 ? 000000000 ?
09016681384 600000000009D8A0 ?
4000000002AE7E10 ?
000008001 ?
9FFFFFFFFFFFA874 ?
opiodr()+2016 call _etext_f()+23058430 00000003C ?
09016681384 9FFFFFFFFFFFF260 ?
9FFFFFFFFFFFF250 ?
9FFFFFFFFFFFBF90 ?
0000000B0 ?
600000000008F560 ?
opidrv()+1136 call _etext_f()+23058430 60000000000AA0BC ?
09017243504 000000001 ?
6000000000015310 ?
6000000000015310 ?
9FFFFFFFFFFFCAE0 ?
600000000009D8A0 ?
sou2o()+240 call 9fffffffffffcae0 00000003C ? 000000004 ?
9FFFFFFFFFFFF250 ?
opimai_real()+480 call 9fffffffffffcae0 9FFFFFFFFFFFF270 ?
00000003C ? 000000004 ?
9FFFFFFFFFFFF250 ?
main()+352 call 9fffffffffffcae0 000000000 ?
9FFFFFFFFFFFF2A0 ?
main_opd_entry()+80 call 9fffffffffffcae0 000000002 ?
9FFFFFFFFFFFF750 ?
C000000000033910 ?
000000000 ?
--------------------- Binary Stack Dump ---------------------
通过查询MOS发现ORA-600 [kgscLogOff-notempty] On Session Logoff [ID 413120.1]中记录有
The following error may occur on session logoff ORA-600 [kgscLogOff-notempty], [1] or ORA-600 [kgscLogOff-notempty], [2] with a Call Stack like: ... kgscLogOff kkslof opifcs ksuxds ksudel ...
和该数据库中的Stack Dump记录一致,数据库版本也在该bug范围内,从而可以确定是unpublished Bug 4887675
解决方案
该错误是在logoff时产生,对数据库影响不大,如果偶尔出现可以忽略,出现频率过高,建议按照下列方法解决
There is No Data Corruption (or) Data Loss due to this Error. This error occurs during the logoff operation, hence the impact should be negligible. This is fixed in 10.2.0.4 and above releases. One-off patches may be available depending on your current release and operating system. To obtain a patch from MetaLink: 1) Click on Patches. 2) Click on Simple Search 3) Enter patch number: 4887675 4) Select your O/S 5) Click Go. As workaround, avoid Killing/Terminating the Session Abnormally.