Wednesday, June 11, 2008


While doing upgrade from 11.5.9 to we encounter one issue. i.e. Whenever we add or modifying responsibility end date, it is not showing in responsibility LOV or at Framework Homepage. We have to bounce apache to resolve this issue. That shows we are having issue with Cache. It takes a while to resolve this issue but following notes worth reading it from metalink i.e 455194.1, which explain "Diagnosing database invalidation issues with Java Cache for eBusiness Suite" Following are the main points on which this note works :

In order to identify any issues, there are several steps to go through:-
1) Gather background information about the environment
Oracle Support need to have a good idea about your environment architecture in order to understand the problem fully.
2) Check latest Java Cache patches have been applied
Release 11i ATG RUP3 patchset was the first release where Java Caching became more noticeably used throughout eBiz. Since then there have been some issues fixed in various patches. It is strongly recommended to apply these patches to resolve the known issues
3) Confirm all eBiz nodes have been configured correctly
It is sometimes possible to misconstrue the required setup, particularly in complex architectures such as through firewalls. It is important to confirm the current setup to ensure all configuration is correct
4) Identify nature and scope of the issue
It may be that Java Caching and Database invalidation itself is functioning correctly, but just one or two specific components are not working. Each different type of data is stored in its own "Component Cache" within the Java Cache and has its own code to control it. For example, profile option changes may be working, but responsibility changes are not. It is important to understand which parts work (if any)
5) Gather additional data to help identify the failure point
Once all the basic checks have been done, the next level of investigation is to to enable detailed logging information. This level of detail does require patient and thorough review to be able to identify the failure point.

Unfortunately due to the complex nature of Java Caching, this may take several iterations of testing and data gathering before any firm conclusions can be reached.

Happy Troubleshooting !!!

1 comment:

Vikram Das said...

Hi Sundeep,

Metalink Note 417439.1 describes a similar issue. You can try that also.

- Vikram