OBIEE11g: When UPDATE_TS Column has No Uniqueness, Dead Records May Be Left in the Event Polling Table
(Doc ID 2259323.1)
Last updated on MARCH 11, 2019
Applies to:Business Intelligence Suite Enterprise Edition - Version 188.8.131.52.0 to 184.108.40.206.170418 [Release 11g]
Information in this document applies to any platform.
Using event pooling tables to invalidate stale cache entries.
The DDL of BIPLATFORM schema for event polling table is S_NQ_EPT; and defined as following:
it could lead to dead records in the event polling table.
UPDATE_TYPE UPDATE_TS DATABASE_NAME CATALOG_NAME SCHEMA_NAME TABLE_NAME OTHER_RESERVED
1 2017-04-20 14:18:18 CA SH TEST_A instance1:coreapplication_obis1
1 2017-04-20 14:18:18 CA SH TEST_B instance1:coreapplication_obis1
1 2017-04-20 14:18:18 CA SH TEST_A
1 2017-04-20 14:18:18 CA SH TEST_B
Note: table_name is a different value in this case. When table_name has the same value, the records can be successfully cleared.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document