Read-Only Queries Load Transactional Data Into The Shared Cache Even After Applying Patch 14189743
(Doc ID 1514615.1)
Last updated on MARCH 01, 2021
Applies to:
Oracle TopLink - Version 11.1.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
Disclaimer
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
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.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |