我們生産伺服器中的一個資料庫發出監控告警日志的郵件，内容如下所示，在31号09:11分出現了大名鼎鼎的ora-00600錯誤。
dear all:
the instance xxx' alert log occured the ora errors ,please see the detail blow and take action for it. many thanks!
----------------------------------------- the errors is blow-----------------------------------------------
56 | mon mar 31 09:11:33 2014 | ora-00600: internal error code, arguments: [17281], [1001], [0x1ff863ee8], [], [], [], [], []
57 | mon mar 31 09:11:33 2014 | ora-01001: invalid cursor
---------------------------------------------end of errors--------------------------------------------------
從oracle metalink上查到如下内容：
applies to:
oracle
database - enterprise edition - version 9.2.0.1 to 11.2.0.0. [release
9.2 to 11.2] information in this document applies to any platform.
*** checked for relevance on 5-jun-2013 ***
you are seeing the following error message when running queries.:
ora-00600: internal error code, arguments: [17281], [1001], [0x18e3ee690], [], [], [], [], []
you may or may not see this error message as well.:
ora-01001: invalid cursor
this issue can be related to running sql through toad.
you can check if toad was the client that resulted in the error from the process state dump in the trace file, it will show:
program: toad.exe / application name: toad.exe
solution
you can also overcome this by patching the oracle client software as follows.:
1. fix
unpublished bug 4359111, if the oracle software is 10.1.0.4 or below.
patches for this bug can be found on my oracle support under patch:4359111.
2. fix unpublished bug 5910901 by applying patch:5910901 if the oracle software is 10.1.0.5 or above,
3. apply the 10.2.0.4 patch set or above on the client.
4. you can change the non-oracle client software being used,
5. you can just ignore the error as it is non-corruptive.
6. run the queries directly through sqlplus instead of using toad.
note:
ensure
that your version of toad is compatible with the version of the
database as well. if the errors continue when using toad, but not with
sql*plus, contact toad support to request a fix.
我
資料庫報錯為ora-00600: internal error code, arguments: [17281], [1001],
[0x1ff863ee8], [], [], [], [], [] ,但是metalink文檔錯誤為ora-00600: internal
error code, arguments: [17281], [1001], [0x18e3ee690], [], [], [], [],
[]，即隻是細微差别。那麼到底是不是toad.exe引起的還很難說。于是檢查告警日志檔案。
errors in file /u01/app/oracle/admin/scm2/bdump/scm2_s001_23744.trc:
ora-00600: internal error code, arguments: [17281], [1001], [0x1ff863ee8], [], [], [], [], []
mon mar 31 09:29:21 2014
接下來我去檢視/u01
/app/oracle/admin/scm2/bdump/scm2_s001_23744.trc檔案，看能否在trace檔案中找到
program: toad.exe / application name:
toad.exe,如果能找到那麼就可以斷定這個錯誤跟metalink描叙的錯誤是一緻的。如下所示。
從metalink上的解決方案來看， 第1、2點都可以忽略,因為我們版本為oracle database 10g release 10.2.0.4.0 - 64bit production。而我找到那位同僚，确認其使用的oracle用戶端程式為oracle 8i版本.是以，要解決這個bug，可以通過更新用戶端應用程式解決。