Dba_tab_modifications not reflecting the DML modified timestamp
(Doc ID 2935910.1)
Last updated on APRIL 10, 2023
Applies to:
Autonomous Database on Shared Infrastructure - Version N/A to N/AInformation in this document applies to any platform.
Goal
Timestamp keeps changing and it reflects the current timestamp, even while there is NO DML Activity towards a table. It results in invalid cache for SQLs based on the table.
SQL> select systimestamp, a.* from dba_tab_modifications a where table_name = 'TESTTAB';
SYSTIMESTAMP TABLE_OWNER TABLE_NAME PARTITION_NAME SUBPARTITION_NAME INSERTS UPDATES DELETES TIMESTAMP TRUNCATED DROP_SEGMENTS
------------------------- ----------- -------------- -------------- ----------------- ------- ------- ------- ------------------- --------- -------------
2023-03-14 14:12:39.801 TEST TESTTAB 0 0 0 2023-03-14 14:12:39 NO 0
SQL> select systimestamp, a.* from dba_tab_modifications a where table_name = 'TESTTAB';
SYSTIMESTAMP TABLE_OWNER TABLE_NAME PARTITION_NAME SUBPARTITION_NAME INSERTS UPDATES DELETES TIMESTAMP TRUNCATED DROP_SEGMENTS
------------------------- ----------- -------------- -------------- ----------------- ------- ------- ------- ------------------- --------- -------------
2023-03-14 14:12:49.062 TEST TESTTAB 0 0 0 2023-03-14 14:12:49 NO 0
Solution
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
| Goal |
| Solution |