oracle rac数据库下用sql性能监控的一个bug说明

教程发布:风哥 教程分类:ITPUX技术网 更新日期:2022-02-12 浏览学习:139

oracle rac数据库下用sql监控性能的一个bug说明

数据库环境 oracle rac + aix 5300-06
Errors in file /opt/oracle/admin/oa/bdump/oa1_s000_430442.trc
ORA-00600: internal error code, arguments: [kolaslGetLength-1], [], [], [], [], [], [], []
通过 more opt/oracle/admin/oa/bdump/oa1_s000_430442.trc
Select s.inst_id, s.username, s.sid, s.serial#, command, t.value cpu_time, i.physical_reads phy_reads, i.block_gets blk_gets,
atus, s.lockwait, q.sql_fulltext sql_text, s.sql_hash_value
FROM GV$session s, GV$sesstat t, GV$statname n, GV$sess_io i, GV$sqlarea q
WHERE s.username is not null
AND (t.value > :"SYS_B_0" or i.physical_reads > :"SYS_B_1" or i.block_gets > :"SYS_B_2")
AND s.sid = t.sid AND s.inst_id = t.inst_id AND t.statistic# = n.statistic# AND t.inst_id = n.inst_id AND = :"SYS_B_3" AND
s.sid = i.sid AND s.inst_id = i.inst_id AND s.sql_address = q.address AND s.sql_hash_value = q.hash_value AND s.inst_id = q.inst_i
d ORDER BY t.value desc
通过查询metalink 已经确认是oracle下的bug,这个是toad工具连接到数据库监控性能时导致的
要解决这个问题,必须升级到oracle 或11g
Bug 4634662 - OERI:kolaslGetLength-1 from V$SQL in RAC
文档 ID: 4634662.8 类型: PATCH
上次修订日期: 12-DEC-2008 状态: PUBLISHED
Bug 4634662 OERI:kolaslGetLength-1 from V$SQL in RAC
This note gives a brief overview of bug 4634662.
The content was last updated on: 12-DEC-2008
Click here for details of each of the sections below.
Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions < 11 Versions confirmed as being affected Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in (Server Patch Set) (Base Release) Symptoms: Related To: Internal Error May Occur (ORA-600) ORA-600 [kolaslGetLength-1] RAC (Real Application Clusters) / OPS V$SQL GV$SQL Description ORA-600[kolaslGetLength-1] selecting from V$SQL (of GV$SQL) on a RAC database with a varying width character set. Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice. References Bug 4634662 (This link will only work for PUBLISHED bugs) Note 245840.1 Information on the sections in this article