Second Before Trigger Does Not See Value Of CLOB Modified In First Before Trigger
(Doc ID 1322350.1)
Last updated on FEBRUARY 23, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.3 to 11.1.0.7 [Release 10.1 to 11.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
If there are 2 before triggers, the second trigger wipes out any lob outbind set by the first trigger.
After trigger 1 modifies the value of a lob column, this lob is passed into trigger 2.
On exit from trigger 2 the original value for the lob column is then passed into the insert (or update), not the value modified by trigger 1.
Example
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 |