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 MAY 15, 2017

Applies to:

Business Intelligence Suite Enterprise Edition - Version 11.1.1.7.0 to 11.1.1.7.170418 [Release 11g]
Information in this document applies to any platform.

Symptoms

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:

CREATE TABLE S_NQ_EPT
(
UPDATE_TYPE DECIMAL(10,0) DEFAULT 1 NOT NULL,
UPDATE_TS                          DATE DEFAULT SYSDATE NOT NULL,
DATABASE_NAME                   VARCHAR2(120) NULL,
CATALOG_NAME                     VARCHAR2(120) NULL,
SCHEMA_NAME                       VARCHAR2(120) NULL,
TABLE_NAME                          VARCHAR2(120) NOT NULL,
OTHER_RESERVED                  VARCHAR2(120) DEFAULT NULL NULL
) ;

UPDATE_TS column is defined DATE and default SYSDATE.  This turns out that UPDATE_TS column with 1 second precision.

Often, there can be multiple inserts done to the polling table for cache purge marking at a sub-second level.

Example:

    

INSERT INTO S_NQ_EPT(update_type,update_ts,database_name,catalog_name,schema_name,table_name,other_reserved)
VALUES(default,default,'CA',NULL,'SH','TEST_A',null);
COMMIT;

INSERT INTO S_NQ_EPT(update_type,update_ts,database_name,catalog_name,schema_name,table_name,other_reserved)
VALUES(default,default,'CA',NULL,'SH','TEST_B',null);
COMMIT;  

 

it could lead to dead records in the event polling table.

Like:

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.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms