ORA-03120: two-task conversion routine: integer overflow

I got ” ORA-03120: two-task conversion routine: integer overflow ”  error in Oracle database.

 

ORA-03120: two-task conversion routine: integer overflow

 

Details of error are as follows.

ORA-03120 two-task conversion routine: integer overflow
 
Cause: An integer value in an internal Oracle structure overflowed when being sent or received over a heterogeneous connection. This can happen when an invalid buffer length or too great a row count is specified. It usually indicates a bug in the user application. 

Action: Check parameters to Oracle calls. If the problem recurs, reduce all integer parameters, column values not included, to less than 32767.

 

 

two-task conversion routine: integer overflow

This ORA-03120 error is related to the integer value in an internal Oracle structure overflowed when being sent or
received over a heterogeneous connection. This can happen when an invalid buffer length or too great a row count is specified. It usually indicates a bug in the user application. 

Check parameters to Oracle calls. If the problem recurs, reduce all integer parameters, column values not included, to less than 32767.

 

User started to get protocol errors through JDBC Thin clients.
When running the following query, application is getting error:

[--SQLUpdate--]
java.sql.SQLException: ORA-03120: two-task conversion routine: integer overflow

  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017)
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:655)
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:249)
  .... 25 more
  ....
Caused By: java.sql.SQLException: ORA-03120: two-task conversion routine: integer overflow

  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017)
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:655)
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:249)

The issue is caused by an application error:


Database trace file generated
===



...
*** 2018-08-28 15:46:06.281
*** SESSION ID:(<SESSION ID>) 2018-08-28 15:46:06.281
*** SERVICE NAME:(<SERVICE NAME>) 2018-08-28 15:46:06.281
*** MODULE NAME:(JDBC Thin Client) 2018-08-28 15:46:06.281
*** CLIENT DRIVER:(jdbcthin) 2018-08-28 15:46:06.281
*** ACTION NAME:() 2018-08-28 15:46:06.281

ORA-03137: TTC protocol internal error : [3120] [94] [] [] [] [] [] []


*** 2018-08-28 15:46:08.554
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=3, mask=0x0)
----- Error Stack Dump -----
ORA-03120: two-task conversion routine: integer overflow
----- Current SQL Statement for this session (sql_id=<SQL ID>) -----
<SQL STATEMENT>

----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
skdstdst()+44 bl kgdsdst() 21782DCA73AD8 ? 000000000 ?
  000000000 ? FFFFFFFFFFF4888 ?
  FFFFFFFFFFF4BE0 ? 000000000 ?
  1054975E8 ? 121667FA0 ?
ksedst1()+96 call skdstdst() 000000003 ? 00000001C ?
  00000000F ? 00000002E ?
  000000008 ? 11298E020 ?
  FFFFFFFFFFF4DF0 ?
  2324084100000000 ?
ksedst()+52 call ksedst1() 000000028 ? 121A0F618 ?
  FFFFFFFFFFF71B0 ?
  FFFFFFFFFFF71E8 ? 112689070 ?
  000002004 ? 000000000 ?
  000000001 ?
dbkedDefDump()+1112 call ksedst() FFFFFFFFFFF4E90 ? 000000030 ?
  B38F0000000001 ? 000000000 ?
  000003B68 ? 000000000 ?
  000000003 ? 000000000 ?
ksedmp()+256 call dbkedDefDump() 330333133 ?
  373A205454432070 ?
  726F746F636F6C20 ?
  696E7465726E616C ?
  206572726F72203A ?
  205B333132305D20 ?
  5B39345D205B5D20 ?
  5B5D205B5D205B5D ?
dbkdaKsdActDriver() call ksedmp() 300000000 ? 000000000 ?
+1000 000000000 ? 64A4442432054 ?
  68696E20436C6965 ?
  6E74000000000000 ?
  000000000 ? 000000000 ?
dbgdaExecuteAction( call dbkdaKsdActDriver() 121723628 ? 000000000 ?
)+376 000000000 ? 000000000 ?
  000000000 ? 000000000 ?
  000000000 ? 000000000 ?
dbgdaRunAction()+48 call dbgdaExecuteAction( 121723628 ? 11299CAC0 ?
4 ) 9000000000A5174 ?
  FFFFFFFFFFF6FF0 ? 11218D141 ?
  FFFFFFFFFFF9250 ?
  FFFFFFFFFFF6FF0 ? 000000060 ?
dbgdRunActions()+12 call dbgdaRunAction() 000000000 ? 000000000 ?
0 000000000 ? 000000000 ?
  000000000 ? 000000000 ?
  000000000 ? 000000000 ?
dbgdProcessEventAct call dbgdRunActions() 000000000 ? 000000000 ?
ions()+244 000000000 ? 000000000 ?
  000000000 ? 000000000 ?
  000000000 ? 000000000 ?
dbgdChkEventKgErr() call dbgdProcessEventAct 121723628 ? 1216EAD28 ?
+400 ions() 121A0F958 ? 120E63368 ?
  FFFFFFFFFFF8830 ? 1219D1020 ?
  FFFFFFFFFFF8850 ?
  86242080216E81F0 ?
dbkdChkEventRdbmsEr call dbgdChkEventKgErr() 000000000 ? FFFFFFFFFFF8A88 ?
r()+64 121723628 ? FFFFFFFFFFF88A0 ?
  FFFFFFFFFFF88D0 ? 1219D1020 ?
  1048176A4 ? 000000001 ?
ksfpec()+104 call dbkdChkEventRdbmsEr FFFFFFFFFFF8A88 ? 1216EAD28 ?
  r() 121830998 ? 000000C30 ?
  000000000 ? FFFFFFFFFFF8A88 ?
  121723628 ? FFFFFFFFFFF88D0 ?
dbgePostErrorKGE()+ call ksfpec() 1216EAD28 ? FFFFFFFFFFF89E2 ?
3328 000000000 ? 12169E748 ?
  000000000 ? 000000080 ?
  FFFFFFFFFFFB0C0 ? 1216E83B0 ?
dbkePostKGE_kgsf()+ call dbgePostErrorKGE() 112C9DCF8 ? 1216EAD28 ?
64 C30219D0048 ? 000000C41 ?
  FFFFFFFFFFF95F0 ?
  4224282400000000 ?
  10480DEFC ? 000000000 ?
kgeade()+408 call dbkePostKGE_kgsf() 000000000 ? 000000002 ?
  FFFFFFFFFFFA088 ? 001000000 ?
  FFFFFFFFFFF95E0 ? 07FFFFFF8 ?
  FFFFFFFFFFF95F0 ? 1216E81E8 ?
kgerelv()+188 call kgeade() 000000000 ? 1216EAD28 ?
  1216EAF30 ? 1216EAD28 ?
  FFFFFFFFFFF9750 ? 000000000 ?
  104811214 ? 1216EAD28 ?
kserecl0()+84 call kgerelv() FFFFFFFFFFFA040 ? 121667FA0 ?
  10A6623EC ? 000000512 ?
  000000034 ? 121667FA0 ?
  D7A00000D7A ? 100000001 ?
ksulbem()+476 call kserecl0() 700000003 ? 000000000 ?
  C3000000C30 ? 0000007FF ?
  000000001 ? 000000000 ?
  000000000 ? 000000000 ?
opitsk()+4376 call ksulbem() 1216E8098 ? 121956B00 ?
  200000002 ? 000000000 ?
  000000C30 ? 000000000 ?
  00000005E ? 000000000 ?
opiino()+2968 call opitsk() 120F04970 ? 000000000 ?
  FFFFFFFFFFFCA70 ?
  FFFFFFFFFFFCC60 ?
  FFFFFFFFFFFCA50 ?
  9001000A00915E8 ?
  FFFFFFFFFFFCA60 ?
  9001000A00915E8 ?
opiodr()+948 call opiino() 3C06E79B58 ?
  BADC0FFEE0DDF00D ?
  FFFFFFFFFFFEFB0 ? 121819358 ?
  BADC0FFEE0DDF00D ?
  BADC0FFEE0DDF00D ?
  FFFFFFFFFFFD6A0 ? 000000000 ?
opidrv()+1044 call opiodr() 3C2F313231 ? 4216A20B0 ?
  FFFFFFFFFFFEFB0 ? 0216A20B0 ?
  000000000 ? FFFFFFFFFFFEB80 ?
  000000000 ? 000000028 ?
sou2o()+240 call opidrv() 3C00000000 ? 400000000 ?
  FFFFFFFFFFFEFB0 ? 000000000 ?
  000000000 ? 000000000 ?
  000000000 ? 000000000 ?
opimai_real()+448 call sou2o() FFFFFFFFFFFF020 ?
  BADC0FFEE0DDF00D ?
  90000000009B290 ?
  BADC0FFEE0DDF00D ?
  1216A4AD8 ? 9001000A00915E8 ?
  A0000000A000000 ? 112444C3C ?
ssthrdmain()+452 call opimai_real() FFFFFFFFFFFF158 ?
  FFFFFFFFFFFF120 ?
  FFFFFFFFFFFF478 ?
  FFFFFFFFFFFF478 ? 000000000 ?
  FFFFFFFFFFFF280 ?
  FFFFFFFFFFFF0F0 ?
  9001000A00915E8 ?
main()+208 call ssthrdmain() 000000000 ? 200000002 ?
  FFFFFFFFFFFF578 ?
  8FFFFFFF0000000 ?
  8FFFFFFF0000090 ? 000000000 ?
  000000000 ? 000000000 ?
__start()+112 call main() 000000000 ? 000000000 ?
  000000000 ? 000000000 ?
  000000000 ? 000000000 ?
  000000000 ? 000000000 ?


--------------------- Binary Stack Dump ---------------------

Execution of the next grep to check the reason of the issue:

grep "reason=" <SID>_ora_22937606.trc
  ChildNode: ChildNumber=0 ID=49 reason=Auto Reoptimization Mismatch(1) size=3x4 kxscflg=32 kxscfl4=4194560 dnum_kksfcxe=8192
  ChildNode: ChildNumber=1 ID=40 reason=Bind mismatch(18) size=4x4 bind_position=29 original_oacflg=16 original_oacflg=16 new_oacflg=18
  ChildNode: ChildNumber=0 ID=40 reason=Bind mismatch(18) size=4x4 bind_position=29 original_oacflg=18 original_oacflg=18 new_oacflg=16
  ChildNode: ChildNumber=1 ID=40 reason=Bind mismatch(18) size=4x4 bind_position=29 original_oacflg=16 original_oacflg=16 new_oacflg=18
  ChildNode: ChildNumber=0 ID=40 reason=Bind mismatch(18) size=4x4 bind_position=29 original_oacflg=18 original_oacflg=18 new_oacflg=16 kkscs=7000100dc89f238 nxt=7000100db989ec8 flg=18 cld=0 hd=7000100dc89ea58 par=7000100dc89ed48 pdb=0
  ChildNode: ChildNumber=0 ID=49 reason=Auto Reoptimization Mismatch(1) size=3x4 kxscflg=32 kxscfl4=4194560 dnum_kksfcxe=8192 kkscs=7000100dc867940 nxt=7000100dc867d70 flg=1a cld=0 hd=7000100dc867160 par=7000100dc867450 pdb=0

The cause of the issue is a Bind mismatch.

 

 

Correct bind mismatch error in the application code. Application reverted back the application changes.

 

 

Do you want to learn Oracle Database for Beginners, then read the following articles.

Oracle Tutorial | Oracle Database Tutorials for Beginners ( Junior Oracle DBA )

 

About Mehmet Salih Deveci

I am Founder of SysDBASoft IT and IT Tutorial and Certified Expert about Oracle & SQL Server database, Goldengate, Exadata Machine, Oracle Database Appliance administrator with 10+years experience.I have OCA, OCP, OCE RAC Expert Certificates I have worked 100+ Banking, Insurance, Finance, Telco and etc. clients as a Consultant, Insource or Outsource.I have done 200+ Operations in this clients such as Exadata Installation & PoC & Migration & Upgrade, Oracle & SQL Server Database Upgrade, Oracle RAC Installation, SQL Server AlwaysOn Installation, Database Migration, Disaster Recovery, Backup Restore, Performance Tuning, Periodic Healthchecks.I have done 2000+ Table replication with Goldengate or SQL Server Replication tool for DWH Databases in many clients.If you need Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS Consultancy and Training you can send my email adress [email protected].-                                                                                                                                                                                                                                                 -Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS ve linux Danışmanlık ve Eğitim için  [email protected] a mail atabilirsiniz.

Leave a Reply

Your email address will not be published. Required fields are marked *