A single cache entry can be associated to multiple dependency IDs, and a dependency ID can be associated to multiple cache entries. A single request could rely on full page cache, fragment cache and data cache.Invalidation of lower level caches such as price, wont be reflected in the store if they are included in a higher level cache such as a JSP fragment or a full page.The restart entry has the following format: Next I list a number of actions and concepts that will help you see why stale pages remain in the store after invalidating. The following points assume a problem with the caches within the Commerce servers.Before using these steps, ensure that the stale content is not being returned from browser cache or an edge cache service such as Akamai.The procedure invalidates the dependent cursors immediately if set to FALSE.
See these documents: For non-WXS caches, ensure the DRS replication domain is configured.
Once you identify the piece of data that is not being refreshed, use the file and the Cache Monitor to understand the different cache entries that include that data, and ensure there are corresponding invalidation IDs for those cache entries as well.
Does not invalidate the dependent cursors if set to TRUE. to have Oracle decide when to invalidate dependent cursors. The default can be changed using the SET_DATABASE_PREFS Procedure, SET_GLOBAL_PREFS Procedure, SET_SCHEMA_PREFS Procedure and SET_TABLE_PREFS Procedure.
The process in the Search servers is a bit different.
There is no scheduler and therefore no Dyna Cache Invalidation job.