Statistics on New, Local Index Partition Not Gathered with DBMS_STATS.GATHER_SCHEMA_STATS, Option GATHER STALE
(Doc ID 2155566.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- Using DBMS_STATS.GATHER_SCHEMA_STATS, option GATHER STALE, statistics are not collected on a locally partitioned index
- The GATHER EMPTY option will gather STATS (as displayed in USER_TAB_PARTITIONS), but GATHER STALE does not, even though rows are INSERT(ed) into the partition
- Only the GATHER AUTO option gathers STATS on the index partition (as observed through the data within USER_IND_PARTITIONS).
Here is an Example of the Use Case scenario:
Neither option GATHER STALE nor GATHER EMPTY populates USER_IND_PARTITIONS with information that six (non-unique) keys are already present within index, SALESMAN_ID_IX, partition SALES_JAN2000.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |