RSA Identity Governance and Lifecycle 7.0.2 GA invalid object error after exporting and importing database schema

[#1]

Article Number

000035015

Applies To

RSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0.2
 

Issue

After exporting and importing database schema using the RSA Identity Governance and Lifecycle 7.0.2 install, the application will start the following message:
 

Initialization status
Initialization operations completed with errors.  Please resolve the problem(s) before the application server can accept requests.
Found Invalid object(s) in the database. Please check the log for error(s).
 

Image description

The following is in the AveksaSever.log:

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).

****************************************

The import process shows the following error:

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

Cause

This is due to an Oracle bug. The fix for Oracle issue 18881811 is listed to be available only as part of Oracle's 12.1.0.2 Bundle Patch 7 (April 2015), or any other patch set that superseded it. 

Resolution

Apply the Oracle patch or get the appliance updater 2017 Q1. 

Workaround

If it is not possible to apply the Oracle update or Appliance updater immediately, the following steps can also be used to workaround this issue:
 

1. Login to the database host as oracle user. Note that the steps below must be taken through an SSH session (and not using tools like SQL Developer) as access to files on the filesystem is required.
2. Save the following lines into a file (e. g., Entitlement_Review_Utils_workaround.sql).

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;

2. Run the script with sqlplus and avuser:

sqlplus avuser/<password> @Entitlement_Review_Utils_workaround.sql

3. Restart the IGL application:

acm restart

Notes

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.