A Troubleshooting the Oracle Identity Manager Upgrade

If you encounter errors while upgrading Oracle Identity Manager, review the following troubleshooting procedures.

Note:

The product Oracle Identity Manager is referred to as Oracle Identity Manager (OIM) and Oracle Identity Governance (OIG) interchangeably in the guide.

• WebLogic Server is Not in the Running Status
  After upgrading, the WebLogic admin server does not change to the running status.
• Upgrading Product Schemas Error: OIMR2PS2_OIM.PK_POP
  When you are upgrading the product schemas, the unique constraint OIMR2PS2_OIM.PK_POP violated error is displayed.
• Upgrading Product Schemas Error: OIMR2PS2_OIM.UK_ENTITY_TYPE
  When you are upgrading the product schemas, the OIMR2PS2_OIM.UK_ENTITY_TYPE violated error is displayed.
• KeystoreService Exception in the Logs After Reconfiguring the OIM Domain
  After you reconfigure the Oracle Identity Manager (OIM) domain, the logs show some exceptions which can be ignored.
• Warning when Generating the Pre-Upgrade Report for OIM
  When you run the pre-upgrade report utility to generate the pre-upgrade report for Oracle Identity Manager, the audit store instantiation failure warning is seen on the console, which can be ignored.
• Domain Reconfiguration Error
  When using the reconfiguration utility you might notice a Domain reconfig error. To fix this error, you need to manually delete the related applications and references.
• OIM Bootstrap for DEPLOYSOACOMPOSITES Task Fails After Upgrade
  After you complete the Oracle Identity Manager upgrade, when you start the Oracle Identity Manager Managed Servers for the first time, bootstrapping happens. If the OIM bootstrap fails for DEPLOYSOACOMPOSITES task, use the workaround described in this section to resolve the issue.
• Authorization Policy Merge Issue
  
• MAR Update or Metadata Merge Issue
  When you start the Oracle Identity Manager Managed Severs for the first time after upgrade, if you encounter any error during the bootstrap process which is related to MARUPDATE bootstrap task, run the external utility mergeMDSDataAfterUpgrade.sh from the 12c Middleware Home to re-trigger the Metadata Services (MDS) merge process.
• Error When Opening ADF DI Excel Sheet After Upgrade
  The ADFDI functionality will not work after you upgrade Oracle Identity Manager to 12c (12.2.1.3.0).
• Complilation Error When Starting the SOA Server After Upgrade
  When you start the Oracle SOA Suite for the first time after upgrade, you may see the compilation error in the SOA server logs.
• Warning in Oracle Identity Manager Server Logs After Upgrade
  After upgrade, the Oracle Identity Manager (OIM) Server logs show NPE warning, which can be ignored.
• Default Challenges Questions are not Updated After Upgrade
  After you upgrade Oracle Identity Manager 11.1.2.3.0 to 12c, the default challenge questions are not updated. It still shows the old or existing challenge questions.
• OPSS Processing Error When Reconfiguring the Domain
  When you upgrade a Oracle Identity Manager in an integrated environment, the OPSS processing error is encountered.
• EditFailedException When Releasing Configuration From WebLogic Console
  After you upgrade Oracle Identity Manager to 12c (12.2.1.3.0), when you click Release Configuration on Oracle WebLogic Console, the following error is seen:
• OIM Application Deployment Fails Intermittently
  After you upgrade Oracle Identity Manager to 12c (12.2.1.3.0), the oim application deployment may fail with the following error:
• soa-infra Application is in ‘Prepared’ State Post Upgrade
  After you upgrade Oracle Identity Manager (OIM) and Oracle Access Manager (OAM) integrated environment that was set up using Life Cycle Management (LCM) tool, the soa-infra application continues to be in Prepared mode, instead of showing active mode.
• Oracle Identity Manager Server Throws OutOfMemoryError
  When you start the servers post upgrade, OutOfMemoryError is thrown.
• SOA Fails to Join Coherence Cluster During the First Start After Upgrade
  After you upgrade Oracle Identity Manager (OIM) and Oracle Access Manager (OAM) integrated environment, when you start the Oracle SOA Suite Server for the first time, the coherence cluster fails to start with the following error:
• LDAP User Create and Update Reconciliation Job Fails
  LDAP User Create and Update Reconciliation job fails to run with the following exception:
• BI Managed Server is Seen on WebLogic Console After Upgrade
  The BI Managed Servers and cluster may not be deleted automatically during the upgrade if your domain has custom names for these servers, that is, names other than bi_server1, bi_server2, and so on. If these servers and cluster still exist post the upgrade, remove them manually via the WebLogic Console.
• Empty Pages or Panels After Upgrade
  After you complete the upgrade, the Applications tile in the OIM Self Service console and the Import/Export links in the Admin console may be rendered as empty pages or panels.
• OIM-AD Communication Fails After the Upgrade
  After the upgrade to 12c (12.2.1.3.0), the OIM-AD communication fails because the upgrade to 12c (12.2.1.3.0) changes the trust key to DemoTrust.
• Deployment Manager is Not Working After the Upgrade
  After the upgrade, when you open Deployment Manager (DM) from the Identity Sysadmin console, the DM window opens, but the UI components do not render, leaving the page blank and inoperable.
• Out Of Memory Error When Running the oigcloneFileOps.sh File
  If you encounter an out-of-memory (OOM) error during the execution of the oigcloneFileOps.sh file, check for the presence of excessively large files in Domain_Home and remove them temporarily. Run the Clone utility again.
• MDS Customizations are Removed After You Restart the OIM Managed Server of an Upgraded Setup
  If any MDS customizations are done after a successful upgrade to 12c (12.2.1.3.0) and if those customizations are lost after you restart the OIM Managed Server, you cannot recover the MDS changes. You have to do the MDS customizations again.
• OPatch Fails for not Finding the 'fuser' Command
  OPatch fails when it is unable to locate the fuser command.
• JPS-07508 or WSM-00401 Errors Seen When Accessing the Sysadmin Console
  This issue occurs when upgrading from OIM 11g Release 2 (11.1.2.3.0) to OIM 12c (12.2.1.3) where the OPSS Keystore Service (KSS) certificates are either corrupted or missing.
• OIM Bootstrap Fails Due to the Presence of Custom Application JARs
  If there are any custom developed libraries or JARs placed inside the OIM_HOME, the OIM bootstrap fails during the upgrade to Oracle Identity Manager 12c (12.2.1.3.0).
• Failure in the Compilation of BPEL Generated Classes From 11g in 12c
  Compilation of the generated BPEL classes from 11g fails in 12c if the class path setting is incorrect. Custom composites should have the dependent jars under BpelcClasspath to ensure that the composites are deployed successfully.
• User, Role, and Organization UDFs Missing After Upgrade from 11g to 12.2.1.x
  The User Defined Fields (UDFs) previously defined in the organization.xml and user.xml files are missing in the MDS storage, after the upgrade of Oracle Identity Manager from 11g (11.1.2.3) to 12c (12.2.1.x).