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

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


even though i post same error before but with diffrent argument 
these internal errors have any arguments and many soluotions .


 [12333] [255] [255] [255] [] [] [] []

solution 

Add this parameter to the sqlnet.ora file at BOTH the origin (or client) and at the server , instance: 

SQLNET.SEND_TIMEOUT=n 

Where n is a value in seconds. The setting itself, and not the value, should resolve this issue so a relatively high setting eliminate this problem. 

E.g. 

SQLNET.SEND_TIMEOUT=60000 

Thanks for the visit !

 Any doubts or correction/suggestions, please comment below it helps me to improve in further posts.


--------above sol not resolved after apply so for this 3137 traditional parameter we applied for fix

Hello Dipak - Please verify/perform the following and let us know the status. 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;    ==> apply and fix please note in some rare cases this parameter causes performance degradation,  as this hidden parameters harmful do not apply simply with out oracle or expert suggestion

ORA-1092 : opitsk aborting process

sharing
This error shown when load high from database and unix server(as we have unix type veritas cluster

) detect hang and db failover to another node.

even in alertlog show only one errror and no other info(no trace file generation) trace cause so 

in this case below is help to trace(generate trace file immediate when impact time by using below mentod) and raise case to vedor and upload trace file(even if you can able to trace cause from file as you can)

Hanganalyze need to be collected when the situation occurs, below are the steps to perform such task. 
Hanganalyze 
sqlplus '/ as sysdba' 
oradebug setmypid 
oradebug unlimit 
oradebug hanganalyze 3 
-- Wait one minute before getting the second hanganalyze 
oradebug hanganalyze 3 
oradebug tracefile_name 
exit 

Thanks for the visit !

 Any doubts or correction/suggestions, please comment below it helps me to improve in further posts.