To avoid the memory issues for Oracle Identity Manager, ensure that the memory settings are updated as per the requirements.

1. Ensure that you set the following parameters in the /etc/security/limits.conf or /etc/security/limits.d file, to the specified values:

   FUSION_USER_ACCOUNT soft nofile 32767
   FUSION_USER_ACCOUNT hard nofile 327679

2. Ensure that you set UsePAM to Yes in the /etc/ssh/sshd_config file.
3. Restart sshd.
4. Check the maxproc limit and increase it to a minimum of 16384, if needed. Increasing the limit will ensure you do not run into memory issues.

   Use the following command to check the limit:

   ulimit -u

   If less than 16384, use following command to increase the limit of open files:

   ulimit -u 16384

   Note:

   You can verify that the limit has been set correctly by reissuing the command ulimit -u.

   To ensure that the settings persist at reboot, add the following line to the /etc/security/limits.conf file or /etc/security/limits.d file:

   oracle hard nproc 16384

   Where, oracle is the install user.

5. Log out (or reboot) and log in to the system again.

If you have an SSL enabled and non-SSL disabled setup, you must open the non-SSL ports for the database before you proceed with the Oracle Identity Manager upgrade.

Clean the /tmp folder on all the Oracle Identity Governance host machines.

After you install the 12c (12.2.1.4.0) binaries in the existing Oracle Home, take a backup of the 12c (12.2.1.4.0)_ORACLE_HOME>/idm/server/apps/oim.ear/metadata.mar file before the upgrade.

Before beginning your upgrade, download Oracle Fusion Middleware Infrastructure, Oracle SOA Suite, and Oracle Identity Manager 12c (12.2.1.4.0) distributions on the target system and install them by using the following commands, in the existing 12c (12.2.1.3.0) Oracle Home.

1. Sign in to the target system (OIMHOST1).
2. Download the following from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
   • If you not yet installed Oracle Fusion Middleware Infrastructure, then download Oracle Fusion Middleware Infrastructure (fmw_12.2.1.4.0_infrastructure.jar)
   • Oracle SOA Suite (fmw_12.2.1.4.0_soa.jar)
   • Oracle Identity and Access Management 12cPS4 (fmw_12.2.1.4.0_idm_Disk1_1of1.zip, which contains fmw_12.2.1.4.0_idm.jar) from OTN or Oracle Fusion Middleware 12c (12.2.1.4.0) Identity and Access Management from Oracle Software Delivery Cloud.

   Note:

   Ensure that the ORACLE_HOME folder exists and it does not contain any files or folders. If there are any remaining files or folders in the ORACLE_HOME folder, delete them.
3. Change to the directory where you downloaded the 12c (12.2.1.4.0) product distribution.
4. If you have already installed Oracle Fusion Middleware Infrastructure (fmw_12.2.1.4.0_infrastructure.jar), go to step 15.
5. Start the installation program for Oracle Fusion Middleware Infrastructure pointing to the new JDK. Pointing to the new JDK location helps to skip a step later in the upgrade process.
   Run the following commands:
   • (UNIX) NEW_JDK_HOME/bin/java -jar fmw_12.2.1.4.0_infrastructure.jar
   • (Windows) NEW_JDK_HOME\bin\java -jar fmw_12.2.1.4.0_infrastructure.jar
6. On UNIX operating systems, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
   Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location, and click Next.

   Note:

   The Installation Inventory Setup screen does not appear on Windows operating systems.
7. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
8. On the Auto Updates screen, select an option:

   • Skip Auto Updates: If you do not want your system to check for software updates at this time.

   • Select patches from directory: To navigate to a local directory if you downloaded patch files.

   • Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.

   Click Next.
9. On the Installation Location screen, specify the location for the existing 12c (12.2.1.3.0) Oracle home directory and click Next.
   For example: If 12c (12.2.1.3.0) Oracle_home is located under /u01/app/fmw/, first uninstall 12c (12.2.1.3.0) and clean up the directory to install 12c (12.2.1.4.0) into /u01/app/fmw/.
   For more information about Oracle Fusion Middleware directory structure, see Understanding Directories for Installation and Configuration in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
10. On the Installation Type screen, select Fusion Middleware Infrastructure.
    Click Next.
11. The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
    To view the list of tasks that are verified, select View Successful Tasks. To view log details, select View Log. If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or the warning message and continue with the installation, click Skip (not recommended).
12. On the Installation Summary screen, verify the installation options that you selected.
    If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.

    Click Install to begin the installation.

13. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
14. The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.
15. After you have installed Oracle Fusion Middleware Infrastructure, enter the following command to start the installer for your product distribution and repeat the steps above to navigate through the installer screens:
    For installing Oracle SOA Suite 12c (12.2.1.4.0), run the following installer:

    Note:

    On the Installation Type screen, for Oracle SOA Suite, select Oracle SOA Suite.

    • (UNIX) NEW_JDK_HOME/bin/java -jar fmw_12.2.1.4.0_soa.jar

    • (Windows) NEW_JDK_HOME\bin\java -jar fmw_12.2.1.4.0_soa.jar

    For installing Oracle Identity Manager 12c (12.2.1.4.0), run the following installer:

    Note:

    On the Installation Type screen, for Oracle Identity Manager, select Collocated Oracle Identity and Access Manager.

    • (UNIX) NEW_JDK_HOME/bin/java -jar fmw_12.2.1.4.0_idm.jar

    • (Windows) NEW_JDK_HOME\bin\java -jar fmw_12.2.1.4.0_idm.jar

    Note:

    By using the opatch tool, apply the latest recommended bundle patches from Oracle Support. See Doc ID 2657920.1 and follow any post-patch steps after the upgrade process is complete. This provides the latest known fixes for upgrade process, if any.
16. If your existing 12c (12.2.1.3.0) DOMAIN_HOME resides within the 12c (12.2.1.3.0) Oracle home directory, do the following:

    Note:

    You need to perform this step only on OIMHOST1.
    1. Go to the 12c (12.2.1.3.0) Oracle home backup location.

       For example: /u01/app/fmw/ORACLE_HOME_old/

    2. Copy the user_projects folder.
    3. Go to the new installed 12c (12.2.1.4.0) Oracle home location.

       For example: /u01/app/fmw/ORACLE_HOME/

    4. Paste the copied user_projects folder.
17. Apply the latest Stack Patch Bundle (SPB) using OPatch, on the 12c (12.2.1.4) binaries. See Doc ID 2657920.1.

You can run the Upgrade Assistant in -readiness mode to detect issues before you perform the actual upgrade. You can run the readiness check in GUI mode using the Upgrade Assistant or in silent mode using a response file.

The Upgrade Assistant readiness check performs a read-only, pre-upgrade review of your Fusion Middleware schemas and WebLogic domain configurations that are at a supported starting point. The review is a read-only operation.

The readiness check generates a formatted, time-stamped readiness report so you can address potential issues before you attempt the actual upgrade. If no issues are detected, you can begin the upgrade process. Oracle recommends that you read this report thoroughly before performing an upgrade.

You can run the readiness check while your existing Oracle Fusion Middleware domain is online (while other users are actively using it) or offline.

You can run the readiness check any number of times before performing any actual upgrade. However, do not run the readiness check after an upgrade has been performed, as the report results may differ from the result of pre-upgrade readiness checks.

Use the -readiness parameter to start the Upgrade Assistant in readiness mode.

1. Go to the oracle_common/upgrade/bin directory:
   • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
   • (Windows) ORACLE_HOME\oracle_common\upgrade\bin

   Where, ORACLE_HOME is the 12c (12.2.1.4.0) Oracle Home.

2. Start the Upgrade Assistant.
   • (UNIX) ./ua -readiness
   • (Windows) ua.bat -readiness

   Note:

   If the DISPLAY environment variable is not set up properly to allow for GUI mode, you may encounter the following error:

   Xlib: connection to ":1.0" refused by server
   Xlib: No protocol specified 

   To resolve this issue you need to set the DISPLAY variable to the host and desktop where a valid X environment is working.

   For example, if you are running an X environment inside a VNC on the local host in desktop 6, then you would set DISPLAY=:6. If you are running X on a remote host on desktop 1 then you would set this to DISPLAY=remoteHost:1.

   For information about other parameters that you can specify on the command line, see:

• Upgrade Assistant Parameters
  

Navigate through the screens in the Upgrade Assistant to complete the pre-upgrade readiness check.

1. On the Welcome screen, review information about the readiness check. Click Next.
2. On the Readiness Check Type screen, select the readiness check that you want to perform:
   • Individually Selected Schemas allows you to select individual schemas for review before upgrade. The readiness check reports whether a schema is supported for an upgrade or where an upgrade is needed.

     When you select this option, the screen name changes to Selected Schemas.

   • Domain Based allows the Upgrade Assistant to discover and select all upgrade-eligible schemas or component configurations in the domain specified in the Domain Directory field.

     When you select this option, the screen name changes to Schemas and Configuration.

     Leave the default selection if you want the Upgrade Assistant to check all schemas and component configurations at the same time, or select a specific option:

     • Include checks for all schemas to discover and review all components that have a schema available to upgrade.

     • Include checks for all configurations to review component configurations for a managed WebLogic Server domain.

   Note:

   If you are running an enterprise type of deployment, the domain directory will be the directory where your Administration Server runs.

   Click Next.

3. If you selected Individually Selected Schemas: On the Available Components screen, select the components that have a schema available to upgrade for which you want to perform a readiness check.
   If you selected Domain Based: On the Component List screen, review the list of components that are present in your domain for which you want to perform a readiness check.
   If you select a component that has dependent components, those components are automatically selected. For example, if you select Oracle Platform Security Services, Oracle Audit Services is automatically selected.

   Depending on the components you select, additional screens may display. For example, you may need to:

   • Specify the Administrator server domain directory.

     Ensure that you specify the 12c (12.2.1.3.0) Administrator server domain directory.

   • Specify schema credentials to connect to the selected schema: Database Type, DBA User Name, and DBA Password. As part of the pre-upgrade requirements, you had created the required user, see Creating a Non-SYSDBA User to Run the Upgrade Assistant.

     Then click Connect.

     Note:

     Oracle database is the default database type. Make sure that you select the correct database type before you continue. If you discover that you selected the wrong database type, do not go back to this screen to change it to the correct type. Instead, close the Upgrade Assistant and restart the readiness check with the correct database type selected to ensure that the correct database type is applied to all schemas.

   • Select the Schema User Name option and specify the Schema Password.

     Note:

     The Upgrade Assistant automatically enables default credentials. If you are unable to connect, make sure that you manually enter the credentials for your schema before you continue.
   Click Next to start the readiness check.
4. On the Readiness Summary screen, review the summary of the readiness checks that will be performed based on your selections.
   If you want to save your selections to a response file to run the Upgrade Assistant again later in response (or silent) mode, click Save Response File and provide the location and name of the response file. A silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again.
   For a detailed report, click View Log.
   Click Next.
5. On the Readiness Check screen, review the status of the readiness check. The process can take several minutes.
   If you are checking multiple components, the progress of each component displays in its own progress bar in parallel.
   When the readiness check is complete, click Continue.
   The following components are marked as ready for upgrade although they are not upgraded. Ignore the ready for upgrade message against these components:

   • Oracle JRF
   • Common Infrastructure Services
   • Oracle Web Services Manager
6. On the End of Readiness screen, review the results of the readiness check (Readiness Success or Readiness Failure):

   • If the readiness check is successful, click View Readiness Report to review the complete report. Oracle recommends that you review the Readiness Report before you perform the actual upgrade even when the readiness check is successful. Use the Find option to search for a particular word or phrase within the report. The report also indicates where the completed Readiness Check Report file is located.

   • If the readiness check encounters an issue or error, click View Log to review the log file, identify and correct the issues, and then restart the readiness check. The log file is managed by the command-line options you set.

After you have uninstalled the software from the 12c (12.2.1.3) Oracle home, install the 12c (12.2.1.4) binaries into the same Oracle home.

When upgrading from 12c (12.2.1.3.0) to 12c (12.2.1.4.0), the reconfiguration wizard is not used. So, the latest JDK version is not automatically updated in the domain home.

If you had set custom configuration in your 12c (12.2.1.3.0) Oracle home, you need to copy the custom configuration present in your backup of 12c (12.2.1.3.0) Oracle home to the 12c (12.2.1.4.0) Oracle home.

For example: Copy any contents from standard directories such as XLIntegrations, connectorResources, and so on, under the backup of 12c (12.2.1.3.0) Oracle home to the corresponding directories under the 12c (12.2.1.4.0) Oracle home.

Similarly, if your schedule job parameters are referring anything from the 12c (12.2.1.3.0) Oracle home, then copy them from the backup of 12c (12.2.1.3.0) Oracle home to the corresponding directories under the 12c (12.2.1.4.0) Oracle home.

If custom applications and libraries are present in your deployment of OIM 11g, Oracle recommends you to update them manually after the upgrade to OIM 12c (12.2.1.4).

After restarting the servers, you have to complete the patching activities. These activities require the servers to be up and running. See Stack Patch Bundle for Oracle Identity Management Products (Doc ID 2657920.1) to complete the post-start phase.

During the post-start phase, the post start command is used to complete the post installation steps. This procedure requires you to manually update the professionalization file and run the patch_oim_wls.sh script.

If you have used container rules in the LDAPSync setup of your 11g deployment, you may want to reimplement the rules defined in the LDAPContainersRule.xml file either as part of transformation and pre-populate adapters and/or leverage the Access policies.

For more information about these system properties, see Table 18-2 of section Non-Default System Properties in Oracle Identity Governance in Administering Oracle Identity Governance.

Oracle recommends creating these system properties only if a legacy connector or an old custom code requires the legacy behavior.

Oracle recommends you to modify the Maximum Message Size from the default value of 10 MB to 100 MB. This value is used to replicate the session data across the nodes. You should perform this step for all the Managed servers and the Administration server.

1. Log in to the WebLogic Server Administration Console.
2. Navigate to Servers, select Protocols, and then click General.
3. Set the value of Maximum Message Size to 100 MB.

1. Open the $DOMAIN_HOME/bin/setDomainEnv.sh file in a text editor.
2. Locate the following code block:

   ALT_TYPES_DIR="${OIM_ORACLE_HOME}/server/loginmodule/wls,${OAM_ORACLE_HOME}/a
   gent/modules/oracle.oam.wlsagent_11.1.1,${ALT_TYPES_DIR}"
   export ALT_TYPES_DIR
   CLASS_CACHE="true"
   export CLASS_CACHE

3. Add the following lines at the end of the above code block:

   JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.oif.serialFilter=maxdepth=250"
   export JAVA_OPTIONS

4. Save and close the setDomainEnv.sh file.

The JMS and TLOG persistent store remain the same after the upgrade to Oracle Identity Manager 12c (12.2.1.4.0). That is, if the persistence store is file-based prior to the upgrade, it will be file-based after the upgrade as well.

If you want to change the persistence stores from a file-based system to a database-based system, you have to perform the steps manually. See Using Persistent Stores for TLOGs and JMS in an Enterprise Deployment.