M-1 Relationships Randomly Becomes Null With Concurrent Updates

(Doc ID 1572249.1)

Last updated on SEPTEMBER 21, 2017

Applies to:

Oracle TopLink - Version to [Release Oracle11g to 12c]
Information in this document applies to any platform.
**Checked for Currency31-JUL-2013**


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.


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