ORA-03137: TTC protocol internal error : [12333] [6] [3] [8] [] [] [] []

By
Cause:
======
This error is only affecting the session seeing the error. This error does not relate to any potential data corruption or any data loss.
This error is only telling us that the client and server process communication was terminated due to some event.
Most of the customers tried workaround of setting "_optim_peek_user_binds"=false to avoid this problem
OR
In Some cases
Bug 18841764 Network related error like ORA-12592 or ORA-3137 or ORA-3106 may be signaled
Network/TTC related error ORA-12592, ORA-3137, ORA-3106 may be signaled on SQL*Net TCP/IP transport.
Usually this problem is seen with following circumstances.
- Sending large size data to database server, for example, using sqlldr, expdp
Solution:
=========
workaround 1
============
one time occurrences can be safely ignored as there wasn't any impact.
OR
If error is consistent,

SQL> alter system set "_optim_peek_user_binds"=false;
Restart the db instance and listener.

Impact:It disables bind peeking and therefore affects execution plans that depend on this feature this is slight query performance impact but
nothing on network.
and
For Bug 18841764 the solution is as follows
============
Workaround 2
============
set sqlnet.send_timeout to any value except 0 on the server and client. In a previous incident setting it to 600 resolved the issue.
Example
sqlnet.send_timeout=600
OR
Apply one off patch 18841764 which is available on base version.
patch not available for 11203 on HP-UX Itanium
NOTE==>11203 is out of premier support and needs exception license to get any new patches or file new bug. As per our records CSI 13872399 do
not have exception license.

Comments

Post a Comment

Popular posts from this blog

Shareplex some commands

By
Shareplex some commands i will post here and update in this post with more commands later, if i provide with example so post become lengthy so please to understand. =====================================================================   sp_ctrl  :- Shareplex provides a command line utility called    'sp_ctrl'   this  sp_ctl located in  <product_directory>/bin  ($SP_HOME/bin)  , if you set profile in os level you easy redirect location. Below i will give commands run under  sp_ctrl  sp_ctrl (xxx)>   show config   ==> To check the active configuration (source side). sp_ctrl (xxx)>   show log reverse  ==> To check the log file sp_ctrl (xxx)>  show  ==>   command to displays status of the replication processes (Capture, Read, Export, Import and Post) . sp_ctrl (xxx)>  status  ==> command from sp_ctrl utility that provides an overview on the state of Shareplex replication. sp_ctrl (xxx)>  qstatus   ==> We can monitor, t
Read more

SQL Tuning Task Creation ORA-13780: SQL statement does not exist.

By
SQL Tuning Task Creation ORA-13780: SQL statement does not exist. ================================================= example:- declare  l_sql_tune_task_id  varchar2(100); begin  l_sql_tune_task_id := dbms_sqltune.create_tuning_task (         sql_id      => 'your sql_id',         scope       => dbms_sqltune.scope_comprehensive,         time_limit  => 10800,         task_name   => 'tuning task name',         description => 'tuning task description');  dbms_output.put_line('l_sql_tune_task_id: ' || l_sql_tune_task_id); end; / declare * ERROR at line 1: ORA-13780: SQL statement does not exist. ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79 ORA-06512: at "SYS.PRVT_SQLADV_INFRA", line 125 ORA-06512: at "SYS.DBMS_SQLTUNE", line 655 solution :----  SELECT SNAP_ID FROM DBA_HIST_SQLSTAT WHERE SQL_ID='sql_id' ORDER BY SNAP_ID; ===========now create task============ declare  l_sql
Read more

ORA 700 [kskvmstatact: excessive swapping observed]

By
ORA 700 [kskvmstatact: excessive swapping observed] ======================================== One of my database down suddenly. Reason:  ORA-700 SWAP error, as the dump it's taking more that 10 minutes pmon killed the process and the database was down. this database running with less memory . Solution alter system set "_kse_die_timeout"=XX or 0 if we want to disable the pmon killer during dumping . note: The error is documented in:  -  Note:1919850.1  - 12c: Warning Message About Heavy Swapping Observation and ORA-700 [kskvmstatact: excessive swapping observed]  Because your swap memory has low values of swap in / swap out, this warning message can be safely ignored.  Given both the alert log message and ORA-700 are expected behavior for 12c, no action is required.  An enhancement request (ER) was created to change the threshold in future releases in  Bug 19495842  - CHANGE THRESHOLD IN THE SWAP WARNING IN THE ALERT_<SID>.LOG  ==============
Read more