Data dictionary problem: Huge values when query dba_segments
(Doc ID 466460.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 to 9.2.0.8 [Release 9.2]Oracle 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 Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Selecting from dba_segments returns huge values and whole database is about 30GB size.
Warning: Poor Storage Clauses (see <Note:50380.1>)
Segment Next Exts Pct MaxExtents
TABLE SYS.BOOTSTRAP$ 14660202147483645
TABLE SYS.UNDO$ 14660202147483645
TABLE SYS.PROXY_ROLE_DATA$ 14660202147483645
TABLE SYS.FILE$ 14660202147483645
TABLE SYS.CON$ 14660202147483645
TABLE SYS.OBJ$ 14660202147483645
TABLE SYS.PROXY_DATA$ 14660202147483645
TABLE SYS.UGROUP$ 14660202147483645
TABLE SYS.VIEW$ 14660202147483645
TABLE SYS.TYPED_VIEW$ 14660202147483645
TABLE SYS.SUPEROBJ$ 14660202147483645
TABLE SYS.SEQ$ 14660202147483645
TABLE SYS.PROCEDURE$ 14660202147483645
TABLE SYS.PROCEDUREINFO$ 14660202147483645
......
Warning: OBJECT name clashes with SCHEMA name - <Bug:2894111> etc..
Schema=FLEXREPAIR Object=FLEXREPAIR.FLEXREPAIR (TABLE)
Found 0 potential problems and 2386 warnings <<<
Contact Oracle Support with the output
to check if the above needs attention or not
PL/SQL procedure successfully completed.
Note : SYSTEM tablespace is LMT (Locally Managed Tablespace) so <Note 50380.1> does not apply.
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 |