DBA_HIST% Objects Become INVALID At Random
(Doc ID 312076.1)
Last updated on FEBRUARY 04, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 and laterOracle Database Cloud Schema 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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on any platform.
Fixed releases: patchset 10.2.0.3.0
Symptoms
The following set of objects become invalid in random:
DBA_HIST_FILESTATXS
DBA_HIST_LATCH
DBA_HIST_LATCH_MISSES_SUMMARY
DBA_HIST_DB_CACHE_ADVICE
DBA_HIST_ROWCACHE_SUMMARY
DBA_HIST_SGASTAT
DBA_HIST_SYSSTAT
DBA_HIST_SQLSTAT
DBA_HIST_SQLBIND
DBA_HIST_SYSTEM_EVENT
DBA_HIST_WAITSTAT
DBA_HIST_SYS_TIME_MODEL
DBA_HIST_OSSTAT
DBA_HIST_PARAMETER
DBA_HIST_SEG_STAT
DBA_HIST_ACTIVE_SESS_HISTORY
DBA_HIST_TABLESPACE_STAT
DBA_HIST_SERVICE_STAT
DBA_HIST_SERVICE_WAIT_CLASS
DBMS_SWRF_REPORT_INTERNAL
DBMS_SQLTUNE
At one moment there will not be any invalid objects in the database. All of a sudden you see the above list of invalid objects in the database.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |