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:
- 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. - Completing the Pre-Upgrade Tasks for Oracle Identity Manager
Complete the pre-upgrade tasks described in this section before you upgrade 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. - 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. - Uninstalling the Software
Follow the instructions in this section to start the Uninstall Wizard and remove 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. - 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. - 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. - Tuning Database Parameters for Oracle Identity Manager
Before you upgrade the schemas, you must tune the Database parameters for Oracle Identity Manager. - 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. - Upgrading Domain Component Configurations
Use the Upgrade Assistant to upgrade the domain component configurations inside the domain to match the updated domain configuration. - Tuning Application Module for User Interface
After you successfully upgrade the Oracle Identity Manager middle-tier, tune the Application Module (AM). - Copying oracle.iam.ui.custom-dev-starter-pack.war from 12c Oracle Home
You have to manually copy theoracle.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/
. - Starting the Servers
After you upgrade Oracle Identity Manager, start 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. - Upgrading Oracle Identity Manager Design Console
Upgrade the Oracle Identity Manager Design Console after you upgrade the Oracle Identity Manager (OIM) domain component configurations. - 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.
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. |
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. |
|
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.
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. |
|
Required Tune the 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: Thejce should use unlimited strength crypto policy.
|
Required Tune the application module for Oracle Identity Manager |
|
Optional Copy the
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). |
|
Optional Perform the post-upgrade task. |
See Post-Upgrade Tasks. |
Completing the Pre-Upgrade Tasks for Oracle Identity Manager
Complete the pre-upgrade tasks described in this section before you upgrade Oracle Identity Manager.
- Verifying the Memory Settings
To avoid the memory issues for Oracle Identity Manager, ensure that the memory settings are updated as per the requirements. - 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. - Clean Temporary Folder
Clean the/tmp
folder on all the Oracle Identity Governance host machines. - Backing Up the metadata.mar File Manually
Verifying the Memory Settings
To avoid the memory issues for Oracle Identity Manager, ensure that the memory settings are updated as per the requirements.
root
user, do the following:
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.
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.
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:
-
(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.
- Log into Weblogic console as a
weblogic
Admin. - Go to Servers > Control tab.
- Select the required managed server.
- Click Shutdown.
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:
-
(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.
- Log into Weblogic console as a
weblogic
Admin. - Go to Servers > Control tab.
- Select the required admin server.
- Click Shutdown.
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
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.
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.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.
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.
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 InfrastructureParent 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 theuser_projects
directory anddomain-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 thedomain-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.
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:
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.
- Change directory to the
DOMAIN_HOME
location. - By using
grep
commands, search theDOMAIN_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.
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.
- 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. - Starting the Upgrade Assistant in Readiness Mode
Use the-readiness
parameter to start the Upgrade Assistant in readiness mode. - Performing a Readiness Check with the Upgrade Assistant
Navigate through the screens in the Upgrade Assistant to complete the 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.
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.
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 |
---|---|---|
|
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 |
|
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. |
|
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). |
|
Optional |
Performs the examine phase but does not perform an actual upgrade. Do not specify this parameter if you have specified the |
|
Optional |
Sets the logging level, specifying one of the following attributes:
The default logging level is Consider setting the |
|
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)
(Windows)
|
|
Optional |
Displays all of the command-line options. |
Parent topic: Starting the Upgrade Assistant in Readiness Mode
Performing a Readiness Check with the Upgrade Assistant
Navigate through the screens in the Upgrade Assistant to complete the pre-upgrade readiness check.
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
|
The directory location of the generated log file. |
No action required. |
Domain Directory | Displays the domain location | No action required. |
Readiness report location
|
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.
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='*';
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 inschema_version_registry
has been properly updated.
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:
-
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;
-
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.
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
.
- Go to the
oracle_common/upgrade/bin
directory:- (UNIX)
ORACLE_HOME
/oracle_common/upgrade/bin
- (Windows)
ORACLE_HOME
\oracle_common\upgrade\bin
- (UNIX)
- 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"
- (UNIX)
- 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 |
---|---|---|
|
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 |
|
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. |
|
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). |
|
Optional |
Performs the examine phase but does not perform an actual upgrade. Do not specify this parameter if you have specified the |
|
Optional |
Sets the logging level, specifying one of the following attributes:
The default logging level is Consider setting the |
|
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)
(Windows)
|
|
Optional |
Displays all of the command-line options. |
Parent topic: Starting the Upgrade Assistant
Upgrading Oracle Identity Manager Schemas Using the Upgrade Assistant
Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.
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 eitherUPGRADING
orUPGRADED
during the schema patching operation, and will becomeVALID
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
andIAU_VIEWER
will appear asINVALID
, 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.
- 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 Domain Component Configurations
Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.
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.
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
.
- Go to the
oracle_common/upgrade/bin
directory:- (UNIX)
ORACLE_HOME
/oracle_common/upgrade/bin
- (Windows)
ORACLE_HOME
\oracle_common\upgrade\bin
- (UNIX)
- 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"
- (UNIX)
- 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.
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:
Note:
If thesetUserOverridesLate.sh
file does not exist, you have to create
it.
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/
.
Starting the Servers
After you upgrade Oracle Identity Manager, start the servers.
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.
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)
<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
orWLS_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
Upgrading Oracle Identity Manager Design Console
Upgrade the Oracle Identity Manager Design Console after you upgrade the Oracle Identity Manager (OIM) domain component configurations.
- 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. - 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.
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:
- Copying Custom Configurations
- Handling Custom Applications
- 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. - Completing the Patching Activities
- Migrating to OID Connector if Using LDAPSync
- Defining System Properties for Legacy Connectors
- Increasing the Maximum Message Size for WebLogic Server Session Replication
- Increasing the maxdepth Value in setDomainEnv.sh
- Changing the JMS and TLOG Persistence Store After the Upgrade
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 theREADME.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.
- Validation and Transformation of Provisioning and Reconciliation Attributes in Performing Self Service Tasks with Oracle Identity Governance.
- Prepopulate Adapters in Developing and Customizing Applications for Oracle Identity Governance.
- Managing Access Policies in Performing Self Service Tasks with Oracle Identity Governance.
Parent topic: Post-Upgrade Tasks
Defining System Properties for Legacy Connectors
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.
- Log in to the WebLogic Server Administration Console.
- Navigate to Servers, select Protocols, and then click General.
- Set the value of Maximum Message Size to 100 MB.
Parent topic: Post-Upgrade Tasks
Increasing the
maxdepth
Value in setDomainEnv.sh
maxdepth
parameter is
250. To update this value:
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