GSMADMIN_INTERNAL objects are invalid
(Doc ID 2878393.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
After installing a Database Release Update (DBRU) or individual patches, some objects in the GSMADMIN_INTERNAL schema may become invalid in the database as a whole or in individual containers (PDBs).
For example, the query:
select owner, object_name, object_type, status from dba_objects where status='INVALID' and owner='GSMADMIN_INTERNAL' order by owner, object_name, object_type;
produces output similar to the following:
Example
------------------------------ ------------------------------ ----------------------------------- --------------- ------
GSMADMIN_INTERNAL DBMS_GSM_POOLADMIN PACKAGE BODY INVALID 3
GSMADMIN_INTERNAL CAT_ROLLBACK_TRIGGER TRIGGER INVALID 3
GSMADMIN_INTERNAL REQUEST_DELETE_TRIGGER TRIGGER INVALID 3
GSMADMIN_INTERNAL DONE_TRIGGER TRIGGER INVALID 3
GSMADMIN_INTERNAL GSMLOGOFF TRIGGER INVALID 3
GSMADMIN_INTERNAL GSM_CHANGE_MESSAGE TYPE INVALID 1
GSMADMIN_INTERNAL GSM_CHANGE_MESSAGE TYPE INVALID 1
GSMADMIN_INTERNAL DBPARAMS_T TYPE INVALID 1
GSMADMIN_INTERNAL GSM_CHANGE_MESSAGE TYPE INVALID 1
GSMADMIN_INTERNAL GSM_CHANGE_MESSAGE TYPE INVALID 1
GSMADMIN_INTERNAL INSTANCE_LIST TYPE INVALID 1
GSMADMIN_INTERNAL RAC_INSTANCE_T TYPE INVALID 1
GSMADMIN_INTERNAL DBPARAMS_LIST TYPE INVALID 1
Changes
Customer applied either a DBRU or individual patches to a database which led to the objects becoming invalid.
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 |