An event polling table is a way to notify the Oracle BI Server that one or more physical tables have been updated. Each row that is added to an event table describes a single update event. The cache system reads rows from, or polls, the event table, extracts the physical table information from the rows, and purges cache entries that reference those physical tables.
Generaly we will purge the cache in two ways
Manage – Cache
From dashboard also we can purge the cache
Settings – Issue SQL — Call Sapurgeallcache()
Instead doing like this on regular interval with the help of Event table we can purge the cache.
Procedure :
Create table S_NQ_EPT
(
UPDATE_TYPE INTEGER DEFAULT 1 NOT NULL,
UPDATE_TIME DATE DEFAULT SYSDATE NOT NULL,
DB_NAME VARCHAR2(40),
CATALOG_NAME VARCHAR2(40),
SCHEMA_NAME VARCHAR2(40),
TABLE_NAME VARCHAR2(40) NOT NULL,
OTHER VARCHAR2(80) DEFAULT NULL
)
Once the table is created we have to import the table into Physical layer.
Goto Tools — Utilities
Generaly we will purge the cache in two ways
Manage – Cache
From dashboard also we can purge the cache
Settings – Issue SQL — Call Sapurgeallcache()
Instead doing like this on regular interval with the help of Event table we can purge the cache.
Procedure :
Create table S_NQ_EPT
(
UPDATE_TYPE INTEGER DEFAULT 1 NOT NULL,
UPDATE_TIME DATE DEFAULT SYSDATE NOT NULL,
DB_NAME VARCHAR2(40),
CATALOG_NAME VARCHAR2(40),
SCHEMA_NAME VARCHAR2(40),
TABLE_NAME VARCHAR2(40) NOT NULL,
OTHER VARCHAR2(80) DEFAULT NULL
)
Once the table is created we have to import the table into Physical layer.
Goto Tools — Utilities
Will find the list of tables.Select the S_NQ_EPT as a Event table and also set the Polling frequency Time.
Once this is done we need to insert data into the S_NQ_EPT table
After the Polling frequency time we mentioned just check the Cache folder it will be Purged
No comments:
Post a Comment