Occasional ORA-12592 (TNS:BAD PACKET) and ORA-03137  When Running SQL*Loader Jobs
Last updated on MAY 07, 2018
Applies to:Oracle Net Services - Version 188.8.131.52 to 184.108.40.206 [Release 11.2 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 04-Jan-2016***
When running several SQL*Loader jobs on 220.127.116.11 or higher, you notice that sometimes one of the jobs fails with following errors:
ORA-12592: TNS: Bad Packet
SQL*Loader-604: Error occurred on an attempt to commit
ORA-03113: end-of-file on communication channel
Process ID: 16057148
Session ID: 3541 Serial number: 47955
SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.
Specify SKIP=xx when continuing the load.
The alert logfile shows the following error:
Sat Jul 05 11:42:48 2014
Errors in file /oracle_base/diag/rdbms/ORCL/ORCL/trace/ORCL_ora_16057148.trc (incident=247676):
ORA-03137: TTC protocol internal error:        
Incident details in: /oracle_base/diag/rdbms/ORCL/ORCL/incident/incdir_247676/ORCL_ora_16057148_i247676.trc
Sat Jul 05 11:42:52 2014
Dumping diagnostic data in directory=[cdmp_20140705114252], requested by (instance=1, osid=16057148), summary=[incident=247676].
The errors are occasional: if the load is re-run then it is likely that the sqlldr job now succeeds without errors.
Other possible errors:
ORA-25402: transaction must roll back
ORA-12152: TNS:unable to send break message
ORA-12592 TNS: Bad Packet
You recently upgraded to 18.104.22.168 and are loading data to the database server with SQL*Loader.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms