1. Upgrading Oracle Identity Manager
  2. In-Place Upgrade of Oracle Identity Manager
  3. Upgrading Oracle Identity Manager Single Node Environments

3 Upgrading Oracle Identity Manager Single Node Environments

You can upgrade Oracle Identity Manager from Release 12c (12.2.1.3.0) to Oracle Identity Governance 12c (12.2.1.4.0) .

Note:

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

Complete the steps in the following topics to perform the upgrade:

Parent topic: In-Place Upgrade of Oracle Identity Manager

About the Oracle Identity Manager Single Node Upgrade Process

Review the roadmap for an overview of the upgrade process for Oracle Identity Manager single node deployments.

The steps you take to upgrade your existing domain will vary depending on how your domain is configured and which components are being upgraded. Follow only those steps that are applicable to your deployment.

Table 3-1 Tasks for Upgrading Oracle Identity Manager Single Node Environments

Task Description

Required

If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.

See:

Required

Complete the necessary pre-upgrade tasks specific to Oracle Identity Manager.

See Completing the Pre-Upgrade Tasks for Oracle Identity Manager.

Required

Shut down the 12c servers. This includes the Administration Server, Managed Servers, Node Manager, and system components such as Oracle HTTP Server.

Ensure that the Database is up during the upgrade.

WARNING: Failure to shut down your servers during an upgrade may lead to data corruption.

See Stopping Servers and Processes.

Required

Create backup of the existing 12c (12.2.1.3.0) Middleware home folders on OIMHOST

See Backing up the 12c (12.2.1.3.0) Oracle Home Folder on OIMHOST.

Required

Uninstall Oracle Fusion Middleware Infrastructure and Oracle Identity Manager 12c (12.2.1.3.0) in the existing Oracle home.

See Uninstalling the Software.

Required

Install Fusion Middleware Infrastructure 12c (12.2.1.4.0), Oracle SOA Suite12c (12.2.1.4.0) and Oracle Identity Manager12c (12.2.1.4.0) in the prepped 12c (12.2.1.3.0) Middleware home.

Install the following products in the prepped 12c (12.2.1.3.0) Middleware home on the same host as the 12c production deployment before you begin the upgrade.

  • Fusion Middleware Infrastructure 12c (12.2.1.4.0)

  • Oracle SOA Suite12c (12.2.1.4.0)

  • Oracle Identity Manager12c (12.2.1.4.0)

It is recommended that you use the simplified installation process to install the products mentioned above, using the quick installer. The quick installer installs the Infrastructure, Oracle SOA Suite, and Oracle Identity and Access Management 12c (12.2.1.4.0) in one go. See Installing Oracle Identity Governance Using Quick Installer in the Installing and Configuring Oracle Identity and Access Management.

The other option is to install these products separately using their respective installers. See Installing Product Distributions.

Required

Update the JDK location

 See Updating the JDK Location.

Note: This step is required only if you do not use the correct JDK to install.

Optional

Run a pre-upgrade readiness check.

See Running a Pre-Upgrade Readiness Check.

Required

Tune the Database parameters for Oracle Identity Manager.

See Tuning Database Parameters for Oracle Identity Manager.

Required

Start the Upgrade Assistant to upgrade the 12c database schemas and to migrate all active (in flight) instance data.

See Upgrading Product Schemas.

Note: The upgrade of active instance data is started automatically when running the Upgrade Assistant. Once the data is successfully upgraded to the new 12c (12.2.1.4.0) environment, you can close the Upgrade Assistant. The closed instances will continue to upgrade through a background process.

Required

Upgrade Domain Component Configurations

See Upgrading Domain Component Configurations.

Note:

The jce should use unlimited strength crypto policy.

Required

Tune the application module for Oracle Identity Manager

See Tuning Application Module for User Interface.

Optional

Copy the oracle.iam.ui.custom-dev-starter-pack.war file to the 12c (12.2.1.4.0) Middleware Home.

Note:

This step required only if the file is modified for UI customizations.

See Copying oracle.iam.ui.custom-dev-starter-pack.war to the 12c (12.2.1.4.0) Middleware Home.

Required

Start the servers.

See Starting the Servers.

Required

Verify that the domain-specific-component configurations is successful.

See Verifying the Domain-Specific-Component Configurations Upgrade.

Required

Upgrade the Oracle Identity Manager Design Console to 12c (12.2.1.4.0).

See Upgrading Oracle Identity Manager Design Console.

Optional

Perform the post-upgrade task.

See Post-Upgrade Tasks.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Completing the Pre-Upgrade Tasks for Oracle Identity Manager

Complete the pre-upgrade tasks described in this section before you upgrade Oracle Identity Manager.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Verifying the Memory Settings

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

On Linux, as a root user, do the following:
  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.

Parent topic: Completing the Pre-Upgrade Tasks for Oracle Identity Manager

Opening the Non-SSL Ports for SSL Enabled Setup

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.

Ensure that the database listener is listening on the same TCP port for the database servers that you provided to Upgrade Assistant as parameters. For more information, see Enabling SSL for Oracle Identity Governance DB.

Parent topic: Completing the Pre-Upgrade Tasks for Oracle Identity Manager

Clean Temporary Folder

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

As the /tmp directory is set against the JVM java.io.tmpdir property, any unwanted files in the /tmp folder can interfere with OIG upgrade process and might result is MDS corruption.

Parent topic: Completing the Pre-Upgrade Tasks for Oracle Identity Manager

Backing Up the metadata.mar File Manually

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.

Parent topic: Completing the Pre-Upgrade Tasks for Oracle Identity Manager

Stopping Servers and Processes

Before you run the Upgrade Assistant to upgrade the schemas and configurations, you must shut down all the pre-upgrade processes and servers, including the Administration Server, Node Manager (if you have configured Node Manager), and any managed servers.

An Oracle Fusion Middleware environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple managed servers, Java components, system components such as Identity Management components, and a database used as a repository for metadata. The components may be dependent on each other, so they must be stopped in the correct order.

Note:

  • The procedures in this section describe how to stop the existing, pre-upgrade servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager.
  • Stop all the servers in your deployment, except for the Database. The Database must be up during the upgrade process.

To stop your pre-upgrade Fusion Middleware environment, navigate to the pre-upgrade domain and follow the steps below.

Step 1: Stop the Managed Servers

Depending on the method you followed to start the managed servers, follow one of the following methods to stop the WebLogic Managed Server:

Method 1: To stop a WebLogic Server Managed Server not managed by Node Manager:

  • (UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url

  • (Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Method 2: To stop a WebLogic Server Managed Server by using the Weblogic Console:
  • Log into Weblogic console as a weblogic Admin.
  • Go to Servers > Control tab.
  • Select the required managed server.
  • Click Shutdown.
Method 3: To stop a WebLogic Server Managed Server using node manager, run the following commands:
wls:/offline>nmConnect('nodemanager_username','nodemanager_password',
            'AdminServerHostName','5556','domain_name',
            'DOMAIN_HOME','nodemanager_type')

wls:/offline>nmKill('ManagedServerName')

Step 2: Stop the Administration Server

When you stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

Follow one of the these methods to stop the Administration Server:

Method 1: To stop the Administration Server not managed by Node Manager:

  • (UNIX) DOMAIN_HOME/bin/stopWebLogic.sh

  • (Windows) DOMAIN_HOME\bin\stopWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Method 2: To stop the Administration Server by using the Weblogic Console:
  • Log into Weblogic console as a weblogic Admin.
  • Go to Servers > Control tab.
  • Select the required admin server.
  • Click Shutdown.
Method 3: To stop a WebLogic Server Managed Server using Node Manager, run the following commands:
wls:/offline>nmConnect('nodemanager_username','nodemanager_password',
            'AdminServerHostName','5556','domain_name',
            'DOMAIN_HOME','nodemanager_type')

wls:/offline>nmKill('AdminServer')

Step 4: Stop Node Manager

To stop Node Manager, run the following command:

<DOMAIN_HOME>/bin/stopNodeManager.sh

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Backing up the 12c (12.2.1.3.0) Oracle Home Folder on OIMHOST

Backup the 12c (12.2.1.3.0) Oracle Home on OIMHOST.

As a backup, copy and rename the 12.2.1.3.0 Oracle home folder on OIMHOST.

For example:

From /u01/app/fmw/ORACLE_HOME to /u01/app/fmw/ORACLE_HOME_old

Note:

Ensure that you back up any custom configuration. Post upgrade, you will restore these configurations.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Uninstalling the Software

Follow the instructions in this section to start the Uninstall Wizard and remove the software.

If you want to uninstall the product in a silent (command-line) mode, see Running the Oracle Universal Installer for Silent Uninstallation in Installing Software with the Oracle Universal Installer.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Starting the Uninstall Wizard

Start the Uninstall Wizard:

  1. Change to the following directory:
    (UNIX) ORACLE_HOME/oui/bin
    (Windows) ORACLE_HOME\oui\bin
  2. Enter the following command:
    (UNIX) ./deinstall.sh
    (Windows) deinstall.cmd

Parent topic: Uninstalling the Software

Selecting the Product to Uninstall

Because multiple products exist in the Oracle home, ensure that you are uninstalling the correct product.

After you run the Uninstall Wizard, the Distribution to Uninstall screen opens.

From the drop-down menu, select the Oracle Fusion Middleware 12c (12.2.1.4.0) Identity and Access Management product and click Uninstall.

Note:

The Uninstall Wizard displays the Distribution to Uninstall screen only if it detects more than one product distribution in the Oracle home from where you initate the wizard. If only Oracle Fusion Middleware 12c (12.2.1.4.0) Identity and Access Management product ditribution is available, the Uninstall Wizard will display the Deinstallation Summary screen.

Note:

Do not select Weblogic Server for FMW 12.2.1.3.0.

The uninstallation program shows the screens listed in Navigating the Uninstall Wizard Screens.

Note:

You can uninstall Oracle Fusion Middleware Infrastructure after you uninstall OIM or OAM software by running the Uninstall Wizard again. Before doing so, ensure that there are no other products using the Infrastructure, as those products will no longer function once the Infrastructure is removed. You will not encounter the Distribution to Uninstall screen if no other software depends on Oracle Fusion Middleware Infrastructure. See, Uninstalling Oracle Fusion Middleware Infrastructure in Installing and Configuring the Oracle Fusion Middleware Infrastructure

Parent topic: Uninstalling the Software

Navigating the Uninstall Wizard Screens

The Uninstall Wizard shows a series of screens to confirm the removal of the software.

If you need help on screen listed in the following table, click Help on the screen.

Table 3-2 Uninstall Wizard Screens and Descriptions

Screen Description

Welcome

Introduces you to the product Uninstall Wizard.

Uninstall Summary

Shows the Oracle home directory and its contents that are uninstalled. Verify that this is the correct directory.

If you want to save these options to a response file, click Save Response File and enter the response file location and name. You can use the response file later to uninstall the product in silent (command-line) mode. See Running the Oracle Universal Installer for Silent Uninstall in Installing Software with the Oracle Universal Installer.

Click Deinstall, to begin removing the software.

Uninstall Progress

Shows the uninstallation progress.

Uninstall Complete

Appears when the uninstallation is complete. Review the information on this screen, then click Finish to close the Uninstall Wizard.

Note:

  • Repeat these steps for uninstalling WebLogic Server for FMW 12.2.1.3.0.

    You will be reinstalling the Oracle binaries into the same location. The installation will fail if any files remain in the ORACLE_HOME location. If the installation fails, manually remove any remaining files from the ORACLE_HOME location prior to installing the new binaries.

  • For installations that have user_projects Domain Home information in the ORACLE_HOME directory: Delete all files and directories under the OIM_HOME except for the user_projects directory and domain-registry.xml file.

    For installations that have user_projects Domain Home information in a different directory than the ORACLE_HOME: Delete all files and directories under the OIM_HOME except the domain-registry.xml file.

Parent topic: Uninstalling the Software

Installing Product Distributions

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.

In addition, ensure that you have installed Java Development Kit (JDK) 1.8.0_211 or later.

Note:

When Infrastructure is required for the upgrade, you must install the Oracle Fusion Middleware distribution first before you install other Fusion Middleware products.

It is recommended that you use the simplified installation process to install the products mentioned above, using the quickstart installer (fmw_12.2.1.4.0_idmquickstart.jar). The quickstart installer installs the Infrastructure, Oracle SOA Suite, and Oracle Identity Manager 12c (12.2.1.4.0) in one go.

Note:

If you are using Redundant binary locations, ensure that you install the software into each of those redundant locations.

See Installing Oracle Identity Governance Using Quickstart Installer in the Installing and Configuring Oracle Identity and Access Management.

The other option is to install the required product distributions - Infrastructure, Oracle SOA Suite, and Oracle Identity Manager 12c (12.2.1.4.0) separately. To do this, complete the following steps:

  1. Sign in to the target system.
  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

    Note:

    If the user_projects directory and the domain-registry.xml file are left in place in the ORACLE_HOME, the -novalidation flag needs to be used to avoid the install from failing.

    Following is an example of the failure message:
    Verifying data......
[VALIDATION] [ERROR]:INST-07319: Validation of Oracle Home location failed. The location specified already exists and is a nonempty directory and not a valid Oracle Home
[VALIDATION] [SUGGESTION]:Provide an empty or nonexistent directory location, or a valid existing Oracle Home
installation Failed. Exiting installation due to data validation failure.
he Oracle Universal Installer failed. Exiting.
  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 the 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:
    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.
For more information about installing Oracle Identity Manager 12c (12.2.1.4.0), see Installing the Oracle Identity and Access Management Software in the Installing and Configuring Oracle Identity and Access Management.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Updating the JDK Location

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.

After upgrading to 12c (12.2.1.4.0), you must search the references to the current JDK in domain home and replace those instances with the location of the new JDK.

You must manually search the references to the current JDK in domain home and replace those instances with the location of the new JDK.

Complete the following steps to manually search and replace the JDK instances:
  1. Change directory to the DOMAIN_HOME location.
  2. By using grep commands, search the DOMAIN_HOME for files containing the old JDK version.

    The following example excludes logs ending in .log and .out, .txt, and .csv files.

    $ grep -rl <OLD_JDK_VERSION> * | grep -v "\.log" | grep -v "\.txt" | grep -v "\.csv" | grep -v "\.out"

For more information about updating the JDK location, see Updating the JDK Location in an Existing Domain Home.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Running a Pre-Upgrade Readiness Check

To identify potential issues with the upgrade, Oracle recommends that you run a readiness check before you start the upgrade process. Be aware that the readiness check may not be able to discover all potential issues with your upgrade. An upgrade may still fail, even if the readiness check reports success.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

About Running a Pre-Upgrade Readiness Check

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.

Note:

To prevent performance from being affected, Oracle recommends that you run the readiness check during off-peak hours.

Parent topic: Running a Pre-Upgrade Readiness Check

Starting the Upgrade Assistant in Readiness Mode

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

To perform a readiness check on your pre-upgrade environment with the Upgrade Assistant:
  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:

Parent topic: Running a Pre-Upgrade Readiness Check

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 3-3 Upgrade Assistant Command-Line Parameters

Parameter Required or Optional Description

-readiness

 Required for readiness checks

Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).

Performs the upgrade readiness check without performing an actual upgrade.

Schemas and configurations are checked.

Do not use this parameter if you have specified the -examine parameter.

-threads

Optional

Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas.

The value must be a positive integer in the range 1 to 8. The default is 4.

-response

Required for silent upgrades or silent readiness checks

Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).

-examine

Optional

Performs the examine phase but does not perform an actual upgrade.

Do not specify this parameter if you have specified the -readiness parameter.

-logLevel attribute

Optional

Sets the logging level, specifying one of the following attributes:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

Consider setting the -logLevel TRACE attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if -logLevel TRACE is used.

-logDir location

Optional

Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files.

The default locations are:

(UNIX)

ORACLE_HOME/oracle_common/upgrade/logs
ORACLE_HOME/oracle_common/upgrade/temp

(Windows)

ORACLE_HOME\oracle_common\upgrade\logs
ORACLE_HOME\oracle_common\upgrade\temp

-help

Optional

Displays all of the command-line options.

Performing a Readiness Check with the Upgrade Assistant

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

Readiness checks are performed only on schemas or component configurations that are at a supported upgrade starting point.
To complete the 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.

Parent topic: Running a Pre-Upgrade Readiness Check

Understanding the Readiness Report

After performing a readiness check for your domain, review the report to determine whether you need to take any action for a successful upgrade.

The format of the readiness report file is:

readiness<timestamp>.txt

Where, timestamp indicates the date and time of when the readiness check was run.

A readiness report contains the following information:

Table 3-4 Readiness Report Elements

Report Information Description Required Action
Overall Readiness Status: SUCCESS or FAILURE The top of the report indicates whether the readiness check passed or completed with one or more errors. If the report completed with one or more errors, search for FAIL and correct the failing issues before attempting to upgrade. You can re-run the readiness check as many times as necessary before an upgrade.

Timestamp

The date and time that the report was generated.

No action required.

Log file location

/oracle_common/upgrade/logs

The directory location of the generated log file.

No action required.
Domain Directory Displays the domain location No action required.

Readiness report location

/oracle_common/upgrade/logs

The directory location of the generated readiness report.

No action required.

Names of components that were checked

The names and versions of the components included in the check and status.

If your domain includes components that cannot be upgraded to this release, such as SOA Core Extension, do not attempt an upgrade.

Names of schemas that were checked

The names and current versions of the schemas included in the check and status.

Review the version numbers of your schemas. If your domain includes schemas that cannot be upgraded to this release, do not attempt an upgrade.

Individual Object Test Status: FAIL

The readiness check test detected an issue with a specific object.

Do not upgrade until all failed issues have been resolved.

Individual Object Test Status: PASS

The readiness check test detected no issues for the specific object.

If your readiness check report shows only the PASS status, you can upgrade your environment. Note, however, that the Readiness Check cannot detect issues with externals such as hardware or connectivity during an upgrade. You should always monitor the progress of your upgrade.

Completed Readiness Check of <Object> Status: FAILURE The readiness check detected one or more errors that must be resolved for a particular object such as a schema, an index, or datatype. Do not upgrade until all failed issues have been resolved.
Completed Readiness Check of <Object> Status: SUCCESS The readiness check test detected no issues. No action required.

Here is a sample Readiness Report file. Your report may not include all of these checks. 

Upgrade readiness check completed with one or more errors.

This readiness check report was created on Fri Aug 16 13:29:41 PDT 2019
Log file is located at: /oracle/work/middleware_latest/oracle_common/upgrade/logs/ua2019-08-16-13-23-36PM.log
Readiness Check Report File: /oracle/work/middleware_latest/oracle_common/upgrade/logs/readiness2019-08-16-13-29-41PM.txt
Domain Directory: /oracle/work/middleware_1212/user_projects/domains/jrf_domain

Starting readiness check of components.

Oracle Platform Security Services
   Starting readiness check of Oracle Platform Security Services.
     Schema User Name: DEV3_OPSS
     Database Type: Oracle Database
     Database Connect String: 
     VERSION Schema DEV3_OPSS is currently at version 12.1.2.0.0.  Readiness checks will now be performed.
   Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
     INFO   Database product version: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
   Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
   Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
   Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
   Starting schema test:  Test that the schema does not contain any unexpected tables  TEST_UNEXPECTED_TABLES
   Completed schema test: Test that the schema does not contain any unexpected tables --> TEST_UNEXPECTED_TABLES +++ Test that the schema does not contain any unexpected tables
   Starting schema test:  TEST_ENOUGH_TABLESPACE  Test that the schema tablespaces automatically extend if full
   Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
   Starting schema test:  TEST_USER_TABLESPACE_QUOTA  Test that tablespace quota for this user is sufficient to perform the upgrade
   Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
   Starting schema test:  TEST_ONLINE_TABLESPACE  Test that schema tablespaces are online
   Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
   Starting permissions test:  TEST_DBA_TABLE_GRANTS  Test that DBA user has privilege to view all user tables
   Completed permissions test: TEST_DBA_TABLE_GRANTS --> Test that DBA user has privilege to view all user tables +++ PASS
   Starting schema test:  SEQUENCE_TEST  Test that the Oracle Platform Security Services schema sequence and its properties are valid
   Completed schema test: SEQUENCE_TEST --> Test that the Oracle Platform Security Services schema sequence and its properties are valid +++ PASS
   Finished readiness check of Oracle Platform Security Services with status: SUCCESS.

Oracle Audit Services
   Starting readiness check of Oracle Audit Services.
     Schema User Name: DEV3_IAU
     Database Type: Oracle Database
     Database Connect String: 
     VERSION Schema DEV3_IAU is currently at version 12.1.2.0.0.  Readiness checks will now be performed.
   Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
     INFO   Database product version: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
   Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
   Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
   Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
   Starting schema test:  TEST_UNEXPECTED_TABLES  Test that the schema does not contain any unexpected tables
   Completed schema test: TEST_UNEXPECTED_TABLES --> Test that the schema does not contain any unexpected tables +++ PASS
   Starting schema test:  TEST_ENOUGH_TABLESPACE  Test that the schema tablespaces automatically extend if full
   Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
   Starting schema test:  TEST_USER_TABLESPACE_QUOTA  Test that tablespace quota for this user is sufficient to perform the upgrade
   Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
   Starting schema test:  TEST_ONLINE_TABLESPACE  Test that schema tablespaces are online
   Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
   Starting permissions test:  TEST_DBA_TABLE_GRANTS  Test that DBA user has privilege to view all user tables
   Completed permissions test: TEST_DBA_TABLE_GRANTS --> Test that DBA user has privilege to view all user tables +++ PASS
   Starting schema test:  TEST_MISSING_COLUMNS  Test that tables and views are not missing any required columns
   Completed schema test: TEST_MISSING_COLUMNS --> Test that tables and views are not missing any required columns +++ PASS
   Starting schema test:  TEST_UNEXPECTED_COLUMNS  Test that tables and views do not contain any unexpected columns
   Completed schema test: TEST_UNEXPECTED_COLUMNS --> Test that tables and views do not contain any unexpected columns +++ PASS
   Starting datatype test for table OIDCOMPONENT:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table OIDCOMPONENT: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table IAU_CUSTOM_01:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table IAU_CUSTOM_01: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table IAU_BASE:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table IAU_BASE: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table WS_POLICYATTACHMENT:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table WS_POLICYATTACHMENT: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table OWSM_PM_EJB:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table OWSM_PM_EJB: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table XMLPSERVER:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table XMLPSERVER: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table SOA_HCFP:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table SOA_HCFP: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting schema test:  SEQUENCE_TEST  Test that the audit schema sequence and its properties are valid
   Completed schema test: SEQUENCE_TEST --> Test that the audit schema sequence and its properties are valid +++ PASS
   Starting schema test:  SYNONYMS_TEST  Test that the audit schema required synonyms are present
   Completed schema test: SYNONYMS_TEST --> Test that the audit schema required synonyms are present +++ PASS
   Finished readiness check of Oracle Audit Services with status: FAILURE.

Common Infrastructure Services
   Starting readiness check of Common Infrastructure Services.
     Schema User Name: DEV3_STB
     Database Type: Oracle Database
     Database Connect String: 
   Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
   Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
   Completed schema test: ALL_TABLES --> TEST_REQUIRED_TABLES +++ Test that the schema contains all the required tables
   Starting schema test:  TEST_UNEXPECTED_TABLES  Test that the schema does not contain any unexpected tables
   Completed schema test: ALL_TABLES --> TEST_UNEXPECTED_TABLES +++ Test that the schema does not contain any unexpected tables
   Starting schema test:  TEST_REQUIRED_VIEWS  Test that the schema contains all the required database views
   Completed schema test: ALL_TABLES --> TEST_REQUIRED_VIEWS +++ Test that the schema contains all the required database views
   Starting schema test:  TEST_MISSING_COLUMNS  Test that tables and views are not missing any required columns
   Completed schema test: ALL_TABLES --> TEST_MISSING_COLUMNS +++ Test that tables and views are not missing any required columns
   Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
   Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
     INFO   Database product version: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
   Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
   Completed schema test: ALL_TABLES --> TEST_DATABASE_VERSION +++ Test that the database server version number is supported for upgrade
   Finished readiness check of Common Infrastructure Services with status: SUCCESS.

Oracle JRF
   Starting readiness check of Oracle JRF.
   Finished readiness check of Oracle JRF with status: SUCCESS.

System Components Infrastructure
   Starting readiness check of System Components Infrastructure.
   Starting config test:  TEST_SOURCE_CONFIG  Checking the source configuration.
     INFO /oracle/work/middleware_1212/user_projects/domains/jrf_domain/opmn/topology.xml was not found. No upgrade is needed.
   Completed config test: TEST_SOURCE_CONFIG --> Checking the source configuration. +++ PASS
   Finished readiness check of System Components Infrastructure with status: ALREADY_UPGRADED.

Common Infrastructure Services
   Starting readiness check of Common Infrastructure Services.
   Starting config test:  CIEConfigPlugin.readiness.test  This tests the readiness of the domain from CIE side.
   Completed config test: CIEConfigPlugin.readiness.test --> This tests the readiness of the domain from CIE side. +++ PASS
   Finished readiness check of Common Infrastructure Services with status: SUCCESS.

Finished readiness check of components.

Parent topic: Running a Pre-Upgrade Readiness Check

Tuning Database Parameters for Oracle Identity Manager

Before you upgrade the schemas, you must tune the Database parameters for Oracle Identity Manager.

See Performance Tuning Guidelines and Diagnostics Collection for Oracle Identity Manager (OIM) (Doc ID 1539554.1).

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Upgrading Product Schemas

After stopping servers and processes, use the Upgrade Assistant to upgrade supported product schemas to the current release of Oracle Fusion Middleware.

The Upgrade Assistant allows you to upgrade individually selected schemas or all schemas associated with a domain. The option you select determines which Upgrade Assistant screens you will use.

Note:

High waits and performance degradation may be seen due to 'library cache lock' (cycle)<='library cache lock' for DataPump Worker (DW) processes in the 12.2 RAC environment. To resolve this issue, you should disable S-Optimization by using the following command:
ALTER SYSTEM SET "_lm_share_lock_opt"=FALSE SCOPE=SPFILE SID='*';
After running the above command, restart all the RAC instances. After the upgrade is complete, you can reset the parameter by using the following command:
alter system reset "_lm_share_lock_opt" scope=spfile sid='*';
  • Identifying Existing Schemas Available for Upgrade
    This optional task enables you to review the list of available schemas before you begin the upgrade by querying the schema version registry. The registry contains schema information such as version number, component name and ID, date of creation and modification, and custom prefix.
  • Starting the Upgrade Assistant
    Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.
  • Upgrading Oracle Identity Manager Schemas Using the Upgrade Assistant
    Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.
  • Verifying the Schema Upgrade
    After completing all the upgrade steps, verify that the upgrade was successful by checking that the schema version in schema_version_registry has been properly updated.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Identifying Existing Schemas Available for Upgrade

This optional task enables you to review the list of available schemas before you begin the upgrade by querying the schema version registry. The registry contains schema information such as version number, component name and ID, date of creation and modification, and custom prefix.

You can let the Upgrade Assistant upgrade all of the schemas in the domain, or you can select individual schemas to upgrade. To help decide, follow these steps to view a list of all the schemas that are available for an upgrade:

  1. If you are using an Oracle database, connect to the database by using an account that has Oracle DBA privileges, and run the following from SQL*Plus:

    SET LINE 120
COLUMN MRC_NAME FORMAT A14
COLUMN COMP_ID FORMAT A20
COLUMN VERSION FORMAT A12
COLUMN STATUS FORMAT A9
COLUMN UPGRADED FORMAT A8
SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID;

  2. Examine the report that is generated.

    If an upgrade is not needed for a schema, the schema_version_registry table retains the schema at its pre-upgrade version.

Notes:

  • If your existing schemas are not from a supported version, then you must upgrade them to a supported version before using the 12c (12.2.1.4.0) upgrade procedures. Refer to your pre-upgrade version documentation for more information.

  • If you used an OID-based policy store in the earlier versions, make sure to create a new OPSS schema before you perform the upgrade. After the upgrade, the OPSS schema remains an LDAP-based store.

  • You can only upgrade schemas for products that are available for upgrade in Oracle Fusion Middleware release 12c (12.2.1.4.0). Do not attempt to upgrade a domain that includes components that are not yet available for upgrade to 12c (12.2.1.4.0).

Parent topic: Upgrading Product Schemas

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.

To start the Upgrade Assistant:

Note:

Before you start the Upgrade Assistant, make sure that the JVM character encoding is set to UTF-8 for the platform on which the Upgrade Assistant is running. If the character encoding is not set to UTF-8, then you will not be able to download files containing Unicode characters in their names. This can cause the upgrade to fail.

To ensure that UTF-8 is used by the JVM, use the JVM option -Dfile.encoding=UTF-8.

  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin
  2. Set a parameter for the Upgrade Assistant to include the JVM encoding requirement:
    • (UNIX) export UA_PROPERTIES="-Dfile.encoding=UTF-8"
    • (Windows) set UA_PROPERTIES="-Dfile.encoding=UTF-8"
  3. Start the Upgrade Assistant:
    • (UNIX) ./ua
    • (Windows) ua.bat

Note:

In the above command, ORACLE_HOME refers to the 12c (12.2.1.4.0) Oracle Home.

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

Parent topic: Upgrading Product Schemas

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 3-5 Upgrade Assistant Command-Line Parameters

Parameter Required or Optional Description

-readiness

 Required for readiness checks

Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).

Performs the upgrade readiness check without performing an actual upgrade.

Schemas and configurations are checked.

Do not use this parameter if you have specified the -examine parameter.

-threads

Optional

Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas.

The value must be a positive integer in the range 1 to 8. The default is 4.

-response

Required for silent upgrades or silent readiness checks

Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).

-examine

Optional

Performs the examine phase but does not perform an actual upgrade.

Do not specify this parameter if you have specified the -readiness parameter.

-logLevel attribute

Optional

Sets the logging level, specifying one of the following attributes:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

Consider setting the -logLevel TRACE attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if -logLevel TRACE is used.

-logDir location

Optional

Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files.

The default locations are:

(UNIX)

ORACLE_HOME/oracle_common/upgrade/logs
ORACLE_HOME/oracle_common/upgrade/temp

(Windows)

ORACLE_HOME\oracle_common\upgrade\logs
ORACLE_HOME\oracle_common\upgrade\temp

-help

Optional

Displays all of the command-line options.

Upgrading Oracle Identity Manager Schemas Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.

To upgrade product schemas with the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the Upgrade Type screen, select the schema upgrade operation that you want to perform:
    • Individually Selected Schemas if you want to select individual schemas for upgrade and you do not want to upgrade all of the schemas used by the domain.

      Caution:

      Upgrade only those schemas that are used to support your 12c (12.2.1.4.0) components. Do not upgrade schemas that are currently being used to support components that are not included in Oracle Fusion Middleware 12c (12.2.1.4.0).
    • All Schemas Used by a Domain to allow the Upgrade Assistant to discover and select all components that have a schema available to upgrade in the domain specified in the Domain Directory field. This is also known as a domain assisted schema upgrade. Additionally, the Upgrade Assistant pre-populates connection information on the schema input screens.

      Note:

      Oracle recommends that you select All Schemas Used by a Domain for most upgrades to ensure all of the required schemas are included in the upgrade.

    Note:

    If you are upgrading SSL enabled Oracle Identity Manager setup, select Individually Selected Schemas option, and then select Oracle Identity Manager schema only. This automatically selects the dependant schemas. For upgrading SSL enabled setup, you must provide the non-SSL Database connection details on the Schema Credentials screen.

  3. If you selected Individually Selected Schemas: On the Available Components screen, select the components for which you want to upgrade schemas. When you select a component, the schemas and any dependencies are automatically selected.

    Note:

    • For the individual schema option, the domain configuration is not accessed, and therefore password values are carried forward from the previous screen. If you encounter any connection failure, check the cause and fix it.

    • For the Upgrade Assistant utility to use the correct UMS schema, manually edit the UMS schema by adding _UMS as a suffix. For example, edit DEV to DEV_UMS for successful SOA upgrade.
  4. On the Screen name, select the domain folder.

    Click Next.

  5. On the Component List screen, it will display the list of components whose schema will be upgraded.

    Click Next.

  6. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  7. On the Schema Credentials screen(s), specify the database connection details for each schema you are upgrading (the screen name changes based on the schema selected):

    • Select the database type from the Database Type drop-down menu.

    • Enter the database connection details, and click Connect.

    • Select the schema you want to upgrade from the Schema User Name drop-down menu, and then enter the password for the schema. Be sure to use the correct schema prefix for the schemas you are upgrading.

    Click Next.

  8. On the Examine screen, review the status of the Upgrade Assistant as it examines each schema, verifying that the schema is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the schemas or configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  9. On the Upgrade Summary screen, review the summary of the options you have selected for schema upgrade.
    Verify that the correct Source and Target Versions are listed for each schema you intend to upgrade.
    If you want to save these options 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.
    Click Upgrade to start the upgrade process.
  10. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any schemas are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

    The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

    Click Next.

  11. After the upgrade completes successfully, the Upgrade Assistant provides the upgrade status and lists the next steps to take in the upgrade process. You should review the Upgrade Success screen of the Upgrade Assistant to determine the next steps based on the information provided. The wizard shows the following information:
    Upgrade Succeeded.

Log File: /u01/oracle/products/12c/identity/oracle_common/upgrade/logs/ua2020-09-15-18-27-29PM.txt
Post Upgrade Text file: /u01/oracle/products/12c/identity/oracle_common/upgrade/logs/postupgrade2020-09-15-18-27-29PM.txt
Next Steps

Oracle SOA
1. The Upgrade Assistant has successfully upgraded all active instances. You can now close the Upgrade Assistant.
2. The automated upgrade of closed instances will continue in the background after the Upgrade Assistant is exited and until the SOA server is started,at which point the upgrade will stop. You can schedule the upgrade of any remaining closed instances for a time when the SOA server is less busy.
   Close the Upgrade Assistant and use the instance data administration scripts to administer and monitor the overall progress of this automated upgrade. For more information see "Administering and Monitoring the Upgrade of SOA Instance Data" in Upgrading SOA Suite and Business Process Management.

    Click Close to complete the upgrade and close the wizard.

    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at ORACLE_HOME/oracle_common/upgrade/logs.

    Note:

    If the upgrade fails, you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

Parent topic: Upgrading Product Schemas

Verifying the Schema Upgrade

After completing all the upgrade steps, verify that the upgrade was successful by checking that the schema version in schema_version_registry has been properly updated.

If you are using an Oracle database, connect to the database as a user having Oracle DBA privileges, and run the following from SQL*Plus to get the current version numbers: 

SET LINE 120
COLUMN MRC_NAME FORMAT A14
COLUMN COMP_ID FORMAT A20
COLUMN VERSION FORMAT A12
COLUMN STATUS FORMAT A9
COLUMN UPGRADED FORMAT A8
SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;

In the query result:

  • Check that the number in the VERSION column matches the latest version number for that schema. For example, verify that the schema version number is 12.2.1.4.0.

    Note:

    However, that not all schema versions will be updated. Some schemas do not require an upgrade to this release and will retain their pre-upgrade version number.

  • The STATUS field will be either UPGRADING or UPGRADED during the schema patching operation, and will become VALID when the operation is completed.

  • If the status appears as INVALID, the schema update failed. You should examine the logs files to determine the reason for the failure.

  • Synonym objects owned by IAU_APPEND and IAU_VIEWER will appear as INVALID, but that does not indicate a failure.

    They become invalid because the target object changes after the creation of the synonym. The synonyms objects will become valid when they are accessed. You can safely ignore these INVALID objects.

Note:

Undo any non-SSL port changes and any non-SYSDBA user that you made when preparing for the upgrade.

Parent topic: Upgrading Product Schemas

Upgrading Domain Component Configurations

Use the Upgrade Assistant to upgrade the domain component configurations inside the domain to match the updated domain configuration.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.

To start the Upgrade Assistant:

Note:

Before you start the Upgrade Assistant, make sure that the JVM character encoding is set to UTF-8 for the platform on which the Upgrade Assistant is running. If the character encoding is not set to UTF-8, then you will not be able to download files containing Unicode characters in their names. This can cause the upgrade to fail.

To ensure that UTF-8 is used by the JVM, use the JVM option -Dfile.encoding=UTF-8.

  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin
  2. Set a parameter for the Upgrade Assistant to include the JVM encoding requirement:
    • (UNIX) export UA_PROPERTIES="-Dfile.encoding=UTF-8"
    • (Windows) set UA_PROPERTIES="-Dfile.encoding=UTF-8"
  3. Start the Upgrade Assistant:
    • (UNIX) ./ua
    • (Windows) ua.bat

Note:

In the above command, ORACLE_HOME refers to the 12c (12.2.1.4.0) Oracle Home.

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

Parent topic: Upgrading Domain Component Configurations

Upgrading Oracle Identity Manager Domain Component Configurations

Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.

Run the Upgrade Assistant to upgrade the domain component configurations to match the updated domain configuration.

To upgrade domain component configurations with the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the next screen:

    • Select All Configurations Used By a Domain. The screen name changes to WebLogic Components.

    • In the Domain Directory field, specify the OIM domain directory.

      Where, Domain Directory is the Administration server domain directory.

    Click Next.

  3. On the Component List screen, verify that the list includes all the components for which you want to upgrade configurations and click Next.
    If you do not see the components you want to upgrade, click Back to go to the previous screen and specify a different domain.
  4. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  5. On the Examine screen, review the status of the Upgrade Assistant as it examines each component, verifying that the component configuration is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  6. On the Upgrade Summary screen, review the summary of the options you have selected for component configuration upgrade.
    The response file collects and stores all the information that you have entered, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file.
    Click Upgrade to start the upgrade process.
  7. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

    The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

    Click Next.

  8. If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard. The Post-Upgrade Actions window describes the manual tasks you must perform to make components functional in the new installation. This window appears only if a component has post-upgrade steps.
    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at ORACLE_HOME/oracle_common/upgrade/logs.

    Note:

    If the upgrade fails you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

Parent topic: Upgrading Domain Component Configurations

Tuning Application Module for User Interface

After you successfully upgrade the Oracle Identity Manager middle-tier, tune the Application Module (AM).

The parameter jbo.ampool.maxavailablesize is used to let OIM know the number of concurrent users expected to access OIM. To check the default value, navigate to $DOMAIN_HOME/setDomainEnv.sh and search for the parameter jbo.ampool.maxavailablesize.

If the set value does not match the number of concurrent users you expect, you need to update that value in the setUserOverridesLate.sh file. It is important that you do not change the setDomainEnv.sh file directly as changes can be lost during future updates. All user defined values should appear in setUserOverridesLate.sh as changes to this file are persistent across upgrades.

The recommended value for the parameter jbo.ampool.maxavailablesize is the number of expected concurrent Users + 20%.

To add the recommended application module settings, complete the following:

  1. Open the file $DOMAIN_HOME/bin/setUserOverridesLate.sh in a text editor.
  2. Edit the setUserOverridesLate.sh file to add the following line:
    JAVA_OPTIONS="${JAVA_OPTIONS} -Djbo.ampool.maxavailablesize = <# of concurrent users + 20%>
  3. Save and close the setUserOverridesLate.sh file.

Note:

If the setUserOverridesLate.sh file does not exist, you have to create it.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Copying oracle.iam.ui.custom-dev-starter-pack.war from 12c Oracle Home

You have to manually copy the oracle.iam.ui.custom-dev-starter-pack.war file from the backup of 12c (12.2.1.3.0) Oracle Home to 12c (12.2.1.4.0) Oracle home: ORACLE_HOME/idm/server/apps/.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Starting the Servers

After you upgrade Oracle Identity Manager, start the servers.

You must start the servers in the following order:
  1. Start the Administration Server. If Node manager is configured, do not start the Node Manager.
  2. Start the Oracle SOA Suite Managed Server with the Administration Server URL. For example:
    ./startManagedWebLogic.sh <soa_managed_server_name> t3://weblogic_admin_host:weblogic_admin_port

    Note:

    In an SSL environment, when you start the managed servers for the first time for bootstrap, provide the non-SSL port number of the Administration Server.
  3. After the SOA server is in the running state and the soa-infra application in the ACTIVE status, start the Oracle Identity Manager Managed Server with the Administration Server URL. For example:
    /startManagedWebLogic.sh <oim_managed_server_name> t3://weblogic_admin_host:weblogic_admin_port

    Note:

    • As done in step 2, provide the non-SSL port number of the Administration Server.
    • The OIM managed server calls the soa-infra application when executing the bootstrap tasks. If the soa-infra application is not in ACTIVE status, then OIM bootstrap fails with the following error:
      <Error> <oracle.iam.OIMPostConfigManager> <BEA-000000> <Shutting down the
BootStrap Process. Please fix the problem and start the OIM Managed server
again to complete OIM BootStrap. OR, If you want to skip the feature which
has failed, mark the feature as complete using sql 'update oimbootstate set
state='COMPLETE' where featurename='FAILED_FEATURE_NAME' and start the
Managed Server again. In the latter case, you will have to manually perform
the task being done by the failed feature. Refer to the Install
documentations for the same>
java.lang.RuntimeException: None of the SOA servers are in RUNNING state!
at
oracle.iam.platform.mbeans.impl.util.SOAIntegrationUtil.getSOAServerURLs(SOAIn
tegrationUtil.java:358)
at
oracle.iam.OIMPostConfigManager.config.OIMConfigManager.updateOIMCONFIGXML(OIM
ConfigManager.java:2939)

    After the upgrade, when the OIM server starts for the first time, the 12c (12.2.1.4.0) bootstrap starts automatically and the server is not shut down.

For more information about stopping the servers and processes, see Stopping Servers and Processes.

  • Starting Servers and Processes
    After a successful upgrade, start all processes and servers, including the Administration Server and any Managed Servers.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Starting Servers and Processes

After a successful upgrade, start all processes and servers, including the Administration Server and any Managed Servers.

The components may be dependent on each other so they must be started in the correct order.

Note:

The procedures in this section describe how to start servers and process using the WLST command line or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.

To start your Fusion Middleware environment, follow the steps below.

Step 1: Start Node Manager (if configured)

Start the Node Manager from the Administration Server <DOMAIN_HOME>/bin location:

  • (UNIX) nohup ./startNodeManager.sh > <DOMAIN_HOME>/nodemanager/nodemanager.out 2>&1 &

  • (Windows) nohup .\startNodeManager.sh > <DOMAIN_HOME>\nodemanager\nodemanager.out 2>&1 &

Where <DOMAIN_HOME> is the Administration server domain home.

Step 2: Start the Administration Server

When you start the Administration Server, you also start the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

If you are not using nodemanager to start Administration Server, use the startWebLogic script:

  • (UNIX) DOMAIN_HOME/bin/startWebLogic.sh

  • (Windows) DOMAIN_HOME\bin\startWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 3: Start the Managed Servers

To start a WebLogic Server Managed Server, use the startManagedWebLogic script:

  • (UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url

  • (Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Note:

  • The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.
  • The Mobile Security Manager (MSM) servers are not supported in 12c. After restarting the servers, the 11g configurations of MSM servers, such as omsm_server1 or WLS_MSM1, might remain. Ignore these configurations and do not restart the MSM servers.

Parent topic: Starting the Servers

Verifying the Domain-Specific-Component Configurations Upgrade

To verify that the domain-specific-component configurations upgrade was successful, sign in to the Administration console and the Oracle Enterprise Manager Fusion Middleware Control and verify that the version numbers for each component is 12.2.1.4.0.

To sign in to the Administration Console, go to: http://administration_server_host:administration_server_port/console

To sign in to Oracle Enterprise Manager Fusion Middleware Control Console, go to: http://administration_server_host:administration_server_port/em

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Upgrading Oracle Identity Manager Design Console

Upgrade the Oracle Identity Manager Design Console after you upgrade the Oracle Identity Manager (OIM) domain component configurations.

To upgrade the Oracle Identity Manager Design Console, complete the following steps:
  1. Replace the 12c (12.2.1.4.0) designconsole/config/xlconfig.xml with the 12c (12.2.1.3.0) designconsole/config/xlconfig.xml file.
  2. If the design console is not configured in the previous version, when you start the design console, the host name and port values of the OIM Managed Server are changed to default variables. In the design console's start window, update the URL to the correct values for your installation.

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Post-Upgrade Tasks

After performing the upgrade of Oracle Access Manager to 12c (12.2.1.4), you should complete the tasks summarized in this section, if required.

This section includes the following topics:

Parent topic: Upgrading Oracle Identity Manager Single Node Environments

Copying Custom Configurations

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.

Note:

The back up of custom configurations that you created in Backing up the 12c (12.2.1.3.0) Oracle Home Folder on OIMHOST are restored in this step.

Parent topic: Post-Upgrade Tasks

Handling Custom Applications

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

Parent topic: Post-Upgrade Tasks

Reinstalling the ADF DI Excel Plug-in

After you upgrade Oracle Identity Manager to 12c (12.2.1.4.0), uninstall and reinstall the ADF DI Excel plug-in, and then re-download the Excel.

Parent topic: Post-Upgrade Tasks

Completing the Patching Activities

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.

Note:

In case you have followed manual patching instead of updating the stack patch bundle, use the README.txt file included in the bundle patch to complete any post-configuration steps that are performed after a restart of the systems. This procedure requires you to manually update the professionalization file and run the patch_oim_wls.sh script.

Parent topic: Post-Upgrade Tasks

Migrating to OID Connector if Using LDAPSync

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 information, see the following guides:

Parent topic: Post-Upgrade Tasks

Defining System Properties for Legacy Connectors

As part of post-upgrade tasks, for legacy connectors such as Resource Access Control Facility (RACF) that use the tcITResourceInstanceOperationsBean.getITResourceInstanceParameters method, you should create the following two system properties and update their values to True:
  • Service Account Encrypted Parameter Value
  • Service Account Parameters Value Store

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.

Parent topic: Post-Upgrade Tasks

Increasing the Maximum Message Size for WebLogic Server Session Replication

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.

Parent topic: Post-Upgrade Tasks

Increasing the maxdepth Value in setDomainEnv.sh

The recommended value for the maxdepth parameter is 250. To update this value:
  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.

Parent topic: Post-Upgrade Tasks

Changing the JMS and TLOG Persistence Store After the Upgrade

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.

Parent topic: Post-Upgrade Tasks