Select the cache entries to purge, and then select Edit, then Purge to remove them.

Managing Performance Tuning and Query Caching 7-31 example, during a load operation. When there are rows in the event table, there is changed data in the underlying databases. The server then invalidates any cache entries that correspond to the changed physical tables and periodically deletes obsolete rows from the event table. The next time it checks the event table, the process repeats. To enable the Oracle BI Server to have write access to the event polling table but not to any other tables in a database, perform the following tasks: ■ Create a separate physical database in the Physical layer of the Administration Tool with a privileged connection pool. ■ Assign a user to the connection pool that has delete privileges. ■ Populate the privileged database with the event table. The Oracle BI Server has write access to the event polling table, but not to any tables that are used to answer user queries.

7.8.1.2 Sample Event Polling Table CREATE TABLE Statements

This section provides sample CREATE TABLE statements for SQL Server and Oracle Database. These CREATE TABLE statements create the structure that is required for an Oracle BI Server event polling table. In these statements, the table that is created is named UET. It resides in the same database as the physical tables that are being updated. The following is a sample CREATE TABLE statement for SQL Server: SQL Server Syntax create table UET UpdateType Integer not null, UpdateTime datetime not null DEFAULT CURRENT_TIMESTAMP, DBName char40 null, CatalogName varchar40 null, SchemaName varchar40 null, TableName varchar40 not null, Other varchar80 null DEFAULT NULL The following is a sample CREATE TABLE statement for Oracle Database: Oracle Database syntax create table UET UpdateType Integer not null, UpdateTime date DEFAULT SYSDATE not null, DBName char40 null, CatalogName varchar40 null, SchemaName varchar40 null, TableName varchar40 not null, Note: In a clustered Oracle Business Intelligence deployment, a single event polling table is shared by every Oracle BI Server node in the cluster. However, a single event polling table cannot be shared by multiple Oracle BI Server clusters. Note: The column lengths must be large enough to represent the object names in the repository.