Menu de navegação

[LuislivelliParticipante]

Bom dia colegas, por favor, alguem poderiame explicar sobre este erro encontrado no alert log de uma instancia Oracle:

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

Agardeço pelo ajuda!!!

Att

Luis

[Fábio PradoParticipante]

@Luislivelli,

Olhe abaixo o que eu peguei no MOS. Existem vários motivos que podem estar causando este erro. Leia a nota da Oracle e tente aplicá-la em seu ambiente:

Troubleshooting ORA-3137 [12333] Errors Encountered When Using Oracle JDBC Driver [ID 1361107.1] To Bottom
Modified:04-Oct-2012Type:TROUBLESHOOTINGStatus:PUBLISHEDPriority:1
Comments (0)

In this Document
Purpose
Troubleshooting Steps
Known Issues
Unpublished Bug:8625762 – ORA-3137 [12333] due to bind data not read from wire
Unpublished Bug:9703463 – ORA-3137 [12333] or ORA-600 [kpobav-1] When Using Bind Peeking
Unpublished Bug:9243912 – Additional diagnostics for ORA-3137 [12333] / OERI:12333
Bug 7390077 ORA-03137: TTC PROTO INTERNAL ERROR: [12333] [8] [80] [65]
Unpublished Bug 9373370 DATA BASE RETURNS WRONG CURSORID WHEN THERE IS AN ORA-01013
Troubleshooting Approaches
1. Disable Bind Peeking
2. Apply Relevant Database Patches
3. Upgrade the Database to Version 11.2.0.3
4. Contact Oracle Support if the problem still persists
References
Applies to:

JDBC – Version 10.2.0.1 to 11.2.0.3.0 [Release 10.2 to 11.2]
Oracle Server – Enterprise Edition – Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]
Information in this document applies to any platform.
Purpose

Oracle Customer Support has observed a large volume of issues reported by customers experiencing ORA-3137 [12333] and occasionally ORA-3137 [1010] errors when connecting to an Oracle RDBMS using the Oracle JDBC driver. This document enumerates troubleshooting approaches that have proven successful.

Note that while this problem may be encountered when making a JDBC connection to the database, it is rare that the problem actually comes from the JDBC driver itself. Instead, the problem usually is caused from one of a small number of database bugs.

Troubleshooting Steps

Known Issues

Unpublished Bug:8625762 – ORA-3137 [12333] due to bind data not read from wire

This bug affects RDBMS version lower than version 11.2. It is fixed in version 11.2 of the database.

It can occur intermittently, due to bind data being left unread database connection. This is a bind peeking bug.

This bug is also known for causing
ORA-3137: TTC protocol internal error : [1010] [] [] [] [] [] [] []

Unpublished Bug:9703463 – ORA-3137 [12333] or ORA-600 [kpobav-1] When Using Bind Peeking

This bug affects versions 11.1.0.6, 11.1.0.7, and 11.2.0.1 of the RDBMS. It is fixed in version 11.2.0.2 of the database.

It can also occur intermittently; similarly to unpublished Bug:8625762, this is a bind peeking bug.

Unpublished Bug:9243912 – Additional diagnostics for ORA-3137 [12333] / OERI:12333

This bug affects versions of the RDBMS lower than version 11.2.0.2. It is fixed in version 11.2.0.2 of the database.

This bug addresses scenarios in which the ORA-3137 [12333] error occur bind issues during the client/server communication process. When this particular bug is fixed, the result may be the uncovering of an additional, more descriptive error: ORA-600 [kpobav-1]

Bug 7390077 ORA-03137: TTC PROTO INTERNAL ERROR: [12333] [8] [80] [65]

This bug affects the RDBMS 11.1.0.6 and is resolved with RDBMS 11.1.0.7.

typical errors:
ORA-03137: TTC protocol internal error : [12333] [10] [83] [74] [] [] [] []
ORA-03137: TTC protocol internal error : [12333] [7] [120] [108] [] [] [] []

example stack:

ORA-03137: TTC protocol internal error : [12333] [7] [120] [108] [] [] [] []
—– Current SQL Statement for this session (sql_id=c0czhbm4hcz98) —–
DELETE FROM PORTAL_CONCURRENT_USER_SCRATCH
WHERE LAST_LOGIN alter system set “_optim_peek_user_binds”=false;

If the ORA-3137 [12333] error no longer reproduces after disabling bind peeking, then in most cases, the problem is due to one of the bugs listed above, or due to some variant of one of those bugs.

Note: disabling bind peeking can have an impact on the database. Specifically, it can alter the explain plan for some queries that use bind variables. This should be taken into account, particularly before considering the use of this option as a long-term workaround.

1. Apply Relevant Database Patches

Whenever possible, the recommended solution when running a database version 11.1.0.7 is to apply the most recent PSU patch.
PSU 11.1.0.7.8 Patch 12419384 includes 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 individually but requires PSU 11.1.0.7.6

Patch:8625762 may also be applicable to databases version 11.1.0.7

If you have disabled bind peeking as a test, and the error no longer reproduces, then applying one of these patches would be the next step.

Alternatively, if you are unable to disable bind peeking for some reason, you may consider applying one of these patches as a diagnostic test in itself, to confirm whether the patch fixes the problem for you.

1. Upgrade the Database to Version 11.2.0.3

All of the above bugs are fixed in version 11.2.0.3 of the database.

1. Contact Oracle Support if the problem still persists

For JDBC connections that have resulted in the ORA-3137 error, the above database-centric approaches have resolved the issue almost all of the time. If disabling bind peeking has no effect and the ORA-3137 [12333] still occurs, please contact Oracle Support, as this is a relatively rare scenario in which further investigation is needed.

References

BUG:7390077 – ORA-03137: TTC PROTO INTERNAL ERROR: [12333] [8] [80] [65]
BUG:7573690 – OCCASIONAL ORA-03137 [12333] AND PROTOCOL VIOLATION AFTER UPGRADE TO 11.1.0.6
BUG:7607470 – ORA-03137: TTC PROTO INTERNAL ERROR: [12333] [5] [196] [28]
BUG:8490909 – ORA-03137: TTC PROTOCOL INTERNAL ERROR : [12333] [7] [84] [69] [] [] [] []
@ BUG:8625762 – PHSB: OCI CLIENT REPORTED ORA-03137:[1010] AND [12333] A/F CLIENT FAILOVER
@ BUG:9243912 – TB_X64: ORA-03137: TTC PROTOCOL INTERNAL ERROR : [12333]
@ BUG:9703463 – APPS_BM_WKLDSTS: APPS ENCOUNTERED ORA-03137 WHILE BENCHMARK REPLAY
NOTE:752297.1 – ORA-03137: TTC Protocol Internal Error : [12333] Using JDBC Driver
NOTE:8625762.8 – Bug 8625762 – ORA-3137 [12333] due to bind data not read from wire
NOTE:9243912.8 – Bug 9243912 – Additional diagnostics for ORA-3137 [12333] / OERI:12333
NOTE:9703463.8 – Bug 9703463 – ORA-3137 [12333] or ORA-600 [kpobav-1] When Using Bind Peeking – superceded
NOTE:9373370.8 – Bug 9373370 – The wrong cursor may be executed by JDBC thin following a query timeout / ORA-3137 [12333]
@NOTE:1341189.1 – How to Diagnose ORA-03137 [12333] or [1010] as Either Database or JDBC Issues

Att,

Fábio Prado
http://www.fabioprado.net

[LuislivelliParticipante]

Fábio, muito obriago pelos alcançes

[Autor]

Posts