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

Document created by RSA Customer Support Employee on Apr 12, 2017Last modified by RSA Customer Support Employee on May 1, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000035015
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0.2
 
IssueAfter 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).

 

User-added image

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) occured while compiling invalid object ENTITLEMENT_REVIEW_UTILS:
    LINE TEXT
-------- --------------------------------------------------
       0 - PLS-00753: malformed or corrupted wrapped unit
CauseThis is due to an Oracle bug. The fix for Oracle bug 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. 
ResolutionApply the Oracle patch or get the appliance updater 2017 Q1. 
WorkaroundIf it not possible to apply the Oracle update or Appliance updater immediately, the following steps can also be used to workaround this issue:
 
  1. 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;

  1. Execute the script with sqlplus and avuser:
sqlplus avuser/<password> @Entitlement_Review_Utils_workaround.sql

  1. Restart the application:
acm restart

Attachments

    Outcomes