ORA-03137: TTC protocol internal error: [12333]

Oracle Database Version 11.2.0.1, operating system CentOSrelease5.9, detailed error information: ORA-03137: TTC protocol internal error: [12333]

Oracle Database Version 11.2.0.1, CentOS release 5.9 operating system, detailed error information: ORA-03137: TTC protocol internal error: [12333]

[1] problem Background: The Oracle database version is 11.2.0.1, and the operating system is CentOS release 5.9. The detailed error message is as follows:

Dump file/data/oracle/diag/rdbms/db01/db01/incident/incdir_70215/db01_ora_17588_i70215.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME =/data/oracle/oracle11
System name: Linux
Node name: db01
Release: 2.6.18-348. el5
Version: #1 SMP Tue Jan 8 17:53:53 EST 2013
Machine: x86_64
Instance name: db01
Redo thread mounted by this instance: 1
Oracle process number: 52
Unix process pid: 17588, image: oracle @ db01

* ** 22:33:42. 577
* ** Session id: (204.33501) 22:33:42. 577
* ** Client id: () 22:33:42. 577
* ** Service name :( SYS $ USERS) 22:33:42. 577
* ** Module name :() 22:33:42. 577
* ** Action name :() 22:33:42. 577
Dump continued from file:/data/oracle/diag/rdbms/db01/db01/trace/db01_ora_17588.trc
ORA-03137: TTC protocol internal error: [12333] [32] [49] [50] [] [] [] []

========= Dump for incident 70215 (ORA 3137 [12333]) ========

* ** 22:33:42. 600
DbkedDefDump (): Starting incident default dumps (flags = 0x2, level = 3, mask = 0x0)
----- Current SQL Statement for this session (SQL _id = 6v8rd0sq5a 8m3 )-----
Select count (t. fd_id) as COUNT from sys_policy_todo_done_info t inner join
(Select distinct (sysnotifyt1 _. fd_subject) FD_SUBJECT, max (sysnotifyt0 _. fd_id) as FD_ID
, Sysnotifyt1 _. fd_app_name, sysnotifyt1 _. fd_type, sysnotifyt1 _. fd_create_time
From sys_policy_todo_done_info sysnotifyt0 _ inner join sys_policy_todo sysnotifyt1 _
On sysnotifyt0 _. fd_todoid = sysnotifyt1 _. fd_id
Where (sysnotifyt0 _. fd_elementid =: 1)
Group by sysnotifyt1 _. fd_subject, sysnotifyt1 _. fd_app_name, sysnotifyt1 _. fd_type, sysnotifyt1 _. fd_create_time) f on t. fd_id = f. fd_id

----- Call Stack Trace -----
Calling call entry argument values in hex
Location type point (? Means dubious value)
----------------------------------------------------------------------------

* ** 22:33:42. 834
Skdstdst () + 36 call kgdsdst () 000000000? 000000000?
7FFF5BCF02B8? 000000001?
7FFF5BCF47B8? 000000000?
Ksedst1 () + 98 call skdstdst () 000000000? 000000000?
7FFF5BCF02B8? 000000001?
000000000? 000000000?
Ksedst () + 34 call ksedst1 () 000000000? 000000001?
7FFF5BCF02B8? 000000001?
[2] Solution

Metalink above did not find the problem of the same symptoms, errors on the ORA-03137, there are a lot of problems, common problems are JDBC, Bind Variable peeping, oracle bug, etc, metalink also provides a series of troubleshooting methods as follows:

2.1 variable binding

Solution: SQL> alter system set "_ optim_peek_user_binds" = false;

Disadvantages: disabling variable binding may lead to inaccurate execution plans when SQL statements use variable binding, to disable this feature in a production environment for a long time, you need to carefully test it;

2.2 update the latest PSU of the database. If you disable variable binding, the database will not report an error. You can apply the latest PSU of each database. Alternatively, when binding variables is disabled, an error is reported again. You can also apply the PSU for testing;

The PSU information is as follows:
PSU 11.1.0.7.8 Patch 12419384 except des Patch: 9703463.
For 11.1.0.7, Patch 9243912 can be applied on top of 11.1.0.7.8 (no conflict ).
Patch: 9703463 can also be applied inpidually but requires PSU 11.1.0.7.6
Patch: 8625762 may also be applicable to databases version 11.1.0.7
2.3 update the database to 11.2.0.3.
All ORA-3137 errors can be addressed in ORACLE 11.2.0.3;

2.4 Contact oracle support to solve this problem after the above operations, you have all stepped on this mine, indicating that the landlord is burning less incense at ordinary times, you need to contact ORALCE's great gods;

[3] Conclusion: After verification, the system set "_ optim_peek_user_binds" = false indicates that the error will disappear;