最近帮客户巡检数据库时,在3月9号下午17点01时报了一个ORA-00600 [qkacon:FJswrwo], [3]错误
环境AIX 5.3+ oracle 10.2.0.4
Tue Mar 9 17:01:15 2010
Errors in file /oracle/app/oracle/admin/fsgaj/udump/fsgaj2_ora_2678886.trc:
ORA-00600: internal error code, arguments: [qkacon:FJswrwo], [3], [], [], [], [], [], []
详细trace文件如下:
qkacon: srtrwo:
[(1104f4500:30:NVL("M2"."SCHEME_ID","M1"."PARENT_ID")), (1104f4e30:30:NV
L("M1"."SCHEME_ID","M1"."ID")), (1106199b8:4:SYSVARCOL), (11061a720:10:I
NTERNAL_FUNCTION("M1"."PARENT_ID")), (11061a4e0:10:INTERNAL_FUNCTION("M2
"."ID")), (1104f4cc0:10:"M1"."ID"), (1104020f8:10:"M1"."PARENT_ID"), (11
04f4da0:30:"M1"."SCHEME_ID"), (1104f47f0:50:"M1"."DISPLAY_NAME"), (11040
1fe8:10:"M2"."ID"), (1104f49b0:30:"M2"."SCHEME_ID")]
qkacon: sw rwo:
[(1104ee3c8:10:"M1"."ID"), (1104edc78:10:"M1"."PARENT_ID"), (1104ee560:3
0:"M1"."SCHEME_ID"), (1104ee198:50:"M1"."DISPLAY_NAME"), (1105e8a88:10:"
M2".ROWID), (1104ecee0:10:"M2"."ID"), (1104ede10:30:"M2"."SCHEME_ID")]
*** 2010-03-09 17:15:00.628
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [qkacon:FJswrwo], [3], [], [], [], [], [], []
Current SQL statement for this session:
select * from INFO.V_MENU
仔细检查V_MENU的视图
有用到start with connect by 树型查询语句
START WITH A.ID = '0000000000'
CONNECT BY A.PARENT_ID = PRIOR A.ID
查询metalink 确认是bug
| Bug 6521934 - OERI[qkacon:FJswrwo] from CONNECT BY query [ID 6521934.8] | |||||
|
| |||||
| 修改时间 08-JUN-2009 类型 PATCH 状态 PUBLISHED | |||||
This note gives a brief overview of bug 6521934.
The content was last updated on: 27-MAY-2009
Click here for details of each of the sections below.
Product (Component) Oracle Server (Rdbms) Range of versions believed to be affected Versions < 11.2 Versions confirmed as being affected Platforms affected Generic (all / most platforms affected)
This issue is fixed in
Symptoms: |
Related To: |
|
A CONNECT BY query can fail with ORA-600 [qkacon:FJswrwo] if the query has operands in the join-predicate which are not also in the select list if cost based transformation occurs. Workaround Set "_OPTIMIZER_CONNECT_BY_COST_BASED" = false or Add a NO_CONNECT_BY_COST_BASED hint to the query. or Include the problem operand in the SELECT list.解决方法:Set "_OPTIMIZER_CONNECT_BY_COST_BASED" = false or Add a NO_CONNECT_BY_COST_BASED hint to the query. or Include the problem operand in the SELECT list.只能到时到用户现场改隐含参数或者改写sql语句了
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/7199859/viewspace-629284/ ,如需转载,请注明出处,否则将追究法律责任。