# OBIS - Purging / Disabling the Query Cache

## 1 - About

How to purge the Query Cache

For the Presentation Server cache, see OBIPS - (Query|Result|Cursor) Cache

Advertising

## 3 - Disabling

### 3.1 - For the entire application

To disable completly the query cache, you must set to the ENABLE cache parameter the value NO in the file nqsconfig.

[CACHE]

ENABLE = NO;

### 3.2 - For one session

For one session, you have to set the session system variable with the value 1:

• DISABLE_CACHE_HIT
• DISABLE_CACHE_SEED

### 3.3 - For one request / answer

For one session, you have to set this request variables with the value 1:

• DISABLE_CACHE_HIT
• DISABLE_CACHE_SEED

Example in the advanced tab of an answer :

SET VARIABLE DISABLE_CACHE_HIT=1;
Advertising

## 4 - Purging

### 4.1 - Via ODBC functions

Note : Replace OracleBI_Home by your own directory.

Create a file PurgeAllCache.sql and add the SAPurgeAllCache ODBC Function :

{call SAPurgeAllCache()};

And save it in a directory (for instance OracleBI_Home\Cache).

Then from a command dos, call nqcmd with this statement :

OracleBI_Home\server\Bin\nqcmd.exe -d AnalyticsWeb -u Administrator -p Password
-s "OracleBI_Home\Cache\PurgeAllCache.sql" -o "OracleBI_Home\Cache\PurgeAllCache.log"

You will retrieve then in the PurgeAllCache.log :

{call SAPurgeAllCache()}
----------------------------------------------------------------
RESULT_CODE  RESULT_MESSAGE
----------------------------------------------------------------
1            [59118] Operation SAPurgeAllCache succeeded!
----------------------------------------------------------------
Row count: 1
----------------------------------------------------------------
Processed: 1 queries

You can also use the ODBC Bi Server cache Function in a script that can call the job manager.

When failed:

call SAPurgeAllCache()
----------------------------------------------------------------
RESULT_CODE  RESULT_MESSAGE
----------------------------------------------------------------
59115        [59115] Operation not performed because caching is not enabled.
----------------------------------------------------------------
Row count: 1
----------------------------------------------------------------

### 4.2 - With Dynamic Repository Variables

In the Server Administration Guide, section “Understanding and Creating Repository Variables”, you can read that :

When the value of a dynamic repository variable changes, all cache entries associated with a business model that
reference the value of that variable will be purged automatically.

This means that the query cache will be purged when the variable is refreshed. By creating a Dynamic Repository Variable that selects a specific value from a table you can easily easily trigger a cache purge.

For instance, from an ETL process :

• create a date column to contain the last update date from your datawarehouse
• then create a dynamic variable to refresh this value (every 10 minutes).
• then when the value change, the cache is automatically purged
Advertising

### 4.4 - Via the event pooling table

The use of an Oracle BI Server event polling table (event table) is a way to notify the Oracle BI Server that one or more physical tables have been updated. The Oracle BI Server cache system reads rows from, or polls, the event table, extracts the physical table information from the rows, and purges stale cache entries that reference those physical tables.

### 4.5 - by setting the Cache Persistence Time

You can purge the cache automatically for a particular table, by setting the Cache Persistence Time field in the Physical Table.

## 5 - Documentation / Reference

dat/obiee/obis/query_processing/query_cache_purging.txt · Last modified: 2018/09/18 11:26 by gerardnico