数据库出现ORA-00600: 内部错误代码, 参数: [12333], [7], [196], [13], [], [], [], []
请前辈们帮忙诊断一下
操作系统：HP-UX 11.31
数据库：10.2.0.5
alert日志中报错堆栈，上传到百度云，麻烦各位前辈下载看看
百度网盘

ORA-00600: 内部错误代码, 参数: [12333], [7], [196], [13], [], [], [], []
Current SQL statement for this session:
SELECT OBJECTID ,V__930.st_SHAPE$,V__930.st_points,V__930.st_numpts,V__930.st_entity,V__930.st_minx,V__930.st_miny,V__930.st_maxx,V__930.st_maxy,V__930.st_area$,V__930.st_len$,V__930.st_rowid FROM (SELECT b.OBJECTID ,1 st_SHAPE$,b.SHAPE.points as st_points,b.SHAPE.numpts as st_numpts,b.SHAPE.entity as st_entity,b.SHAPE.minx as st_minx,b.SHAPE.miny as st_miny,b.SHAPE.maxx as st_maxx,b.SHAPE.maxy as st_maxy,b.SHAPE.area as st_area$,b.SHAPE.len as st_len$,b.rowid as st_rowid FROM SDE.lv_capacity b WHERE SDE.ST_EnvIntersects(b.SHAPE,:1,:2,:3,:4) = 1 AND b.OBJECTID NOT IN (SELECT /*+ HASH_AJ */ SDE_DELETES_ROW_ID FROM SDE.D930 WHERE DELETED_AT IN (SELECT l.lineage_id FROM SDE.state_lineages l WHERE l.lineage_name = :lineage_name1 AND l.lineage_id <= :state_id1) AND SDE_STATE_ID = 0) UNION ALL SELECT a.OBJECTID ,2 st_SHAPE$,a.SHAPE.points as st_points,a.SHAPE.numpts as st_numpts,a.SHAPE.entity as st_entity,a.SHAPE.minx as st_minx,a.SHAPE.miny as st_miny,a.SHAPE.maxx as st_maxx,a.SHAPE.maxy as st_maxy,a.SHAPE.area as st_area$,a.SHAPE.len as st_len$,a.rowid as st_rowid FROM SDE.A930 a,SDE.state_lineages SL WHERE SDE.ST_EnvIntersects(a.SHAPE,:5,:6,:7,:8) = 1 AND (a.OBJECTID, a.SDE_STATE_ID) NOT IN (SELECT /*+ HASH_AJ */ SDE_DELETES_ROW_ID, SDE_STATE_ID FROM SDE.D930 WHERE DELETED_AT IN (SELECT l.lineage_id FROM SDE.state_lineages l WHERE l.lineage_name = :lineage_name2 AND l.lineage_id <= :state_id2) AND SDE_STATE_ID > 0) AND a.SDE_STATE_ID = SL.lineage_id AND SL.lineage_name = :lineage_name3 AND SL.lineage_id <= :state_id3) V__930
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst()+64 call ksedst1() 000000000 ? 000000001 ?
ksedmp()+2176 call ksedst() 000000000 ?
C000000000000D20 ?
400000000406C0C0 ?
000000000 ? 000000000 ?
000000000 ?
ksfdmp()+112 call ksedmp() 000000003 ?
--------------------
PROTOCOL VIOLATION
--------------------
-----Page before-----
00000033B530 11 69 1E 01 01 01 02 01 32 03 5E 1F 02 80 79 00 [.i......2.^...y.]
00000033B540 01 02 0C 28 01 01 0D 00 01 00 01 01 02 0F A0 01 [...(............]
00000033B550 01 0E 00 00 00 00 01 01 01 0C 00 00 01 FE 40 53 [..............@S]
00000033B560 45 4C 45 43 54 20 20 4F 42 4A 45 43 54 49 44 20 [ELECT OBJECTID ]
00000033B570 20 2C 56 5F 5F 39 33 30 2E 73 74 5F 53 48 41 50 [ ,V__930.st_SHAP]
00000033B580 45 24 2C 56 5F 5F 39 33 30 2E 73 74 5F 70 6F 69 [E$,V__930.st_poi]
00000033B590 6E 74 73 2C 56 5F 5F 39 33 30 2E 73 74 5F 6E 40 [nts,V__930.st_n@]
00000033B5A0 75 6D 70 74 73 2C 56 5F 5F 39 33 30 2E 73 74 5F [umpts,V__930.st_]
00000033B5B0 65 6E 74 69 74 79 2C 56 5F 5F 39 33 30 2E 73 74 [entity,V__930.st]
00000033B5C0 5F 6D 69 6E 78 2C 56 5F 5F 39 33 30 2E 73 74 5F [_minx,V__930.st_]
00000033B5D0 6D 69 6E 79 2C 56 5F 5F 39 33 30 2E 73 74 5F 6D [miny,V__930.st_m]
00000033B5E0 40 61 78 78 2C 56 5F 5F 39 33 30 2E 73 74 5F 6D [@axx,V__930.st_m]
00000033B5F0 61 78 79 2C 56 5F 5F 39 33 30 2E 73 74 5F 61 72 [axy,V__930.st_ar]
00000033B600 65 61 24 2C 56 5F 5F 39 33 30 2E 73 74 5F 6C 65 [ea$,V__930.st_le]
00000033B610 6E 24 2C 56 5F 5F 39 33 30 2E 73 74 5F 72 6F 77 [n$,V__930.st_row]
00000033B620 69 40 64 20 46 52 4F 4D 20 28 53 45 4C 45 43 54 [i@d FROM (SELECT]
00000033B630 20 62 2E 4F 42 4A 45 43 54 49 44 20 2C 31 20 73 [ b.OBJECTID ,1 s]

10.2.0.5.0 + HP-UX B.11.31 ia64 + RAC
12333 常见的一些solution 如下， 你的case 当中使用了绑定变量 ， 似乎没哟用JDBC （只是通过看module猜测）
For any ONE-TIME occurrence we can safely ignore the error. This error does not cause to any potential data corruption or any data loss. Check Note 35928.1 for known issues and two basic usages of OERI(12333):
Usage with 3 additional numeric values
Usage with 4 additional values ... new since 8.0.X
In case the errors are seen consistently and no known issues matches to your issue then do the following
Common Causes & Solutions:
1. Check the client software version. An incompatible client software is a common cause of this error. Upgrade the client software to current version (i.e. match the server version).
The following note explains the supported combinations of clients for a particular RDBMS Server release.
Note 207303.1 Client / Server / Interoperability Support Between Different Oracle Versions
Similar issues are reported when the client installation is faulty.
2. An incompatible NLS Client setting can also trigger such internal errors. Check the NLS settings as explained in the following note.
Note 77442.1 ORA_NLS (ORA_NLS32, ORA_NLS33, ORA_NLS10) Environment Variables explained
3. There are a number of bugs associated with the use of bind peeking. Turn off bind peeking as follows:
alter system set "_optim_peek_user_binds"=false;
4. Please review your listener.log and SQLNET log for network errors at the time of the ORA-600[12333] errors. Correct these errors.
Try to reproduce the issue from a different client machine, preferably from server. This will rule out the possibility of bad network. If the execution fails from a particular client then it could be due to the bad network from that client to server. The error ORA-600[12333] could occur when a request is being received from a network packet and the request code in the packet is not recognized.
5. Ask your sysadmin to correct any network delays. A slow network can lead to this error.
6. If the error still continues , then do the following to understand from where the error is generated.
We need to understand which session/program/application that triggers this issue. This shall be found from the trace files under the session state object '(session)'. Sometimes the ORA-00600 [12333] trace files will not capture the session information. In such cases we can check with the end users about any issues around the time-frame of this internal error.
There is a HIGH chance for application run-time exception to lead to this ORA-00600 [12333]. Due to the unhandled exceptions there is a chance for incomplete information passed to the server hence the internal errors are raised. In such cases, handling those exceptions (or) addressing those errors on the application code will resolve the issue.
In few cases, the problem application will work for a while before it terminates with the error. This could be due to the TIMEOUT settings at the Application Server (or) Forms Server.,etc. To resolve this either tune the failing application to complete within the TIMEOUT value (or) reset the TIMEOUT to an optimal value.
There could be more possibilities here; in simple words the approach should be from application side, which would help us to understand the other issues that triggered this network interruption (ORA-00600 [12333]).
Check the 'Current SQL Statement' section of the incident trace files. Does each trace file point to the same SQL statement. If so, there may be a problem with the code.
7. If you notice JDBC Client as the failing program under Session state object, please check the following
That you use latest compatible version of JDBC Drivers in your application side.
Note 430839.1 to verify the version of JDBC Drivers and for Installation steps.
Monitor and try to handle correctly the timeouts from the application
Check that idle or died programs/processes are not just killed at the client side but using a good cleaning procedure.
Increase queue sizes / buffers and similar from the jdbc side.
Further diagnostics regarding JDBC Application driver can be found:
Note 1361107.1 Suggestions For Troubleshooting ORA-3137 [12333] Errors Encountered When Using Oracle JDBC Driver
8. For database version 11.2.0.4 and above, you may encounter this error during a SQL*Net TCP/IP transport.
To determine if you encountered this bug, check your alert log for
ORA-12592 or ORA-3106
and check your incident trace file for
'SQL*Net TCP/IP' or 'TCP/IP'
If any of these exist, proceed with the solution below:
1.
The fix for 18841764 will be included in 12.2 database release. This was not available at the time of writing.
2.
Download and apply patch 18841764 if it is available for your platform.
3.
Workaround the error by setting
sqlnet.send_timeout to any value except 0 on the server and client. In a previous incident setting it to 600 resolved the issue.
9. In-case if all the above suggestions does not help to identify the cause, and the ORA-00600 [12333] persists we may need to enable the networking tracings from the problem client and need to review the network traces to understand where the problem occurs. See Note 219968.1 Title: SQL*Net, Net8, Oracle Net Services - Tracing and Logging at a Glance. Check the network logs for errors and fix them with the network administrator.
E.g.:
ifconfig -a
=======
eth0 Link encap:Ethernet HWaddr ...
...
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7855996 errors:288 dropped:291 overruns:0 frame:0
TX packets:9874201 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1325085201 (1263.6 Mb) TX bytes:1313633137 (1252.7 Mb)
Interrupt:9 Base address:0x1080
In this case the network administrator should investigate the RX packets errors listed above (RX packets:7855996 errors:288 dropped:291).