My Oracle Support Banner

ORA-600 [12333] DURING INSERT VIA BPEL PM DATABASE ADAPTER (Doc ID 356359.1)

Last updated on APRIL 16, 2021

Applies to:

Oracle(R) BPEL Process Manager 10g - Version 10.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

In a BPEL 10.1.2 patch 2 installation that uses Oracle 9i as dehydration store, once the pay load gets to certain size, the BPEL engine fails to insert audit trails and an error as follows is shown on the domain log:

<2006-01-16 17:26:52,771> <ERROR> <default.collaxa.cube>
<BaseCubeSessionBean::logError> Error while invoking bean "cube delivery":
Cannot insert invoke message. The process domain was unable to insert the
invocation data for message "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-7ff8",
operation "initiate" in the datastore. The exception reported is: No more data
to read from socket Please check that the machine hosting the datasource is
physically connected to the network. Otherwise, check that the datasource
connection parameters (user/password) is currently valid. sql statement: INSERT
INTO invoke_message_bin( message_guid, domain_ref, bin_csize, bin_usize, bin )
VALUES ( ?, ?, ?, ?, ? ) <2006-01-16 17:26:52,959> <ERROR> <
default.collaxa.cube> <BaseCubeSessionBean::logError>


At the same time, it is generated an internal error in the Alert Log file:

     ORA-00600: internal error code, arguments: [12333], [6], [197], [20], [], [], [] , []

The failing statement is:

  INSERT INTO invoke_message_bin( message_guid, domain_ref, bin_csize, bin_usize, bin ) VALUES ( :1, :2, :3, :4, :5 )

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.