Monitoring DML to get an idea of the activity on our tables is not new. The number of insert/delete/update/truncate since last stats gathering is tracked automatically. The statistics gathering job use it to list and prioritize tables that need fresh statistics. This is for slow changes on tables. In 12.2 we have the statistics advisor that goes further, with a rule that detects volatile tables:
SQL> select * from V$STATS_ADVISOR_RULES where rule_id=14;
RULE_ID NAME RULE_TYPE DESCRIPTION CON_ID
------- ---- --------- ----------- ------
14 LockVolatileTable OBJECT Statistics for objects with volatile data should be locked 0
But to detect volatile tables, you need to track DML frequency with finer grain. Let’s investigate what is new here in 12.2
Recent comments
12 weeks 6 days ago
25 weeks 5 hours ago
29 weeks 2 days ago
30 weeks 19 hours ago
34 weeks 5 days ago
1 year 3 weeks ago
1 year 24 weeks ago
2 years 1 week ago
2 years 38 weeks ago
2 years 38 weeks ago