Caching is turned off by default for the Transactional Business Intelligence content to ensure the Transactional Business Intelligence reports always return real-time data. If not absolutely necessary, then you can enable caching to obtain better query performance. You have the following options to enable caching and set a cache timeout in Transactional Business Intelligence:
Use the Cache Manager to manually manage the cache entries after you enable caching for Transactional Business Intelligence view objects. Enable view object level caching by using the Oracle BI Administration tool and editing the master Oracle BI repository as follows:
Edit the view object properties and check the Cacheable check box.
Note: | if the source view object property has already been changed, do not edit the properties for aliases . It is reflected in the alias automatically. |
Set the Cache Persistence Time property to determine how frequently the cache should expire.
You can also use the following two options for automating the cache management process:
Use the Oracle BI Administration Tool to set the Cacheable and Cache Persistence Time properties for any view object that you want cached.
Use the Configure Oracle BI Server Event Polling Tables to purge the cache. Doing so requires a trigger that you would have to implement to populate this table when there are changes to the application's transaction tables, ensuring that you always avoid hitting a stale cache.
See Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.