Diagnosing database invalidation issues with Java Cache for eBusiness Suite
(Doc ID 455194.1)
Last updated on AUGUST 07, 2024
Applies to:
Oracle Applications Framework - Version 11.5.10.0 to 11.5.10.2.6 [Release 11.5.10]Information in this document applies to any platform.
This note has been written using eBusiness Release 11.5.10 RUP5 and Release 12.0.3, however should apply to any eBiz 11i version with ATG RUP3 or above applied as well as all Release 12 versions
Purpose
Java Caching is a mechanism used to improve performance by storing data in the Middle Tier JVM memory, instead of retrieving the data from the database every time it is requested.
One common issue reported to Oracle Support is that changes made to users responsibilities are not immediately propagated to the OA Framework home page. For example, a new responsibility added to a user may take 30-60 minutes to appear on the users home page (but is available immediately if they access the responsibility list from Core Forms) This behavior is indicative of a Database Invalidation issue with the Java Caching mechanism.
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| References |