ORA-600(kkdlfjou_1)错误

10.2.0.5 RAC环境出现ORA-600[kkdlfjou_1]错误。
错误信息:

Thu Jun 02 10:09:38 EAT 2011
Errors IN file /oracle/app/admin/orcl/udump/orcl2_ora_17796.trc:
ORA-00600: internal error code, arguments: [kkdlfjou_1], [], [], [], [], [], [], []
Thu Jun 02 10:09:40 EAT 2011
Errors IN file /oracle/app/admin/orcl/udump/orcl2_ora_29452.trc:
ORA-00600: 内部错误代码, 参数: [kkdlfjou_1], [], [], [], [], [], [], []
Thu Jun 02 10:09:42 EAT 2011
Errors IN file /oracle/app/admin/orcl/udump/orcl2_ora_27143.trc:
ORA-00600: internal error code, arguments: [kkdlfjou_1], [], [], [], [], [], [], []

该错误是由于在线重建索引的操作被异常中止,而Oracle没有清理数据字典以及中间表,导致在查询该表时出现错误。
Oracle建议的解决方法是删除中间表,并重启数据库实例。

Posted in BUG | Tagged , , , , | Leave a comment

ORA-600(krbounotread_noctx)错误

由于RMAN备份导致的BUG。
ORA-600(krboReadBitmap_badbitmap)错误:https://yangtingkun.net/?p=863
这个问题和以前碰到的问题属于同一个BUG,错误信息为:

Tue May 8 02:18:42 2012
Backup optimization FOR file +DATA/orcl/datafile/index_ts1.ora stopped due TO errors:
Tue May 8 02:18:42 2012
Errors IN file /u01/app/oracle/admin/ORCL/udump/orcl2_ora_3758.trc:
ORA-00600: internal error code, arguments: [krboReadBitmap_badbitmap], [272945930], [+DATA/orcl/datafile/index_ts1.ora], [6], [30], [33554432], [1024], [19808273]
Tue May 8 02:18:42 2012
Trace dumping IS performing id=[cdmp_20120508021842]
Tue May 8 02:18:42 2012
Errors IN file /u01/app/oracle/admin/ORCL/udump/orcl2_ora_3758.trc:
ORA-00600: internal error code, arguments: [krbounotread_noctx], [], [], [], [], [], [], []

出现这个ORA-600[krbounotread_noctx]错误的同时,也出现了ORA-600[krboReadBitmap_badbitmap]错误,二个错误是同一个问题导致的,而且在出现错误之前,告警日志中有个Backup optimization的信息,说明问题发生时刻在进行备份,且启用了备份的优化。
因此,导致问题的原因也和前一篇文档中介绍的一样,参考MOS文档:ORA-600 [Krbodo_badend] On RMAN Backup [ID 412170.1],这个问题对应的BUG为:Bug 5556503,在进行备份时通过文件头的BITMAP信息在确定哪些空间需要备份时,出现了错误并导致了ORA-600错误。
针对这个错误,可以通过升级到10.2.0.4来解决该问题,也可以在备份的时候去掉备份优化选项,在BACKUP语句中添加BLOCKS ALL语句。

Posted in BUG | Tagged , , , | Leave a comment

ORA-7445(kfcbCloseCIC10)错误

10.2.0.3 RAC的ASM实例,出现ORA-7445错误导致实例崩溃。
详细错误信息为:

Tue Nov 9 10:47:59 2010
NOTE: reconfiguration OF GROUP 4/0x654fe2a9 (DATA), FULL=1
NOTE: disk validation pending FOR GROUP 4/0x654fe2a9 (DATA)
ERROR: GROUP 4/0x654fe2a9 (DATA): could NOT validate disk 25
SUCCESS: validated disks FOR 4/0x654fe2a9 (DATA)
NOTE: PST refresh pending FOR GROUP 4/0x654fe2a9 (DATA)
NOTE: PST UPDATE: grp = 4, dsk = 25, mode = 0x4
Tue Nov 9 10:48:03 2010
ERROR: too many offline disks IN PST (grp 4)
Tue Nov 9 10:48:03 2010
NOTE: PST NOT enabling heartbeating (grp 4): GROUP dismounted
Tue Nov 9 10:48:03 2010
SUCCESS: refreshed PST FOR 4/0x654fe2a9 (DATA)
ERROR: ORA-15040 thrown IN RBAL FOR GROUP NUMBER 4
Tue Nov 9 10:48:03 2010
Errors IN file /u01/app/oracle/admin/+ASM/bdump/+asm2_rbal_7330.trc:
ORA-15040: diskgroup IS incomplete
ORA-15066: offlining disk "" may RESULT IN a DATA loss
ORA-15042: ASM disk "25" IS missing
Tue Nov 9 10:48:05 2010
Errors IN file /u01/app/oracle/admin/+ASM/bdump/+asm2_ckpt_7321.trc:
ORA-00600: internal error code, arguments: [kfcbCloseCIC10], [4], [25], [7], [], [], [], []
Tue Nov 9 10:48:06 2010
Errors IN file /u01/app/oracle/admin/+ASM/bdump/+asm2_ckpt_7321.trc:
ORA-00600: internal error code, arguments: [kfcbCloseCIC10], [4], [25], [7], [], [], [], []
Tue Nov 9 10:48:06 2010
CKPT: terminating instance due TO error 469
Tue Nov 9 10:48:06 2010
Trace dumping IS performing id=[cdmp_20101109104806]
Tue Nov 9 10:48:08 2010
Shutting down instance (abort)
License high water mark = 7
Tue Nov 9 10:48:11 2010
Instance TERMINATED BY CKPT, pid = 7321
Tue Nov 9 10:48:13 2010
Instance TERMINATED BY USER, pid = 25914

根据MOS文档Bug 8374703 – RAC ASM crash after disconnect in storage interconnect [ID 8374703.8],当存储连接断开可能会导致ASM实例的脑裂。而当前的这个问题虽然和文档描述的不完全一致,但是这个ORA-600错误显然是由于之前ASM磁盘找不到的问题所引起的。
这个问题Oracle在11.2.0.1在最终解决,事实上11.2的ASM的架构都和11.1及以前版本的ASM发生了明显的变化。而针对Bug 8374703的bug也只是在11.1上被FIXED,这个问题并没有10g上的解决方案。不过从错误信息上看,这个错误在10g上应该是偶然出现,而且和磁盘故障直接相关。

Posted in BUG | Tagged , , , , , , , | Leave a comment

ORA-600(1403)和ORA-7445($cold_kslgetsl)错误

10.2.0.2 RAC的ASM实例,出现这两个错误并导致实例的崩溃。
错误信息为:

Thu Apr 12 18:55:42 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface TYPE 1 lan901 192.168.0.0 configured FROM OCR FOR USE AS a cluster interconnect
Interface TYPE 1 lan900 198.5.1.0 configured FROM OCR FOR USE AS a public interface
Picked latch-free SCN scheme 3
USING LOG_ARCHIVE_DEST_1 parameter DEFAULT VALUE AS /u01/app/oracle/product/10.2.0/db_1/dbs/arch
Autotune OF undo retention IS turned off. 
LICENSE_MAX_USERS = 0
SYS auditing IS disabled
ksdpec: called FOR event 13740 prior TO event GROUP initialization
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters WITH non-DEFAULT VALUES:
large_pool_size = 12582912
instance_type = asm
cluster_database = TRUE
instance_number = 2
remote_login_passwordfile= EXCLUSIVE
background_dump_dest = /u01/app/oracle/admin/+ASM/bdump
user_dump_dest = /u01/app/oracle/admin/+ASM/udump
core_dump_dest = /u01/app/oracle/admin/+ASM/cdump
asm_diskstring = /hpap/rdsk/*
asm_diskgroups = DATE, AEG2_CTL, CTL, DATA, AEG2_DATA
Cluster communication is configured to use the following interface(s) for this instance
192.168.0.112
Thu Apr 12 18:55:43 2007
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=26298
DIAG started with pid=3, OS id=26300
PSP0 started with pid=4, OS id=26302
LMON started with pid=5, OS id=26304
LMD0 started with pid=6, OS id=26306
LMS0 started with pid=7, OS id=26308
MMAN started with pid=8, OS id=26310
DBW0 started with pid=9, OS id=26313
LGWR started with pid=10, OS id=26316
CKPT started with pid=11, OS id=26321
SMON started with pid=12, OS id=26324
RBAL started with pid=13, OS id=26353
GMON started with pid=14, OS id=26380
Thu Apr 12 18:55:44 2007
Errors in file /u01/app/oracle/admin/+ASM/bdump/+asm2_ckpt_26321.trc:
ORA-07445: exception encountered: core dump [$cold_kslgetsl()+1424] [SIGSEGV] [Address not mapped to object] [0x3FFFFFFF812FA310] [] []
Thu Apr 12 18:55:44 2007
lmon registered with NM - instance id 2 (internal mem no 1)
Thu Apr 12 18:55:44 2007
Errors in file /u01/app/oracle/admin/+ASM/bdump/+asm2_ckpt_26321.trc:
ORA-00081: address range [0x60000000000A7D70, 0x60000000000A7D74) is not readable
ORA-07445: exception encountered: core dump [$cold_kslgetsl()+1424] [SIGSEGV] [Address not mapped to object] [0x3FFFFFFF812FA310] [] []
Thu Apr 12 18:55:45 2007
Reconfiguration started (old inc 0, new inc 6)
ASM instance 
List of nodes:
0 1
Global Resource Directory frozen
Communication channels reestablished
* allocate domain 1, invalid = TRUE 
* domain 1 valid = 1 according to instance 0 
* allocate domain 2, invalid = TRUE 
* domain 2 valid = 1 according to instance 0 
* allocate domain 3, invalid = TRUE 
* domain 3 valid = 1 according to instance 0 
* allocate domain 4, invalid = TRUE 
* domain 4 valid = 1 according to instance 0 
Thu Apr 12 18:55:45 2007
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Thu Apr 12 18:55:45 2007
LMS 0: 0 GCS shadows cancelled, 0 closed
Set master node info 
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Thu Apr 12 18:55:45 2007
LMS 0: 0 GCS shadows traversed, 0 replayed
Thu Apr 12 18:55:45 2007
Submitted all GCS remote-cache requests
Fix write in gcs resources
Reconfiguration complete
Thu Apr 12 18:55:45 2007
Errors in file /u01/app/oracle/admin/+ASM/udump/+asm2_ora_26212.trc:
ORA-00600: internal error code, arguments: [1403], [], [], [], [], [], [], []
Thu Apr 12 18:55:46 2007
USER: terminating instance due to error 81
Instance terminated by USER, pid = 26212

可以看到,ASM实例刚刚启动,就由于ORA-7445[$cold_kslgetsl]错误和ORA-600[1403]错误以及ORA-81错误导致了实例被中止。
虽然ORA-7445对应的错误在MOS上几乎没有记载,不过ORA-600[1403]错误在10.2.0.2的RAC版本上有明确的bug记载:Bug 5128575 RAC install of 10.2.0.2 does not update libknlopt.a on all nodes。导致问题的原因是由于在按照10.2.0.2时,一个库文件libknlopt.a没有拷贝到远端站点并编译到oracle可执行文件中,导致远端节点出现DUMP的情况,可能出现的错误包括ORA-600[1403]和ORA-81等。
解决该问题的方法是拷贝$ORACLE_HOME/rdbms/lib/libknlopt.a文件到所有远端站点,然后在远端站点重新编辑oracle可执行文件make -f ins_rdbms.mk ioracle。

Posted in BUG | Tagged , , , , , , , , , , , | Leave a comment

ORA-7445(pfrrun_no_tool)错误

数据库的ASM实例碰到ORA-7445[pfrrun_no_tool]。
详细错误信息为:

Thu Sep 6 17:40:51 2007
WARNING: Oracle executable BINARY mismatch detected.
BINARY OF NEW process does NOT MATCH BINARY which started instance
issue ALTER system SET "_disable_image_check" = TRUE TO disable these messages
Thu Sep 6 17:40:51 2007
Errors IN file /u01/app/oracle/admin/+ASM/udump/+asm1_ora_15541.trc:
ORA-07445: exception encountered: core dump [pfrrun_no_tool()+113] [SIGSEGV] [Address NOT mapped TO object] [0x4000000070F898E3] [] []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
Thu Sep 6 17:40:51 2007
Errors IN file /u01/app/oracle/admin/+ASM/udump/+asm1_ora_15541.trc:
ORA-07445: exception encountered: core dump [pfrlnitinit()+801] [SIGSEGV] [Address NOT mapped TO object] [0x000001000] [] []
ORA-07445: exception encountered: core dump [pfrrun_no_tool()+113] [SIGSEGV] [Address NOT mapped TO object] [0x4000000070F898E3] [] []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
WARNING: Oracle executable BINARY mismatch detected.
BINARY OF NEW process does NOT MATCH BINARY which started instance
issue ALTER system SET "_disable_image_check" = TRUE TO disable these messages
Thu Sep 6 17:41:44 2007
Errors IN file /u01/app/oracle/admin/+ASM/udump/+asm1_ora_17005.trc:
ORA-07445: exception encountered: core dump [pfrrun_no_tool()+113] [SIGSEGV] [Address NOT mapped TO object] [0x4000000070F898E3] [] []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
Thu Sep 6 17:41:44 2007
Errors IN file /u01/app/oracle/admin/+ASM/udump/+asm1_ora_17005.trc:
ORA-07445: exception encountered: core dump [pfrlnitinit()+801] [SIGSEGV] [Address NOT mapped TO object] [0x000001000] [] []
ORA-07445: exception encountered: core dump [pfrrun_no_tool()+113] [SIGSEGV] [Address NOT mapped TO object] [0x4000000070F898E3] [] []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
WARNING: Oracle executable BINARY mismatch detected.
BINARY OF NEW process does NOT MATCH BINARY which started instance
issue ALTER system SET "_disable_image_check" = TRUE TO disable these messages
Thu Sep 6 17:42:59 2007
Errors IN file /u01/app/oracle/admin/+ASM/udump/+asm1_ora_18973.trc:
ORA-07445: exception encountered: core dump [pfrrun_no_tool()+113] [SIGSEGV] [Address NOT mapped TO object] [0x4000000070F898E3] [] []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
Thu Sep 6 17:42:59 2007
Errors IN file /u01/app/oracle/admin/+ASM/udump/+asm1_ora_18973.trc:
ORA-07445: exception encountered: core dump [pfrlnitinit()+801] [SIGSEGV] [Address NOT mapped TO object] [0x000001000] [] []
ORA-07445: exception encountered: core dump [pfrrun_no_tool()+113] [SIGSEGV] [Address NOT mapped TO object] [0x4000000070F898E3] [] []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
ORA-06544: PL/SQL: internal error, arguments: [], [interpreter cannot interpret pcode], [], [], [], [], [], []
WARNING: Oracle executable BINARY mismatch detected.
BINARY OF NEW process does NOT MATCH BINARY which started instance
issue ALTER system SET "_disable_image_check" = TRUE TO disable these messages

这个错误信息和Bug 10322959 – Various ORA-7445s from PL/SQL code run by the job scheduler [ID 10322959.8]描述的比较接近,其中pfrrun_no_tool错误和pfrlnitinit错误在文档中都有体现,且错误发生在PL/SQL代码中也和文档描述的一致。唯一的区别在于这个文档描述的版本是11.1及以上,而当前错误发生在10.2版本上,且是ASM实例。
如果不是Bug 10322959,那么根据错误信息,问题应该与Oracle的可行性文件发生改变有关。在整个告警日志中,Oracle可执行二进制文件不匹配的问题都引发了这两个ORA-7445错误。
也就是说只要避免Oracle executable binary mismatch问题的产生就可以避免这两个错误的产生,而一般来说导致二进制文件改变的因素只有几种,排除人为破坏之外,一般与操作系统上的权限或目录的改变以及Oracle版本的升级有关。

Posted in NEWS | Tagged , , , , | Leave a comment

ORA-7445(kssdct)和ORA-7445(kssdch)错误

Oracle 10.2.0.5数据库出现这两个ORA-7445错误后,导致实例CRASH。
很严重的问题,这个错误会直接导致实例的CRASH,而作为Oracle的10.2的最终版出现这个的错误不太应该。
错误信息为:

Mon Oct 31 12:13:21 CST 2011
Errors IN file /u01/oracle/admin/orcl/udump/orcl_ora_23475.trc:
ORA-07445: exception encountered: core dump [kssdct()+94] [SIGSEGV] [Address NOT mapped TO object] [0x000026D1B] [] []
Mon Oct 31 12:13:24 CST 2011
Errors IN file /u01/oracle/admin/orcl/bdump/orcl_pmon_29355.trc:
ORA-07445: exception encountered: core dump [kssdch()+2188] [SIGSEGV] [Address NOT mapped TO object] [0x000026D2B] [] []
Mon Oct 31 12:13:26 CST 2011
Errors IN file /u01/oracle/admin/orcl/bdump/orcl_pmon_29355.trc:
ORA-00602: internal programming exception
ORA-07445: exception encountered: core dump [kssdch()+2188] [SIGSEGV] [Address NOT mapped TO object] [0x000026D2B] [] []
Mon Oct 31 12:13:26 CST 2011
PMON: terminating instance due TO error 602
Instance TERMINATED BY PMON, pid = 29355

可以看到出现了两个ORA-7445错误后,直接导致了ORA-602的错误,随后PMON进程终结了数据库实例。
这个错误的详细描述为:ORA-7445 [kssdct()] Followed BY ORA-602, ORA-7445 [kssdch()] From PMON Crashing The Instance [ID 1281101.1],Oracle的PMON进程在尝试清理一个SQL*NET连接的中断会话时,导致实例崩溃。导致这个问题的原因是修正Bug:6887866引入了错误,改问题对应的内部Bug:9184754。
解决问题的方法是升级或打补丁,将数据库升级到10.2.0.5.4或11.2.0.2可以解决该问题,或者直接应用PATCH 9184754。

Posted in BUG | Tagged , , , , , , | Leave a comment

ORA-600(kcblasm_1)错误

在10.2.0.5上碰到这个错误。
其实以前这个错误也碰到过几次,但是不是9.2上,就是在10.2.0.4以前的版本,因此导致错误产生的bug,肯定与当前环境下不同。
错误信息其实很简单:

Mon Aug 22 14:14:51 CST 2011
Errors IN file /u01/db/oracle/admin/orcl/udump/orcl_ora_7848.trc:
ORA-00600: internal error code, arguments: [kcblasm_1], [103], [], [], [], [], [], []

查询MOS,该问题的描述为:ORA-600 [kcblasm_1] In 10.2.0.5. [ID 1133845.1],这个错误在以前的版本中已经被FIXED,但是在10.2.0.5中解决BUG 7523755时,又一次被引入。
Oracle目前除了升级和打补丁外,没有其他的方面避免该错误。将数据库升级到10.2.0.5.4和11.2可以修正该问题。此外,对于10.2.0.5.0到10.2.0.5.3的版本,还可以直接打PATCH 7612454来避免改错误。

Posted in BUG | Tagged , , | Leave a comment

ORA-7445(kcsgrsn)错误(二)

之前记录过ORA-7445 [kcsgrsn]错误,但是上次记录的原因与SHUTDOWN有关,而这次显然是不一样的。
ORA-7445(kcsgrsn)错误:https://yangtingkun.net/?p=519
错误信息为:

Mon May 28 10:13:49 2012
Errors IN file /u01/app/oracle/admin/orcl/udump/orcl_ora_27407.trc:
ORA-03135: connection lost contact
Mon May 28 10:13:50 2012
Errors IN file /u01/app/oracle/admin/orcl/udump/orcl_ora_27407.trc:
ORA-07445: exception encountered: core dump [kcsgrsn()+336] [SIGSEGV] [Invalid permissions FOR mapped object] [0x0000006EC] [] []
ORA-03135: connection lost contact
Mon May 28 10:13:51 2012
Errors IN file /u01/app/oracle/admin/orcl/udump/orcl_ora_27407.trc:
ORA-07445: exception encountered: core dump [kcsgrsn()+336] [SIGSEGV] [Invalid permissions FOR mapped object] [0x0000006EC] [] []
ORA-07445: exception encountered: core dump [kcsgrsn()+336] [SIGSEGV] [Invalid permissions FOR mapped object] [0x0000006EC] [] []
ORA-03135: connection lost contact

发生错误前后都没有关闭数据库的信息,不过每次出现ORA-7445错误,都伴随着ORA-3135错误的产生,显然二者有直接的关系。
根据MOS上记录的信息,除了上一篇文章的由于数据库关闭导致这个问题之外,还有一种可能性,就是在进行redo的dump时可能引发这个错误。参考文档Ora-07445: Core Dump In Kcsgrsn [ID 418723.1],这个问题影响的版本从10.2.0.1一直到11g,可能在任何的平台上出现。但是这个ORA-600错误并非是问题的根本原因,而是由于其他原因导致会话异常,在进行REDO信息的DUMP时,引发了问题。常见引发这个ORA-600的错误就包括ORA-3135错误。
Oracle确认这个问题属于bug 5640904,除了针对该bug打补丁外,Oracle给出的建议是避免会话的意外中止。

Posted in BUG | Tagged , , , , | Leave a comment

ORA-600(16480)错误

告警日志出现ORA-600 [16480]错误。
数据库版本为10.2.0.4 RAC,详细错误信息为:

Mon Mar 12 23:41:27 2012
PMON failed TO acquire latch, see PMON dump
Mon Mar 12 23:41:54 2012
Errors IN file /home/oracle/admin/orcl/bdump/orcl2_s004_942128.trc:
ORA-00600: internal error code, arguments: [16480], [111], [0x70000080A1A5248], [], [], [], [], []
Mon Mar 12 23:41:55 2012
Trace dumping IS performing id=[cdmp_20120312234155]

在ORA-600错误出现之前,出现了PMON failed to acquire latch, see PMON dump错误信息,显然这个600错误的出现与无法获取全局拴锁有直接的关系。
查询MOS,找到一个类似的BUG描述ORA-600 [16480], [201] Followed by ORA-569 in One Instance of a RAC Database [ID 603650.1]。ORA-569错误就是无法获取全局队列锁,这与当前的现象非常相似,而且这个问题发生的版本为10.2.0.1到10.2.0.4,这也与当前的版本相符。
不同之处在于,Bug中描述的问题的原因是另外一个节点上出现ORA-4031错误,由于资源不足,导致当前节点获取全局锁失败。而当前环境中,另外一个节点并没有任何的错误和告警信息出现。
除了ORA-4031之外,如果另一个节点执行了RESTRICTED SESSION也会导致类似的问题,显然这个ORA-600[16480]错误是无法获取全局锁导致的,而一般来说,无法获取锁与资源不足或限制会话等有关。

Posted in BUG | Tagged , , , , , | Leave a comment

ORA-7445(jtc_active_clint_init_ncomp_slots)错误

在10.2.0.4 RAC环境中,发现了这个错误。
错误信息如下:

Mon Mar 12 11:38:25 2012
Errors IN file /home/oracle/admin/orcl/bdump/orcl2_s005_1032420.trc:
ORA-07445: exception encountered: core dump [jtc_active_clint_init_ncomp_slots+0094] [SIGSEGV] [Address NOT mapped TO object] [0x8001000A014C0B8] [] []
Mon Mar 12 11:38:27 2012
Trace dumping IS performing id=[cdmp_20120312113827]
Mon Mar 12 11:38:38 2012
Thread 2 advanced TO log SEQUENCE 278518 (LGWR switch)
CURRENT log# 10 seq# 278518 mem# 0: +DATA/orcl/onlinelog/group_10.4560.748347669
CURRENT log# 10 seq# 278518 mem# 1: +DATA/orcl/onlinelog/group_10.5517.748347669
Mon Mar 12 11:38:49 2012
found dead shared server 'S005', pid = (52, 185)

这个错误非常少见,查询MOS系统,只有一两篇文章涉及到ORA-7445 [jtc_active_clint_init_ncomp_slots+0094]错误,但是这些文章描述的情况与当前碰到的错误还是有很大出入的。
根据报错信息的函数名以及MOS中相关文章的描述,这个错误和JVM有关。从而报错信息本身分析,问题发生在共享连接会话上,而且在错误发生后,Oracle发现了报错的共享连接进程已经变成了死进程。
这个错误发生了两次后,该节点由于调整系统时间导致了重启,而重启之后,这个问题没有再次出现。根据这些信息推测,应该是共享连接方式状态异常导致的。将导致这个错误的会话改为专用连接方式,就可以避免错误的产生。

Posted in BUG | Tagged , , , , | Leave a comment