PM40051: "CANNOT INSERT NULL INTO" PRIMARY KEY FIELD WHEN ADDING 2 JPA ENTITIES.

Fixes are available

APAR status

Closed as program error.

Error description

The following exception occurs when inserting multiple
entities where the entites contain sequence generated id and
contain relationships with other entities:

Caused by: <openjpa-1.1.0-r422266:657916 nonfatal general
error> org.apache.openjpa.persistence.PersistenceException:
ORA-01400: cannot insert NULL into
("MYSCHEMA"."MYENTITY"."MYENTITY_ID")
FailedObject: prepstmnt 674113582 INSERT INTO
MYSCHEMA.MYENTITY (MYENTITY_ID, MYENTITY_TEXT,
ANOTHER_ENTITY_ID)
VALUES (?, ?, ?)
[org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedS
tatement]
at
org.apache.openjpa.jdbc.sql.SQLExceptions.narrow(SQLExceptions.j
ava:144)
at
org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDic
tionary.java:4150)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions
.java:102)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions
.java:72)
at
org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerI
mpl.flushBatch(BatchingPreparedStatementManagerImpl.java:183)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0.0 and V8.0.0 who use sequence   *
*                  generated ids and bi-directional            *
*                  relationships in their Java Persistence     *
*                  API (JPA) entities.                         *
****************************************************************
* PROBLEM DESCRIPTION: Sequence generated ids may fail to      *
*                      get assigned when flushing a graph      *
*                      with bi-directional relationships.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Flushing a multi-level graph with many bi-directional
relationships can result in SQL exceptions due to
sequence-generated IDs of some leaf entities not getting
assigned during pre-flush. Sequence-generated id's require an
additional ID population step which happens during pre-flush.
OpenJPA's state transitioning during a pre-flush can fail to
pre-flush child entities when certain bi-directional
traversals occur.

Problem conclusion

With this fix, code has been added such that when flushing,
a pre-flush will occur on entities that may have moved from
provisional to new state (as a result of a previous traversal)
without being properly pre-flushed. If the entity was
previously pre-flushed, it will have been tagged as such and
the operation will simply return. Otherwise, it will pre-flush
the entity and all child entities, generating IDs in the
process.

The fix for this APAR is currently targeted for
inclusion in Service Levels (Fix Packs) 7.0.0.21 and 8.0.0.2
of WebSphere Application Server versions 7.0.0 and 8.0.0.

Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM40051
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-25
Closed date
2011-08-25
Last modified date
2011-09-02

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM42704

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM40051: "CANNOT INSERT NULL INTO" PRIMARY KEY FIELD WHEN ADDING 2 JPA ENTITIES.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?