Accepted Solutions (0)
Answers (5)
Hi Paul,
hmm i just setup a tiny test case here on 11.2.0.3.6.
SQL> create table TABA (id NUMBER NOT NULL, text VARCHAR2(10))
PARTITION BY RANGE (id)
(PARTITION part1 VALUES LESS THAN (11),
PARTITION part2 VALUES LESS THAN (21) ,
PARTITION part3 VALUES LESS THAN (31));
SQL> begin
for i in 1..30 loop
insert into TABA values(i,'XXXXX');
end loop;
commit;
end;
/
SQL> exec DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO();
SQL> select TABLE_NAME, PARTITION_NAME, INSERTS, UPDATES, DELETES, TIMESTAMP
from DBA_TAB_MODIFICATIONS
where TABLE_NAME like '%TABA';
SQL> exec DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => USER, TABNAME => 'TABA', PARTNAME => 'PART1',
ESTIMATE_PERCENT => .2, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL,
GRANULARITY => 'PARTITION', CASCADE => TRUE, NO_INVALIDATE => FALSE);
SQL> select TABLE_NAME, PARTITION_NAME, INSERTS, UPDATES, DELETES, TIMESTAMP
from DBA_TAB_MODIFICATIONS
where TABLE_NAME like '%TABA';
So it works as expected in my case, but i don't know your exact partitioning as it is custom made. However i would crosscheck the underlying table SYS.MON_MODS_ALL$ and its populated values. If it is wrong there as well - i would open an Oracle SR.
MOS note #1390718.1 describes a very specific case and can be verified easily
Regards
Stefan
| User | Count |
|---|---|
| 95 | |
| 11 | |
| 10 | |
| 9 | |
| 9 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.