Non Null BLOB is not Inserted Through Triggers When Using Java Persistence API (Doc ID 1927700.1)

Last updated on AUGUST 16, 2016

Applies to:

Oracle TopLink - Version 11.1.1.0.1 and later
Information in this document applies to any platform.

Symptoms

A table (TBL_BPM_SERVICES_MASTER ) is created in Oracle Database that  contains a BLOB  type column (service_data).

A trigger is defined on this table (TBL_BPM_SERVICES_MASTER ) so
 that for any insert / update on a row , a copy of the inserted / updated row
 is done to another similar table (TABLE TBL_BPM_SERVICES_MASTER_AU) with
 a blob column (service_data).
 
  An entity is mapping the table TBL_BPM_SERVICES_MASTER :

 
The problem occurs when persisting ServicesMaster entity with a non null BLOB  :
the corresponding row is well inserted into TBL_BPM_SERVICES_MASTER table
with a non null blob column (service_data).

But the row inserted into the TBL_BPM_SERVICES_MASTER_AU table thanks to the trigger
has the corresponding  blob column (service_data) empty.

The expected behaviour is that TBL_BPM_SERVICES_MASTER_AU contais a row with a non null blob
value as in TBL_BPM_SERVICES_MASTER.

The used  Eclipselink version  is 1.0.2 .

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