遭遇ora-600 [qkacon:FJswrwo], [3] oracle 10.2.0.4 bug

paulyibinyi發表於2010-03-11

  最近幫客戶巡檢資料庫時,在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  

Bug 6521934  OERI[qkacon:FJswrwo] from CONNECT BY query

 This note gives a brief overview of bug 6521934.
 The content was last updated on: 27-MAY-2009
 Click for details of each of the sections below.

Affects:

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)

Fixed:

This issue is fixed in

Symptoms:

Related To:

  • _OPTIMIZER_CONNECT_BY_COST_BASED

Description

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部落格 ” ,連結:http://blog.itpub.net/7199859/viewspace-629284/,如需轉載,請註明出處,否則將追究法律責任。

相關文章