Invalid Objects Exists In TMS User after TMS 4.6 Upgrade
(Doc ID 1083598.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Adverse Event Reporting System - Version 4.6.1 and laterInformation in this document applies to any platform.
Symptoms
After upgrade of TMS 4.5.2 to TMS 4.6.Invalid objects On TMS 4.6 new Install .
SQL> SELECT OBJECT_NAME, OBJECT_TYPE, STATUS, OWNER FROM ALL_OBJECTS WHERE STATUS='INVALID';
OBJECT_NAME OBJECT_TYPE STATUS OWNER
------------------------------ ------------------ ------- ------------------
TMS_TAL_MT_POOL PACKAGE BODY INVALID TMS
TMS_USER_THI_QTY_ACC VIEW INVALID TMS
TMS_USER_THI_QTY_ACC_QC VIEW INVALID TMS
TMS_USER_THI_QTY_UNALLOC VIEW INVALID TMS
On trying to compile
alter package TMS_TAL_MT_POOL compile body;
Show Errors;
SQL> Show Errors;
Errors for PACKAGE BODY TMS_TAL_MT_POOL:
LINE/COL ERROR
-------- -----------------------------------------------------------------
463/7 PL/SQL: SQL Statement ignored
484/23 PL/SQL: ORA-00904: "DEFACT"."DEF_ACTION_REF_KEY": invalid
identifier
488/7 PL/SQL: SQL Statement ignored
511/23 PL/SQL: ORA-00904: "DEFACT"."DEF_ACTION_REF_KEY": invalid
identifier
575/7 PL/SQL: SQL Statement ignored
593/23 PL/SQL: ORA-00904: "DEFACT"."DEF_ACTION_REF_KEY": invalid
identifier
Changes
Upgrade from TMS 4.5.2 to 4.6
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 |