M-1 Relationships Randomly Becomes Null With Concurrent Updates
(Doc ID 1572249.1)
Last updated on FEBRUARY 01, 2022
Applies to:Oracle TopLink - Version 188.8.131.52.0 to 184.108.40.206 [Release Oracle11g to 12c]
Information in this document applies to any platform.
You encounter an issue when you have multiple threads accessing M-1 relationships of some entities while they are doing update on some other entities, the M-1 relationships will randomly become null even though the data in database and cache is correct.
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