INSERT into a LOB Column of a Partitioned Table Fails with ORA-22922 with Fixes 8819768 and 13877007 Applied
(Doc ID 1552147.1)
Last updated on MARCH 06, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.3 to 126.96.36.199 [Release 10.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
An INSERT into a LOB column of a partitioned table fails with the following error if a concurrent DDL (TRUNCATE for example) on another partition is in progress at the same time:
The fixes for:
<Bug 8819768> - ORA-1652 DUE TO COPY OF LOB IN TRIGGER WITH JAVA/JDBC CLIENT
<Bug 13877007> - ORA-600 [KOKEGPINLOB1] DURING INSERT OPERATION
<Patch 13877007> fixes an ORA-600[kokegPinLob1] error during an INSERT which was introduced by the changes made to fix <Bug 8819768>. However, this error:
ORA-22922: Nonexistant LOB value
can now occur.
<Bug 8819768> - Temp tablespace space leak / ORA-1652 from DML on LOB with a trigger - superseded (<Note 8819768.8>)
<Bug 13877007> - ORA-600 [kokegPinLob1] during INSERT to partitioned table with LOB data (<Note 13877007.8>)
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