ORACLE11GRAC alert日誌ORA-600 [kqlnrc_1]錯誤處理
今早檢查發現DBRAC庫節點1資料庫ORA-600 [kqlnrc_1],經分析發現是透過PL/SQL Developer連上來執行儲存過程報錯,
其儲存過程使用到同義詞失效引起!
具體分析過程如下:
1、檢視alert日誌如下:
Mon Mar 03 11:04:29 2014
Sweep [inc][1992719]: completed
Sweep [inc][1992718]: completed
Sweep [inc2][1992718]: completed
Errors in file /oraclelog/diag/rdbms/dbrac1/dbrac1i1/trace/dbrac1i1_ora_61080830.trc (incident=1992720):
ORA-00600: internal error code, arguments: [kqlnrc_1], [0x70000113FC52DB8], [], [], [], [], [], [], [], [], [], []
Incident details in: /oraclelog/diag/rdbms/dbrac1/dbrac1i1/incident/incdir_1992720/dbrac1i1_ora_61080830_i1992720.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /oraclelog/diag/rdbms/dbrac1/dbrac1i1/trace/dbrac1i1_ora_61080830.trc (incident=1992721):
ORA-00600: internal error code, arguments: [kqlnrc_1], [0x70000113FC52DB8], [], [], [], [], [], [], [], [], [], []
Incident details in: /oraclelog/diag/rdbms/dbrac1/dbrac1i1/incident/incdir_1992721/dbrac1i1_ora_61080830_i1992721.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Mon Mar 03 11:04:38 2014
Errors in file /oraclelog/diag/rdbms/dbrac1/dbrac1i1/trace/dbrac1i1_ora_61080830.trc (incident=1992722):
ORA-00600: internal error code, arguments: [kqlnrc_1], [0x70000113FC52DB8], [], [], [], [], [], [], [], [], [], []
Incident details in: /oraclelog/diag/rdbms/dbrac1/dbrac1i1/incident/incdir_1992722/dbrac1i1_ora_61080830_i1992722.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2、檢視trace日誌如下:
*** 2014-03-03 11:03:22.426
*** SESSION ID:(7208.55105) 2014-03-03 11:03:22.426
*** CLIENT ID:() 2014-03-03 11:03:22.426
*** SERVICE NAME:(dbrac1) 2014-03-03 11:03:22.426
*** MODULE NAME:(PL/SQL Developer) 2014-03-03 11:03:22.426
*** ACTION NAME:(SQL Window - New) 2014-03-03 11:03:22.426
Incident 1992718 created, dump file: /oraclelog/diag/rdbms/dbrac1/dbrac1i1/incident/incdir_1992718/dbrac1i1_ora_61080830_i1992718.trc
ORA-00600: internal error code, arguments: [kqlnrc_1], [0x70000113FC52DB8], [], [], [], [], [], [], [], [], [], []
3、繼續分析DUMP檔案:
LibraryHandle: Address=70000113fc52db8 Hash=31dbed4 LockMode=S PinMode=S LoadLockMode=0 Status=INVL
ObjectName: Name=TEST_OWNER.TEST_TAB@DBLNK_TESTDB2
FullHashValue=7f26177bcf3fe188cf0fbb3d031dbed4 Namespace=TABLE/PROCEDURE(01) Type=SYNONYM(05) Identifier=0 OwnerIdn=2147483644
Statistics: InvalidationCount=2 ExecutionCount=0 LoadCount=1 ActiveLocks=1 TotalLockCount=5 TotalPinCount=5
Counters: BrokenCount=1 RevocablePointer=1 KeepDependency=0 BucketInUse=19 HandleInUse=19 HandleReferenceCount=0
Concurrency: DependencyMutex=70000113fc52e68(0, 31, 0, 0) Mutex=70000113fc52ee8(7208, 90587, 0, 6)
Flags=REM/PIN/TIM/[00022801]
WaitersLists:
Lock=70000113fc52e48[70000113fc52e48,70000113fc52e48]
Pin=70000113fc52e28[70000113fc52e28,70000113fc52e28]
LoadLock=70000113fc52ea0[70000113fc52ea0,70000113fc52ea0]
透過以上日誌我們可以看出由於在library cache中同義詞TEST_OWNER.TEST_TAB@DBLNK_TESTDB2無效導致!
4、檢視TESTDB2庫物件狀態如下:
SQL> set pagesize 10000 linesize 300
SQL> SELECT object_name,object_type,owner,status
2 FROM dba_objects
3 WHERE object_name='TEST_TAB' and owner = 'TEST_OWNER';
OBJECT_NAME OBJECT_TYPE OWNER STATUS
--------------------------- ------------------- ------------------------------ -------
TEST_TAB SYNONYM TEST_OWNER VALID
發現同義詞狀態正常,ORA-600此時在alert日誌中沒報。
綜上所述:
如果發現ORA-600錯誤一直報出,重新編譯同義詞解決問題!
詳細見官檔:
ORA-600 [kqlnrc_1] (文件 ID 1274843.1)
其儲存過程使用到同義詞失效引起!
具體分析過程如下:
1、檢視alert日誌如下:
Mon Mar 03 11:04:29 2014
Sweep [inc][1992719]: completed
Sweep [inc][1992718]: completed
Sweep [inc2][1992718]: completed
Errors in file /oraclelog/diag/rdbms/dbrac1/dbrac1i1/trace/dbrac1i1_ora_61080830.trc (incident=1992720):
ORA-00600: internal error code, arguments: [kqlnrc_1], [0x70000113FC52DB8], [], [], [], [], [], [], [], [], [], []
Incident details in: /oraclelog/diag/rdbms/dbrac1/dbrac1i1/incident/incdir_1992720/dbrac1i1_ora_61080830_i1992720.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /oraclelog/diag/rdbms/dbrac1/dbrac1i1/trace/dbrac1i1_ora_61080830.trc (incident=1992721):
ORA-00600: internal error code, arguments: [kqlnrc_1], [0x70000113FC52DB8], [], [], [], [], [], [], [], [], [], []
Incident details in: /oraclelog/diag/rdbms/dbrac1/dbrac1i1/incident/incdir_1992721/dbrac1i1_ora_61080830_i1992721.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Mon Mar 03 11:04:38 2014
Errors in file /oraclelog/diag/rdbms/dbrac1/dbrac1i1/trace/dbrac1i1_ora_61080830.trc (incident=1992722):
ORA-00600: internal error code, arguments: [kqlnrc_1], [0x70000113FC52DB8], [], [], [], [], [], [], [], [], [], []
Incident details in: /oraclelog/diag/rdbms/dbrac1/dbrac1i1/incident/incdir_1992722/dbrac1i1_ora_61080830_i1992722.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2、檢視trace日誌如下:
*** 2014-03-03 11:03:22.426
*** SESSION ID:(7208.55105) 2014-03-03 11:03:22.426
*** CLIENT ID:() 2014-03-03 11:03:22.426
*** SERVICE NAME:(dbrac1) 2014-03-03 11:03:22.426
*** MODULE NAME:(PL/SQL Developer) 2014-03-03 11:03:22.426
*** ACTION NAME:(SQL Window - New) 2014-03-03 11:03:22.426
Incident 1992718 created, dump file: /oraclelog/diag/rdbms/dbrac1/dbrac1i1/incident/incdir_1992718/dbrac1i1_ora_61080830_i1992718.trc
ORA-00600: internal error code, arguments: [kqlnrc_1], [0x70000113FC52DB8], [], [], [], [], [], [], [], [], [], []
3、繼續分析DUMP檔案:
LibraryHandle: Address=70000113fc52db8 Hash=31dbed4 LockMode=S PinMode=S LoadLockMode=0 Status=INVL
ObjectName: Name=TEST_OWNER.TEST_TAB@DBLNK_TESTDB2
FullHashValue=7f26177bcf3fe188cf0fbb3d031dbed4 Namespace=TABLE/PROCEDURE(01) Type=SYNONYM(05) Identifier=0 OwnerIdn=2147483644
Statistics: InvalidationCount=2 ExecutionCount=0 LoadCount=1 ActiveLocks=1 TotalLockCount=5 TotalPinCount=5
Counters: BrokenCount=1 RevocablePointer=1 KeepDependency=0 BucketInUse=19 HandleInUse=19 HandleReferenceCount=0
Concurrency: DependencyMutex=70000113fc52e68(0, 31, 0, 0) Mutex=70000113fc52ee8(7208, 90587, 0, 6)
Flags=REM/PIN/TIM/[00022801]
WaitersLists:
Lock=70000113fc52e48[70000113fc52e48,70000113fc52e48]
Pin=70000113fc52e28[70000113fc52e28,70000113fc52e28]
LoadLock=70000113fc52ea0[70000113fc52ea0,70000113fc52ea0]
透過以上日誌我們可以看出由於在library cache中同義詞TEST_OWNER.TEST_TAB@DBLNK_TESTDB2無效導致!
4、檢視TESTDB2庫物件狀態如下:
SQL> set pagesize 10000 linesize 300
SQL> SELECT object_name,object_type,owner,status
2 FROM dba_objects
3 WHERE object_name='TEST_TAB' and owner = 'TEST_OWNER';
OBJECT_NAME OBJECT_TYPE OWNER STATUS
--------------------------- ------------------- ------------------------------ -------
TEST_TAB SYNONYM TEST_OWNER VALID
發現同義詞狀態正常,ORA-600此時在alert日誌中沒報。
綜上所述:
如果發現ORA-600錯誤一直報出,重新編譯同義詞解決問題!
詳細見官檔:
ORA-600 [kqlnrc_1] (文件 ID 1274843.1)
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/28258625/viewspace-1348186/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-600[kqlnrc_1]錯誤分析及處理
- node錯誤處理與日誌
- oracle alert日誌亂碼處理Oracle
- node專案錯誤處理與日誌
- ORACLE 告警日誌alert過大的處理Oracle
- alert日誌中的兩種ORA錯誤分析
- ORA-600[6122]錯誤處理
- ORA-600[4000]/[4097]錯誤的處理
- 資料庫alert日誌報ORA-03137 TTC 協議內部錯誤故障分析處理資料庫協議
- oracle 中 alert 報警日誌過大的處理方法Oracle
- 水煮十三《——ora-16038日誌檔案錯誤處理
- oracle ora-600 Ktspgsb-1 錯誤處理案例Oracle
- alert日誌中出現Private Strand Flush Not Complete的處理方法
- mysql 日誌之錯誤日誌MySql
- oracle alert日誌Oracle
- 排查錯誤日誌
- ELK 處理 Spring Boot 日誌,不錯!Spring Boot
- nginx日誌處理Nginx
- 錯誤處理
- oracle資料庫歸檔日誌空間滿引起的錯誤處理Oracle資料庫
- Apche日誌系列(2):錯誤日誌(轉)
- 【問題處理】處理alert警告日誌中出現無法找到libocr*.so檔案問題
- Data guard 中 alert 日誌報錯 "FAL archive failed"HiveAI
- Mabatis配置錯誤日誌BAT
- net 日誌分析錯誤
- 日誌查詢錯誤
- 錯誤日誌檢視
- SQL Server 錯誤日誌SQLServer
- 用外部表的方式查詢alert日誌檔案中ora-錯誤資訊
- RMAN刪除歸檔日誌出現RMAN-0813錯誤的處理
- ALERT日誌中常見監聽相關報錯之一:ORA-609錯誤的排查
- ALERT日誌中常見監聽相關報錯之二:ORA-3136錯誤的排查
- oracle11gRAC之log日誌體系Oracle
- 歸檔oracle alert日誌Oracle
- 使用sql查alert日誌SQL
- PHP日誌處理類PHP
- PHP 錯誤處理PHP
- php錯誤處理PHP