The Stale Table Statistics alert warns when too many user or application tables in an Oracle container have stale optimizer statistics.
Mini DBA checks user/application tables in the current Oracle container/database and ignores system schemas such as SYS, SYSTEM, XDB, APEX, and other Oracle-owned accounts. Empty new installs with no visible user table statistics do not alert. When stale statistics are detected, the alert details include the affected container/database and sample owner.table names.
Outdated optimizer statistics can cause poor execution plans and performance degradation. Mini DBA evaluates this alert once a minute, while the underlying Oracle stale-statistics sample follows the lower cadence documented in the Oracle sampling policy.
This alert gives Mini DBA a focused signal for a condition that can affect Oracle reliability, performance, or operational visibility. It helps the team move from a general problem report to a specific metric, threshold, and investigation path.
Enable it on any monitored Oracle instance where this condition would require an administrator to investigate or communicate with the application team. Tune noisy development systems after you have a short baseline.
Threshold meaning: % stale. Major threshold: 25 %. Minor threshold: 10 %. Comparison direction: "over". Use higher thresholds on batch-heavy, development, or intentionally bursty systems where brief pressure is expected. Use lower thresholds on latency-sensitive production systems, small instances with little headroom, and services with strict recovery or availability commitments.
Open the related Mini DBA page for the instance, compare the current value with the recent baseline, note the affected container/database and sample table names, identify whether the change is caused by workload, configuration, host capacity, or maintenance, then record the corrective action in the incident notes.
If the alert creates repeated noise, review whether it is enabled on the correct instances, whether maintenance windows are configured, and whether the minor and major routes match the real business impact. System tables are excluded, so repeated alerts should normally point to application schemas with real table statistics. Keep enough history to prove the new setting before changing it broadly.
Use the alert configuration modal's Databases tab to exclude a database/PDB whose application statistics are intentionally unmanaged or irrelevant. When the sampled Oracle container/database is excluded, Mini DBA suppresses the stale-statistics alert for that container.