Read-Only Queries Load Transactional Data Into The Shared Cache Even After Applying Patch 14189743

(Doc ID 1514615.1)

Last updated on FEBRUARY 05, 2013

Applies to:

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

Symptoms

Read-Only queries executed within a transaction with changes could load those changes into the shared cache.

Testing the standalone application works fine. However, when deploying the application to WebLogic, it fails. The flushed but uncommitted object is still put in the cache,
and the read_only query will read uncommitted objects which is in contrary to the behavior in standalone test.

Scenario:

The issue occurs even after applying <patch 14189743> as per:

<Document 1513181.1> READ_ONLY query hint causes uncommitted data to be loaded into shared cache.

Cause

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