Ensuring Correct Cache Results When Using Row-Level Database Security

7-26 System Administrators Guide for Oracle Business Intelligence Enterprise Edition Expand the repository tree to display all the business models with cache entries, and expand the business models to display all users with cache entries. The right pane displays only the cache entries associated with the selected item in the hierarchical tree.

7.7.4.1 Displaying Global Cache Information in the Cache Manager

Select Action, then select Show Info to display global cache information. Table 7–5 describes the information that appears in the Global Cache Information window. Table 7–4 Cache Options Option Description User The ID of the user who submitted the query that resulted in the cache entry. Created The time the cache entrys result set was created. Last used The last time the cache entrys result set satisfied a query. After an unexpected shutdown of the Oracle BI Server, the last used time might temporarily have a stale value—a value that is older than the true value. Creation elapsed time The time, in seconds, that is needed to create the result set for this cache entry. Note: The value that is stored in the cache object descriptor on disk is in units of milliseconds. The value is converted to seconds for display purposes. Row count The number of rows generated by the query. Row size The size of each row in bytes in this cache entrys result set. Full size Full size is the maximum size used, considering variable length columns, compression algorithm, and other factors. The actual size of the result set is smaller than Full size. Column count The number of columns in each row of this cache entrys result set. Logical Request The logical request that is associated with this cache entry. If subrequests are being cached, then this column shows the text of the subrequest. Use count The number of times that this cache entrys result set has satisfied a query since Oracle BI Server startup. Business model The name of the business model that is associated with the cache entry. Repository The name of the Oracle Business Intelligence repository that is associated with this cache entry. SQL The SQL statement that is associated with this cache entry. If subrequests are being cached, then there might be multiple cache entries that are associated with a single SQL statement. Query Server The Oracle BI Server that serviced the query. Fact Table Source The fact table that is associated with the logical request for this cache entry. Managing Performance Tuning and Query Caching 7-27 With the Cache Manager as the active window, press F5, or select Action, then Refresh to refresh the display. This retrieves the current cache entries for the repository that you have open and the current global cache information. If the DSN is clustered, then information about all repositories in the cluster is displayed.

7.7.4.2 Purging Cache in the Administration Tool

Purging cache is the process of deleting entries from the query cache. You can purge cache entries in the following ways: ■ Manually, using the Administration Tool Cache Manager facility in online mode. ■ Automatically, by setting the Cache Persistence Time field in the Physical Table dialog for a particular table. ■ Automatically, by setting up an Oracle BI Server event polling table. ■ Automatically, as the cache storage space fills up. To manually purge cache entries in the Cache Manager: 1. Use the Administration Tool to open a repository in online mode.

2. Select Manage, then Cache to open the Cache Manager dialog.

3. Select Cache or Physical mode by selecting the appropriate tab in the left pane.

Table 7–5 Global Cache Information Column Description Amount of space still available for cache storage use The amount of space, in megabytes, still available for cache storage. Amount of space used on disks containing cache related files The total amount of space, in megabytes, used on the disk that contains cache-related files not just space used for the cache-related files. Maximum allowable number of entries in cache The maximum number of entries that can be in the cache, from the MAX_CACHE_ENTRIES parameter in the NQSConfig.INI file. Maximum allowable number of rows per cache entry result set The maximum number of rows that are allowed for each cache entrys result set, from the MAX_ROWS_PER_CACHE_ENTRY parameter in the NQSConfig.INI file. Number of entries currently in cache The current number of entries in the global cache. These entries might relate to multiple repositories. Number of queries not satisfied from cache since startup of Oracle BI Server Cache misses, since the last time the Oracle BI Server was started. Number of queries satisfied from cache since startup of Oracle BI Server Cache hits, since the last time the Oracle BI Server was started. Note: You can also purge the cache programmatically using ODBC-extension functions. See Section 7.6.2, Purging and Maintaining Cache Using ODBC Procedures for more information. In addition, cache can be purged when the value of dynamic repository variables changes. See Section 7.6.3.4, Changes to Dynamic Repository Variables for more information.