ePM fails to insert records into message tracking tables when the internal ROLLBACK SEGMENT size is small. (Doc ID 1028433.1)

Last updated on JUNE 24, 2004

Applies to:

Sun B2B - Version: 4.5.3 and later
Oracle Solaris SPARC (32-bit)

Symptoms

ePM fails to insert records into message tracking tables when the internal ROLLBACK SEGMENT size is small. As a result all the incoming transactions are not accounted for in web interface and 997s generation/consolidation process is not initiated.

1) Message tracking web interface doesn't get updated
2) No records get inserted into the database and the following errors will be seen in ePM log:

08:24:15.063 MNK I 1 (monklog:406): In eX_X12_Inb_I_generic
08:24:15.198 MNK I 1 (monklog:406): ux-store-msg-ext failed
08:24:15.212 MNK I 1 (monklog:406): UX_I_fragment_store_msg: invalid sql_stmt
08:24:15.213 MNK I 1 (monklog:406): ORACLE|ORA-01461|can bind a LONG value only for insert into a LONG column

08:24:15.869 MNK I 1 (monklog:406): In eX_X12_Inb_I_generic
08:24:15.878 MNK I 1 (monklog:406): ux-store-msg-ext failed
08:24:15.879 MNK I 1 (monklog:406): UX_I_fragment_store_msg: invalid sql_stmt
08:24:15.879 MNK I 1 (monklog:406): ORACLE|ORA-01465|invalid hex number

Cause

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