11g Sys_plsql_% Type Records Exist In DBA_OBJECTS but not in DBA_TYPES
(Doc ID 1288785.1)
Last updated on AUGUST 07, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 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 Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
select from dba_objects where object_type = 'TYPE' and a record doesn't exist in dba_types
OWNER OBJECT_NAME STATUS
CTXSYS SYS_PLSQL_41157_DUMMY_1 VALID
CTXSYS SYS_PLSQL_41157_125_1 VALID
CTXSYS SYS_PLSQL_41157_100_1 VALID
CTXSYS SYS_PLSQL_41157_305_1 VALID
CTXSYS SYS_PLSQL_41157_290_1 VALID
CTXSYS SYS_PLSQL_41157_92_1 VALID
CTXSYS SYS_PLSQL_41157_74_1 VALID
CTXSYS SYS_PLSQL_41157_66_1 VALID
CTXSYS SYS_PLSQL_41157_38_1 VALID
CTXSYS SYS_PLSQL_41157_30_1 VALID
CTXSYS SYS_PLSQL_41157_12_1 VALID
CTXSYS SYS_PLSQL_41170_561_1 VALID
CTXSYS SYS_PLSQL_41170_DUMMY_1 VALID
CTXSYS SYS_PLSQL_41170_541_1 VALID
XDB SYS_PLSQL_9813600_DUMMY_1 VALID
XDB SYS_PLSQL_9813600_9_1 VALID
Changes
Oracle 11g introduced new system generated types that are excluded from the %_TYPES views.
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 |