ERROR (MSC service thread 1-3) [com.aveksa.migration.jdbctool.CheckDatabase] Found invalid object(s) in the database. Please check the log for error(s). INFO (MSC service thread 1-3) [com.aveksa.server.runtime.AveksaSystem] ******************** Aveksa System Initialization End ******************** FATAL (MSC service thread 1-3) [com.aveksa.server.runtime.AveksaSystem] **************************************** Initialization has failed! Found invalid object(s) in the database. Please check the log for error(s). ****************************************
ORA-39082: Object type PACKAGE BODY:"AVUSER"."ENTITLEMENT_REVIEW_UTILS" created with compilation warnings
Job "AVUSER"."SYS_IMPORT_SCHEMA_01" completed with 1 error(s) at Thu Apr 6 14:14:20 2017 elapsed 0 00:04:00
Recompiling the wrapped package does not work and Oracle reports the following error:
Error(s) occurred while compiling invalid object ENTITLEMENT_REVIEW_UTILS:
LINE TEXT
-------- --------------------------------------------------
0 - PLS-00753: malformed or corrupted wrapped unit
whenever sqlerror exit 1 rollback whenever oserror exit 2 rollback set serveroutput on size 1000000 @/home/oracle/database/packages/review/Entitlement_Review_Utils.pks @/home/oracle/database/packages/review/Entitlement_Review_Utils.pkb exec AV_Compile_Invalid_Objects;
sqlplus avuser/<password> @Entitlement_Review_Utils_workaround.sql
acm restart
WARNING: This KB article is for a very specific issue. If the symptoms/errors and product versions do not match exactly with the issue on your system, do not use this article.
This article is intended to be used when the specific object mention in the KB article "SYS_IMPORT_SCHEMA_01" generates the error. For all other objects do not use this article.
Note that if there is a general problem with the database as a result of a catastrophic failure then the most common symptom is a general failure compiling one or more arbitrary objects in the database. Do not use this article for these use cases.