Manually Editing Additional Global Cache Parameters

7-18 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

7.6.2.2 About Sharing the Presentation Services Query Cache

When users access Answers to run queries, Presentation Services caches the results of the queries. Presentation Services uses the request key and the logical SQL string to determine if subsequent queries can use cached results. If the cache can be shared, then subsequent queries are not stored. ■ SAGetSharedRequestKey: An ODBC procedure that takes a logical SQL statement from Presentation Services and returns a request key value. The following shows the syntax of this procedure: SAGetSharedRequestKeysql-string-literal The value of the request key is affected by the following factors: ■ Whether the Virtual Private Database option has been selected in the repository physical database object ■ Whether any session variables have been marked as Security Sensitive in the repository Presentation Services takes security sensitive variable values into consideration when computing the request key for logical requests against database objects marked as Virtual Private Databases. See Section 7.9, Managing the Oracle BI Presentation Services Cache Settings for more information about the Presentation Services query cache.

7.6.2.3 About Result Records

A result record is returned after you issue a purge cache command. The result record contains two columns. The first column is a result code and the second column is a short message that describes the result of the purge operation. Table 7–1 shows examples of result records.

7.6.2.4 Storing and Purging Cache for SAPBW Data Sources

In Microsoft Analysis Services, member caption name is the same as member unique name. However, in SAPBW data sources, member caption name is different from member unique name. Therefore, the Oracle BI Server maintains a cache subsystem for SAPBW member unique names. This subsystem is turned off by default. For configuration information, see the topic about the MDX Member Name Cache Section in Appendix A, NQSConfig.INI File Configuration Settings. When a query is received for member unique name, the subsystem checks the cache to determine whether cache exists for this query. If cache exists, then the record for the cached unique name is returned. If there is no cache that matches the query, then the subsystem sends a probing query to SAPBW. Table 7–1 Query Result Codes Result Code Result Message 1 SAPurgeCacheByDatabase returns successfully. 59115 Operation not performed because caching is not enabled. 59116 The database specified does not exist. 59117 The table specified does not exist.