Coherence Write-behind Causing Oracle Sessions To Block On Insert, How to Avoid?

(Doc ID 2323576.1)

Last updated on JANUARY 19, 2018

Applies to:

Oracle Coherence - Version and later
Information in this document applies to any platform.


During a rolling restart of the Coherence Cluster customer sees instances where several storage enabled jvms’ write-behind threads attempt to write the same data to Oracle DB, causing lock contention and block the application from writing to Oracle DB. This eventually leads to application failure. User can identify this by multiple instances attempting to insert the same data (sql_id). Application requests supposed to be happening the updates with no contention. 


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