Specifying Time Limit For Cache Warming (Doc ID 1958776.1)

Last updated on FEBRUARY 09, 2016

Applies to:

Oracle Endeca Server - Version 7.6.0 to 7.6.0 [Release 7.x]
Information in this document applies to any platform.
Any time data is updated, the cache will become stale needing to be refreshed. In earlier releases, you would have to render applications one by one in order for the cache to get back up to date. In this release, you can warm the cache and also set a time for it to process expensive queries.

Goal

If when warming the cache it is sees an expensive query, the default time in seconds for cache warming is small so that when it encounters the query, it basically ignores it because the time limit is too short.  So, because it is not executed, it is getting warmed when the Studio pages are opened.  Hence, by specifying a higher time limit, that enables the server to execute the queries without having the user open the Studio pages to warm the cache.

Solution

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