4 Upgrading Oracle Directory Integration Platform from 11g

You can upgrade Oracle Directory Integration Platform from Oracle Fusion Middleware Release 11g to 12c (12.2.1.3.0) .

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

• About the Oracle Directory Integration Platform Upgrade Process
  Review the flowchart and roadmap for an overview of the upgrade process for Oracle Directory Integration Platform
• Extending the 11g Domain to Include Oracle Directory Integration Platform
  Before you upgrade Oracle Directory Integration Platform to 12c, ensure that the 11g domain is configured with Oracle Directory Integration Platform 11.1.1.2.0 domain template.
• Installing Oracle Internet Directory
  Before beginning your upgrade, download Oracle Fusion Middleware Infrastructure and Oracle Internet Directory (OID) 12c (12.2.1.3.0) distributions on the target system and install them using Oracle Universal Installer.
• Creating the Required Schemas
  When upgrading from 11g, you must create the required 12c schemas. You can use the Repository Creation Utility (RCU) to create customized schemas or, optionally, you can use the Upgrade Assistant to create schemas using the default schema settings. This procedure describes how to create schemas using the RCU. Information about using the Upgrade Assistant to create schemas is covered in the upgrade procedures.
• 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.
• Stopping Servers and Processes
  Before you run the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all of the pre-upgrade processes and servers, including the Administration Server and any managed servers.
• 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.
• About Reconfiguring the Domain
  Run the Reconfiguration Wizard to reconfigure your domain component configurations to 12c (12.2.1.3.0).
• Upgrading Domain Component Configurations
  After reconfiguring the domain, use the Upgrade Assistant to upgrade the domain component configurations inside the domain to match the updated domain configuration.
• Additional Configuration to Include Oracle Directory Integration Platform
  Select the required option to upgrade Oracle Directory Integration Platform to 12c.
• Starting Servers and Processes
  After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.
• Performing Post-Upgrade Tasks for Oracle Directory Integration Platform
  After you upgrade Oracle Directory Integration Platform to 12c (12.2.1.3.0), perform the necessary post-upgrade tasks.

About the Oracle Directory Integration Platform Upgrade Process

Review the flowchart and roadmap for an overview of the upgrade process for Oracle Directory Integration Platform

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 4-1 Tasks for Upgrading Oracle Directory Integration Platform

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 Pre-Upgrade Requirements
Required Install Oracle Fusion Middleware Infrastructure and Oracle Internet Directory 12c (12.2.1.3.0) in the new Oracle home.	See Installing Oracle Internet Directory.
Required Start the Repository Creation Utility (RCU) to create the required 12c database schemas.	The schemas you create will vary depending on your existing schema configuration. See Creating the Required Schemas.
Optional Run a pre-upgrade readiness check.	See Running a Pre-Upgrade Readiness Check.
Required Shut down the 11g environment (stop all Administration and Managed Servers).	WARNING: Failure to shut down your servers during an upgrade may lead to data corruption. See Stopping Servers and Processes.
Required Start the Upgrade Assistant to upgrade the 11g 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.3.0) environment, you can close the Upgrade Assistant. The closed instances will continue to upgrade through a background process. This step is required only when OID is the backend Server. Do not perform this step when using DIP with OUD as the backend Server. As one of the steps requires connecting to the database for the ODS Schema, which does not exist in an OUD or DIP configuration.
Required Start the Reconfiguration Wizard to reconfigure the domain.	Run the Configuration Wizard to update the existing domain to use the newly installed software. See About Reconfiguring the Domain.
Required Start the Upgrade Assistant (again) to upgrade domain component configurations.	Run the Upgrade Assistant to upgrade the reconfigured domain’s component configurations. See Upgrading Domain Component Configurations.
Required Configuration to upgrade the Oracle Directory Integration platform.	See Additional Configuration to Include Oracle Directory Integration Platform.
Required Start the servers.	When the upgrade process is complete, restart the 12c (12.2.1.3.0) instance. See Starting Servers and Processes.
Required Perform the necessary post-upgrade tasks.	Ensure all of the upgraded components are working as expected before deleting your backups. See Performing Post-Upgrade Tasks for Oracle Directory Integration Platform.

Note:

The Oracle Directory Integration Platform version label remains the same (that is 11g Release 1 (11.1.1.9.0) or 12c (12.2.1.2.0, depending on the starting point of the upgrade) after the upgrade to 12c (12.2.1.3.0).

Extending the 11g Domain to Include Oracle Directory Integration Platform

Before you upgrade Oracle Directory Integration Platform to 12c, ensure that the 11g domain is configured with Oracle Directory Integration Platform 11.1.1.2.0 domain template.

Note:

This task is required only if you had configured Oracle Directory Integration Platform (DIP) with Oracle Internet Directory (OID) backend directory in your 11g Release 1 (11.1.1.9.0) deployment, using the instructions from one of the following sections:

• Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.9.0) Software in Oracle Fusion Middleware Installation Guide for Oracle Identity Managementfor 11g Release 1 (11.1.1.9.0).

• Configuring Oracle Identity Management for "Install Software - Do Not Configure" Option in Oracle Fusion Middleware Installation Guide for Oracle Identity Managementfor 11g Release 1 (11.1.1.9.0).

To do this, complete the following steps:

1. Start the configuration wizard by running the following command from the location EXISTING_MW_HOME/oracle_common/common/bin:
   • (UNIX) ./config.sh
   • (Windows) config.cmd
   Ensure you start this command from the 11g Middleware Home.
2. On the Welcome screen, select Extend an Existing WebLogic Domain.
   Click Next.
3. On the Select a WebLogic Domain Directory screen, select the OID or DIP 11.1.1.9 domain directory.
   Click Next.
4. On the Select Extension Source screen, select Oracle Directory Integration Platform 11.1.1.2.0.

   Click Next.

   Note:

   You will be prompted to confirm whether the conflict extension name "Oracle Directory Integration Platform" should be resolved with component type as application and server. Select Keep existing component and proceed.
5. On the Configure JDBC Data Sources screen, select the SchedulerDS data source. Verify that you specify the details for Host Name, Username, and Port of the OID or DIP Database.
   Click Next.
6. On the Test JDBC Data Sources screen, verify that the message Test Successful is displayed.
   Click Next.
7. On the Select Optional Configuration screen, click Next.
8. On the Configuration Summary screen, verify the details, and click Extend.
9. On the Extending Domain screen, verify that the message Domain Extension Applied Successfully! is displayed, and click Done.

Installing Oracle Internet Directory

Before beginning your upgrade, download Oracle Fusion Middleware Infrastructure and Oracle Internet Directory (OID) 12c (12.2.1.3.0) distributions on the target system and install them using Oracle Universal Installer.

Note:

Oracle Internet Directory 12c (12.2.1.3.0) should be installed in a new ORACLE_HOME location that is separate from the previous OID 11.1.1.9.0 ORACLE_HOME.

In case of a standalone Oracle Internet Directory upgrade, you do not have to install Oracle Fusion Middleware Infrastructure. You can install Oracle Internet Directory directly selecting the Standalone option.

To install the 12c (12.2.1.3.0) distributions:

1. Sign in to the target system.
2. Download the following from Oracle Technical Resources or Oracle Software Delivery Cloud to your target system:
   • Oracle Fusion Middleware Infrastructure (fmw_12.2.1.3.0_infrastructure.jar)
   • Oracle Internet Directory (UNIX: fmw_12.2.1.3.0_oid_<platform>.bin), (Windows: fmw_12.2.1.3.0_oid_win64.exe)
3. Change to the directory where you downloaded the 12c (12.2.1.3.0) product distribution.
4. Start the installation program for Oracle Fusion Middleware Infrastructure:
   • (UNIX) JAVA_HOME/bin/java -jar fmw_12.2.1.3.0_infrastructure_generic.jar
   • (Windows) JAVA_HOME\bin\java -jar fmw_12.2.1.3.0_infrastructure_generic.jar
5. 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.
6. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
7. 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.
8. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
   For more information about Oracle Fusion Middleware directory structure, see About the Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.
9. On the Installation Type screen, select the following:
   • For Infrastructure, select Fusion Middleware Infrastructure
   • For Oracle Internet Directory, select Standalone Oracle Internet Directory Server(Managed independently of Weblogic server) or Collocated Oracle Internet Directory Server(Managed through Weblogic server), as appropriate for your installation.
   Click Next.
10. 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).
11. 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.

12. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
13. 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.
14. After you have installed Oracle Fusion Middleware Infrastructure, enter the following command to start the installer for Oracle Internet Directory and repeat the steps above to navigate through the installer screens:
    (UNIX) ./fmw_12.2.1.3.0_oid_<platform>.bin
    (Windows) fmw_12.2.1.3.0_oid_win64.exe

Note:

For more information about installing Oracle Internet Directory, see Installing the Oracle Internet Directory Software in the Installing Oracle Internet Directory.

Creating the Required Schemas

When upgrading from 11g, you must create the required 12c schemas. You can use the Repository Creation Utility (RCU) to create customized schemas or, optionally, you can use the Upgrade Assistant to create schemas using the default schema settings. This procedure describes how to create schemas using the RCU. Information about using the Upgrade Assistant to create schemas is covered in the upgrade procedures.

The following schemas must exist before you upgrade to 12c. If you are upgrading from 11g, and you are not sure which schemas you currently have, refer to the steps below to identify the existing schemas in your domain. You do not need to re-create these schemas if they already exist.

• Service Table schema (prefix_STB). This schema is new in 12c and is required for domain-based upgrades. It stores basic schema configuration information (for example, schema prefixes and passwords) that can be accessed and used by other Oracle Fusion Middleware components during the domain creation. This schema is automatically created when you run the Repository Creation Utility (RCU), where you specify the existing schema owner prefix that you used for your other 11g schemas.

  Note:

  If the Service Table schema does not exist, you may encounter the error message UPGAST-00328 : The schema version registry table does not exist on this database. If that happens it is necessary to create the service table schema in order to run Upgrade Assistant

To create the 12c schemas with the RCU:

1. (Optional) If you are upgrading from 11g, and you wish to confirm the schemas which are present in your existing domain, then connect to the database as a user with DBA privileges, and run the following code 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. Verify that a certified JDK already exists on your system by running java -version from the command line. For 12c (12.2.1.3.0), the certified JDK is 1.8.0_131 and later.
   Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK. For example:
   • (UNIX) setenv JAVA_HOME=/home/Oracle/Java/jdk1.8.0_131
   • (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_131
   Add $JAVA_HOME/bin to $PATH.
3. Go to the oracle_common/bin directory:
   • (UNIX) NEW_ORACLE_HOME/oracle_common/bin
   • (Windows) NEW_ORACLE_HOME\oracle_common\bin
4. Start the RCU:
   • (UNIX) ./rcu
   • (Windows) rcu.bat
5. On the Welcome screen, click Next.
6. On the Create Repository screen, select Create Repository and then select System Load and Product Load.
   If you do not have DBA privileges, select Prepare Scripts for System Load. This will generate a SQL script containing all the same SQL statements and blocks that would have been called if the RCU were to execute the actions for the selected components. After the script is generated, a user with the necessary SYS or SYSDBA privileges can execute the script to complete the system load phase.

   Click Next.

7. On the Database Connection Details screen, select the Database Type and enter the connection information for the database that hosts the 12c (12.2.1.2.0) schemas. See the pertinent table below.

   Table 4-2 Connection Credentials for Oracle Databases and Oracle Databases with Edition-Based Redefinition

   Option	Description and Example
   Host Name	Specify the name of the server where your database is running in the following format: examplehost.exampledomain.com For Oracle RAC databases, specify the VIP name or one of the node names in this field.
   Port	Specify the port number for your database. The default port number for Oracle databases is 1521.
   Service Name	Specify the service name for the database. Typically, the service name is the same as the global database name. For Oracle RAC databases, specify the service name of one of the nodes in this field. For example: examplehost.exampledomain.com
   Username	Enter the user name for your database. The default user name is SYS.
   Password	Enter the password for your database user.
   Role	Select the database user's role from the drop-down list: Normal or SYSDBA

8. On the Select Components screen, if you have:
   • Oracle Unified Directory (OUD) as the backend directory in your 11g Release 1 (11.1.1.9.0) deployment, complete the following steps:
     1. Select Create new prefix and specify a custom prefix.
     2. Select the Oracle Platform Security Services schema.
        This automatically selects the following schemas as dependencies:

        • Audit Services
        • Audit Services Append
        • Audit Services Viewer
        • WebLogic Services
   • Oracle Internet Directory (OID) as the backend directory in your 11g Release 1 (11.1.1.9.0) deployment:

     Select the existing prefix and then select the prefix that was used to create the existing 11g schemas from the drop-down menu (for example, DEV11G).

     This prefix is used to logically group schemas together for use in this domain. Ensure that the following schemas are selected:

     • Oracle Platform Security Services
     • Audit Services
     • Audit Services Append
     • Audit Services Viewer
     • WebLogic Services

   Note:

   The Common Infrastructure Services (prefix_STB) schema is selected by default if it has not yet been created.

   Make a note of the prefix and schema names for the components you are installing as you will need this information when you configure the installation. Click Next.

9. In the Checking Prerequisites dialog, verify that the prerequisites check is successful, then click OK.
10. On the Schema Passwords screen, specify the passwords for your schema owners.
    Make a note of the passwords you enter on this screen as you will need this information while configuring your product installation.
11. On the Map Tablespaces screen, configure the desired tablespace mapping for the schemas you want to create.
    Click Next, then click OK in the confirmation dialog. When the progress dialog shows the tablespace creation is complete, click OK.
12. Verify the information on the Summary screen and click Create to begin schema creation.
    This screen contains information about the log files that were created from this RCU operation. Click on the name of a particular log file to view the contents of that file.
13. Review the information on the Completion Summary screen to verify that the operation is completed successfully. Click Close to complete the schema creation.

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.

Note:

This is applicable only for a collocated Oracle Internet Directory deployment scenario and not for a standalone deployment 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.
• 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.

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) NEW_ORACLE_HOME/oracle_common/upgrade/bin
   • (Windows) NEW_ORACLE_HOME\oracle_common\upgrade\bin
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, set the DISPLAY environment variable to the system name or IP address of your local workstation, and rerun Upgrade Assistant.

   If you continue to receive these errors after setting DISPLAY, try launching another GUI tool, such as vncconfig. If you see the same errors, your DISPLAY environment variable may still not be set correctly.

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

• Upgrade Assistant Parameters
  

Upgrade Assistant Parameters

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

Table 4-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) NEW_ORACLE_HOME/oracle_common/upgrade/logs NEW_ORACLE_HOME/oracle_common/upgrade/temp (Windows) NEW_ORACLE_HOME\oracle_common\upgrade\logs NEW_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.

   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 domain directory.

   • Specify schema credentials to connect to the selected schema: Database Type, DBA User Name, and DBA Password. 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.

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

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 4-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 NEW_ORACLE_HOME/oracle_common/upgrade/logs	The directory location of the generated log file.	No action required.
Readiness report location NEW_ORACLE_HOME/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 Tue May 30 11:15:52 EDT 2016
Log file is located at: NEW_ORACLE_HOME/oracle_common/upgrade/logs/ua2016-05-30-11-14-06AM.log
Readiness Check Report File: NEW_ORACLE_HOME/oracle_common/upgrade/logs/readiness2016-05-30-11-15-52AM.txt

Starting readiness check of components.

Oracle Metadata Services
   Starting readiness check of Oracle Metadata Services.
     Schema User Name: DEV11_MDS
     Database Type: Oracle Database
     Database Connect String: [e-mail]
     VERSION Schema DEV11_MDS is currently at version 12.1.1.1.0.  Readiness checks will now be performed.
   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_REQUIRED_PROCEDURES  Test that the schema contains all the required stored procedures
     EXCEPTION     Schema is missing a required procedure: GETREPOSITORYFEATURES
   Completed schema test: TEST_REQUIRED_PROCEDURES --> Test that the schema contains all the required stored procedures +++ FAIL
   Starting schema test:  TEST_REQUIRED_VIEWS  Test that the schema contains all the required database views
   Completed schema test: TEST_REQUIRED_VIEWS --> Test that the schema contains all the required database views +++ PASS
   Starting index test for table MDS_ATTRIBUTES:  TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
   Completed index test for table MDS_ATTRIBUTES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
   Starting index test for table MDS_COMPONENTS:  TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
   Completed index test for table MDS_TXN_LOCKS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
   Starting schema test:  TEST_REQUIRED_TRIGGERS  Test that the schema has all the required triggers
   Completed schema test: TEST_REQUIRED_TRIGGERS --> Test that the schema has all the required triggers +++ 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_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_UNEXPECTED_PROCEDURES  Test that the schema does not contain any unexpected stored procedures
   Completed schema test: TEST_UNEXPECTED_PROCEDURES --> Test that the schema does not contain any unexpected stored procedures +++ PASS
   Starting schema test:  TEST_UNEXPECTED_VIEWS  Test that the schema does not contain any unexpected views
   Completed schema test: TEST_UNEXPECTED_VIEWS --> Test that the schema does not contain any unexpected views +++ PASS
   Starting index test for table MDS_ATTRIBUTES:  TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
   Completed index test for table MDS_ATTRIBUTES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
   Completed index test for table MDS_LABELS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
   Starting index test for table MDS_LARGE_ATTRIBUTES:  TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
   Starting schema test:  TEST_UNEXPECTED_TRIGGERS  Test that the schema does not contain any unexpected triggers
   Completed schema test: TEST_UNEXPECTED_TRIGGERS --> Test that the schema does not contain any unexpected triggers +++ 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 MDS_ATTRIBUTES:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table MDS_ATTRIBUTES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table MDS_COMPONENTS:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   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_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 schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
     INFO   Database product version: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
   Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
   Finished readiness check of Oracle Metadata Services with status: FAILURE.

If you are running the 12.1.3.0 version of Oracle Fusion Middleware IAU Schemas, and those schemas were upgraded from 11g (11.1.1.7 and later) or 12c (12.1.2.0), your readiness check may fail with the following error:

Note:

This is not applicable for Oracle Internet Directory.

Starting index test for table IAU_COMMON:  TEST_REQUIRED_INDEXES --> Test 
that the table contains all the required indexes 
     INFO Audit schema index DYN_EVENT_CATEGORY_INDEX in table IAU_COMMON is 
missing the required columns or index itself is missing. This maybe caused by 
a known issue, anyway, this missing index will be added in 12.2.2 upgrade. 
     INFO Audit schema index DYN_EVENT_TYPE_INDEX in table IAU_COMMON is 
missing the required columns or index itself is missing. This maybe caused by 
a known issue, anyway, this missing index will be added in 12.2.2 upgrade. 
     INFO Audit schema index DYN_TENANT_INDEX in table IAU_COMMON is missing 
the required columns or index itself is missing. This maybe caused by a known 
issue, anyway, this missing index will be added in 12.2.2 upgrade. 
     INFO Audit schema index DYN_USER_INDEX in table IAU_COMMON is missing 
the required columns or index itself is missing. This maybe caused by a known 
issue, anyway, this missing index will be added in 12.2.2 upgrade. 
     INFO Audit schema index DYN_COMPONENT_TYPE_INDEX in table IAU_COMMON is 
missing the required columns or index itself is missing. This maybe caused by 
a known issue, anyway, this missing index will be added in 12.2.2 upgrade. 
     INFO Audit schema index DYN_USER_TENANT_INDEX in table IAU_COMMON is 
missing the required columns or index itself is missing. This maybe caused by 
a known issue, anyway, this missing index will be added in 12.2.2 upgrade. 
   Completed index test for table IAU_COMMON: TEST_REQUIRED_INDEXES --> Test 
that the table contains all the required indexes +++ FAIL

Note:

You can ignore the missing index error in the readiness report. This is a known issue. The corresponding missing index is added during the schema upgrade operation. This error does not occur if the schema to be upgraded was created in 12c using the RCU.

Stopping Servers and Processes

Before you run the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all of the pre-upgrade processes and servers, including the Administration Server 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.

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

Step 1: Stop System Components

To stop system components, such as Oracle HTTP Server, use the stopComponent script:

• (UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name

• (Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

You can stop system components in any order.

Step 2: Stop the Managed Servers

To stop a WebLogic Server Managed Server, use the stopManagedWebLogic script:

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

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

When prompted, enter your user name and password.

Step 3: Stop Oracle Identity Management Components

Stop any Oracle Identity Management components, such as Oracle Internet Directory:

• (UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name

• (Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

Step 4: 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.

To stop the Administration Server, use the stopWebLogic script:

• (UNIX) EXISTING_DOMAIN_HOME/bin/stopWebLogic.sh

• (Windows) EXISTING_DOMAIN_HOME\bin\stopWebLogic.cmd

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

Step 5: Stop Node Manager

To stop Node Manager, close the command shell in which it is running.

Alternatively, after setting the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. See stopNodeManager in WLST Command Reference for WebLogic Server.

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:

Upgrading product schemas is required only when OID is the backend Server. Do not perform this step when using DIP with OUD as the backend Server. As one of the steps requires connecting to the database for the ODS Schema, which does not exist in an OUD or DIP 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.3.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 Directory Integration Platform Schemas
  Navigate through the screens in the Upgrade Assistant to upgrade the 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.3.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:

1. Go to the oracle_common/upgrade/bin directory:
   • (UNIX) NEW_ORACLE_HOME/oracle_common/upgrade/bin
   • (Windows) NEW_ORACLE_HOME\oracle_common\upgrade\bin
2. Start the Upgrade Assistant:
   • (UNIX) ./ua
   • (Windows) ua.bat

For information about other parameters that you can specify on the command line, such as logging parameters, see Upgrade Assistant Parameters.

Upgrading Oracle Directory Integration Platform Schemas

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 Selected Schemas 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.3.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.3.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.

   Click Next.

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

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

7. On the Upgrade Summary screen, review the summary of the schemas that will be upgraded and/or created.
   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 Next .
8. 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.

9. If the upgrade is successful: On the Upgrade Success screen, 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 NEW_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.

About Reconfiguring the Domain

Run the Reconfiguration Wizard to reconfigure your domain component configurations to 12c (12.2.1.3.0).

When you reconfigure a WebLogic Server domain, the following items are automatically updated, depending on the applications in the domain:

• WebLogic Server core infrastructure

• Domain version

Note:

Before you begin the domain reconfiguration, note the following limitations:

• The Reconfiguration Wizard does not update any of your own applications that are included in the domain.

• Transforming a non-dynamic cluster domain to a dynamic cluster domain during the upgrade process is not supported.

  The dynamic cluster feature is available when running the Reconfiguration Wizard, but Oracle only supports upgrading a non-dynamic cluster upgrade and then adding dynamic clusters. You cannot add dynamic cluster during the upgrade process.

• If the installation that you’re upgrading does not use Oracle Access Management (OAM), then you must edit two files to prevent the Reconfiguration Wizard from attempting to update the nonexistent OAM Infrastructure schema, which causes the upgrade to fail.

  Comment out the lines in your $DOMAIN/init-info/domain-info.xml that are similar to this example:

  <!--extention-template-ref name="Oracle Identity Navigator" 
    version="11.1.1.3.0" 
    location="/u01/app/oracle/product/fmw/iam111130/common/templates/applications/yourcomany.oinav_11.1.1.3.0_template.jar" 
    symbol=""/-->
  
  <!--install-comp-ref name="oracle.idm.oinav" version="11.1.1.3.0" 
    symbol="yourcompany.idm.oinav_11.1.1.3.0_iam111130_ORACLE_HOME" 
    product_home="/u01/app/oracle/product/fmw/iam111130"/-->

  and similarly comment out the lines in $DOMAIN/config/config.xml that are similar to this example:

  <!--app-deployment> 
    <name>oinav#11.1.1.3.0</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
  
    <source-path>/u01/app/oracle/product/fmw/iam111130/oinav/modules/oinav.ear_11.1.1.3.0/oinav.ear</source-path>
    <deployment-order>500</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
  </app-deployment-->
  

Specifically, when you reconfigure a domain, the following occurs:

• The domain version number in the config.xml file for the domain is updated to the Administration Server's installed WebLogic Server version.

• Reconfiguration templates for all installed Oracle products are automatically selected and applied to the domain. These templates define any reconfiguration tasks that are required to make the WebLogic domain compatible with the current WebLogic Server version.

• Start scripts are updated.

  If you want to preserve your modified start scripts, be sure to back them up before starting the Reconfiguration Wizard.

Note:

When the domain reconfiguration process starts, you can’t undo the changes that it makes. Before running the Reconfiguration Wizard, ensure that you have backed up the domain as covered in the pre-upgrade checklist. If an error or other interruption occurs while running the Reconfiguration Wizard, you must restore the domain by copying the files and directories from the backup location to the original domain directory. This is the only way to ensure that the domain has been returned to its original state before reconfiguration.

Follow these instructions to reconfigure the existing domain using the Reconfiguration Wizard. See Reconfiguring WebLogic Domains in Upgrading Oracle WebLogic Server.

• Backing Up the Domain
  
• Starting the Reconfiguration Wizard
  
• Reconfiguring the Oracle Directory Integration Platform Domain
  Navigate through the screens in the Reconfiguration Wizard to reconfigure your existing domain.

Backing Up the Domain

Before running the Reconfiguration Wizard, create a backup copy of the domain directory.

To create a backup of the domain directory:

1. Copy the source domain to a separate location to preserve the contents.
   (Windows) copy C:\domains\mydomain to C:\domains\mydomain_backup.
   (UNIX) cp -rf mydomain mydomain_backup
2. Before updating the domain on each remote Managed Server, create a backup copy of the domain directory on each remote machine.
3. Verify that the backed up versions of the domain are complete.

If domain reconfiguration fails for any reason, you must copy all files and directories from the backup directory into the original domain directory to ensure that the domain is returned entirely to its original state before reconfiguration.

Starting the Reconfiguration Wizard

Note:

Shut down the administration server and all collocated managed servers before starting the reconfiguration process. See Stopping Servers and Processes.

To start the Reconfiguration Wizard in graphical mode:

1. Sign in to the system on which the domain resides.
2. Open the command shell (on UNIX operating systems) or open a command prompt window (on Windows operating systems).
3. Edition Based Database Users Only: If your schemas are configured with EBR database, a default edition name must be manually supplied before you run the Reconfiguration Wizard.
   Run the following SQL command to set the default edition:

   ALTER DATABASE DEFAULT EDITION = edition_name;

   where edition_name is the child edition name.

4. Go to the oracle_common/common/bin directory:
   • (UNIX) NEW_ORACLE_HOME/oracle_common/common/bin
   • (Windows) NEW_ORACLE_HOME\oracle_common\commom\bin
5. Start the Reconfiguration Wizard with the following logging options:
   • (UNIX) ./reconfig.sh -log=log_file -log_priority=ALL
   • (Windows) reconfig.cmd -log=log_file -log_priority=ALL

   where log_file is the absolute path of the log file you'd like to create for the domain reconfiguration session. This can be helpful if you need to troubleshoot the reconfiguration process.

   The parameter -log_priority=ALL ensures that logs are logged in fine mode.

   Note:

   When you run this command, the following error message might appear to indicate that the default cache directory is not valid:

   *sys-package-mgr*: can't create package cache dir
   

   You can change the cache directory by setting the environment variable CONFIG_JVM_ARGS. For example:

   CONFIG_JVM_ARGS=-Dpython.cachedir=valid_directory

Reconfiguring the Oracle Directory Integration Platform Domain

Navigate through the screens in the Reconfiguration Wizard to reconfigure your existing domain.

Note:

If the source is a clustered environment, run the Reconfiguration Wizard on the primary node only. Use the pack/unpack utility to apply the changes to other cluster members in the domain.

To reconfigure the domain with the Reconfiguration Wizard:

1. On the Select Domain screen, specify the location of the domain you want to upgrade or click Browse to navigate and select the domain directory. Click Next.
2. On the Reconfiguration Setup Progress screen, view the progress of the setup process. When complete, click Next.
   During this process:

   • The reconfiguration templates for your installed products, including Fusion Middleware products, are automatically applied. This updates various domain configuration files such as config.xml, config-groups.xml, and security.xml (among others).

   • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

   • The domain upgrade is validated.

3. On the Domain Mode and JDK screen, select the JDK to use in the domain or click Browse to navigate to the JDK you want to use. The supported JDK version for 12c (12.2.1.3.0) is 1.8.0_131 and later. Click Next.

   Note:

   You cannot change the Domain Mode at this stage.
   For a list of JDKs that are supported for a specific platform, see Oracle Fusion Middleware Supported System Configurations.
4. On the Database Configuration Type screen, select RCU Data to connect to the Server Table (_STB) schema. Enter the database connection details using the RCU service table (_STB) schema credentials and click Get RCU Configuration. The Reconfiguration Wizard uses this connection to automatically configure the data sources required for components in your domain.

   Note:

   For any existing 11g datasource, the reconfiguration will preserve the existing values. For new datasources where the schema was created for 12c by the RCU, the default connection data will be retrieved from the _STB schema. If no connection data for a given schema is found in the _STB schema, then the default connection data is used.

   If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.

5. On the JDBC Component Schema screen, verify that the DBMS/Service and the Host name is correct for each component schema and click Next.
6. On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema. The result of the test is indicated in the Status column.
   When the check is complete, click Next.
7. On the Advanced Configuration screen, you can select all categories for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.

   Note:

   The categories that are listed on the Advanced Configuration screen depend on the resources defined in the templates you selected for the domain.
   For this upgrade, select none of the options and click Next.
8. On the Configuration Summary screen, review the detailed configuration settings of the domain before continuing.
   You can limit the items that are displayed in the right-most panel by selecting a filter option from the View drop-down list.
   To change the configuration, click Back to return to the appropriate screen. To reconfigure the domain, click Reconfig.

   Note:

   The location of the domain does not change when you reconfigure it.
9. The Reconfiguration Progress screen displays the progress of the reconfiguration process.
   During this process:

   • Domain information is extracted, saved, and updated.

   • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

   When the progress bar shows 100%, click Next.
10. The End of Configuration screen indicates whether the reconfiguration process completed successfully or failed. It also displays the location of the domain that was reconfigured as well as the Administration Server URL (including the listen port). If the reconfiguration is successful, it displays Oracle WebLogic Server Reconfiguration Succeeded.
    If the reconfiguration process did not complete successfully, an error message is displayed indicates the reason. Take appropriate action to resolve the issue. If you cannot resolve the issue, contact My Oracle Support.
    Note the Domain Location and the Admin Server URL for further operations.

Upgrading Domain Component Configurations

After reconfiguring the domain, 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.3.0). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.
• Upgrading Domain Component Configurations
  Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.
• 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.3.0.

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.3.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:

1. Go to the oracle_common/upgrade/bin directory:
   • (UNIX) NEW_ORACLE_HOME/oracle_common/upgrade/bin
   • (Windows) NEW_ORACLE_HOME\oracle_common\upgrade\bin
2. Start the Upgrade Assistant:
   • (UNIX) ./ua
   • (Windows) ua.bat

For information about other parameters that you can specify on the command line, such as logging parameters, see Upgrade Assistant Parameters.

Upgrading Domain Component Configurations

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

After running the Reconfiguration Wizard to reconfigure the WebLogic domain to 12c (12.2.1.3.0), you must 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, enter the WebLogic domain directory path.

   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.

   In case of cluster upgrade, a pop-up message — Upgrade not necessary for Directory Integration Platform is displayed. Ignore this and proceed.

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

9. 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 NEW_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.

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

Note:

After upgrade, make sure you run the administration tools from the new 12c Oracle home directory and not from the previous Oracle home directory.

Additional Configuration to Include Oracle Directory Integration Platform

Select the required option to upgrade Oracle Directory Integration Platform to 12c.

Complete the following steps to upgrade Oracle Directory Integration Platform to 12c:

1. Start the configuration wizard by running the following command from the location EXISTING_MW_HOME/oracle_common/common/bin:
   • (UNIX) ./config.sh
   • (Windows) config.cmd

   Ensure that you start this command from the 12c Oracle Home.

2. On the Welcome screen, select Extend an Existing WebLogic Domain, and then click Next.
3. In the configuration wizard, from available templates list, select Oracle Directory Integration platform (DIP).
4. Click Continue and complete the upgrade.

Starting Servers and Processes

After a successful upgrade, restart 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 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.

To start the Administration Server, use the startWebLogic script:

• (UNIX) NEW_DOMAIN_HOME/bin/startWebLogic.sh

• (Windows) NEW_DOMAIN_HOME\bin\startWebLogic.cmd

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

Step 2: Start Node Manager

To start Node Manager, use the startNodeManager script:

• (UNIX) NEW_DOMAIN_HOME/bin/startNodeManager.sh

• (Windows) NEW_DOMAIN_HOME\bin\startNodeManager.cmd

Step 3: Start Oracle Identity Management Components

Start any Oracle Identity Management components, such as Oracle Internet Directory, that form part of your environment:

• (UNIX) NEW_DOMAIN_HOME/bin/startComponent.sh component_name

• (Windows) NEW_DOMAIN_HOME\bin\startComponent.cmd component_name

Step 4: Start the Managed Servers

Note:

Do not start the ODIP managed server (for example, wls_ods1) at this stage. As additional configuration is required as described in Updating ODIP Domain Configuration Details.

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

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

• (Windows) NEW_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.

Step 5: Start System Components

To start system components, such as Oracle HTTP Server, use the startComponent script:

• (UNIX) NEW_DOMAIN_HOME/bin/startComponent.sh component_name

• (Windows) NEW_DOMAIN_HOME\bin\startComponent.cmd component_name

You can start system components in any order.

Performing Post-Upgrade Tasks for Oracle Directory Integration Platform

After you upgrade Oracle Directory Integration Platform to 12c (12.2.1.3.0), perform the necessary post-upgrade tasks.

Note:

After upgrade, Resource Usage Charts will not be displayed in Enterprise Manager Oracle Directory Integration Platform 12c (12.2.1.3.0).

Topics:

• Updating ODIP Domain Configuration Details
  After you upgrade Oracle Directory Integration Platform (ODIP) to 12c (12.2.1.3.0), you must update the ODIP domain configurations.
• Adding the 12c Cipher Suites (Optional)
  Review the Secure Sockets Layer (SSL) modes available for Oracle Directory Integration Platform (ODIP).
• Copying the Custom Mapping Plug-ins to the Upgraded Environment
  After you upgrade Oracle Directory Integration Platform to 12c (12.2.1.3.0), you must copy the custom mapping plug-ins to the upgraded environment.
• Updating the Database Profiles With Service Names
  If you had created any database profiles in 11g, ensure that manually update existing value of SID with the service names, after upgrade.
• Importing Administration Server Certificate of Oracle Unified Directory to ODIP Trust Store
  If you are using Oracle Unified Directory as the backend directory, ensure that you import the Administration Server certificate of Oracle Unified Directory to Oracle Directory Integration Platform (ODIP) trust store.

Updating ODIP Domain Configuration Details

After you upgrade Oracle Directory Integration Platform (ODIP) to 12c (12.2.1.3.0), you must update the ODIP domain configurations.

Prior to upgrade, if none of the Managed Servers had the name wls_ods1, then you must delete the new managed server wls_ods1 that is created after upgrade. To do this, complete the following steps:

1. Start the WebLogic Administration Server. See Starting Servers and Processes.
2. Log in to the WebLogic Administration console using the following URL:
   http://admin_host:admin_port/console
3. Click Lock & Edit.
4. Click Environments and then click Coherence Clusters.
5. Select defaultCoherenceCluster and then click Members.
6. Deselect wls_ods1.
7. Click Save.
8. Go back to Environments, and click Servers.
9. Select wls_ods1.
10. Click Delete.
11. Save and Release the configuration once the changes are made.

Prior to upgrade, if any of the Managed Servers had the name wls_ods1, then you must update the Managed Server configuration settings to their original values which were present prior to upgrade. To do this, complete the following steps:

1. Start the WebLogic Administration Server. See Starting Servers and Processes.

2. Log in to the WebLogic Administration console using the following URL:

   http://admin_host:admin_port/console

3. Click Lock & Edit.

4. Click Environments, and then click Servers.

5. Locate the server name wls_ods1 under <server> tag in the $DOMAIN_HOME_BACKUP/config/config.xml file. This file contains the server configuration details that were present prior to upgrade.

6. Update the following sections on the Administration console with the values present in the backup config.xml file:

   • Go to the Keystores under SSL and Configuration , and update the SSL configuration information.

     Note:

     The step is mandatory if you configured SSL for wls_ods1 server prior to upgrade.

   • Go to the HTTP tab under Protocols, and update the value for Post Timeout.

   • Go to the Tuning tab under Configuration and click the Advanced link then update the values for Idle Periods Until Timeout, DGC Idle Periods Until Timeout.

   • Go to the General tab under Protocols and update the Complete Message Timeout, Idle Connection Timeout and so on, if they are present in the backup config.xml file.

   • Update any other details related to wls_ods1, that are present in the backup config.xml file.

7. In case of a cluster (high availability) setup, target the Infrastructure Data Sources to ODIP Managed Server cluster. To do this, complete the following steps:

   1. Go to Services, and click Data Sources.

   2. Select a data source that is targeted to wls_ods1.

   3. Go to the Targets tab, and deselect wls_ods1.

   4. Select All Servers in the Cluster.

   5. Click Save.

   6. Repeat the steps for all of the data sources that are targeted to wls_ods1, such as opss-audit-DBDS, opss-audit-viewDS, opss-data-source and so on.

8. In case of cluster (high availability) setup, do the following:

   1. Click Environments and then click Coherence Clusters.

   2. Select defaultCoherenceCluster and then click Members.

   3. Select Cluster.

   4. Select All Servers in the cluster.

   5. Release the configuration once the changes are made.

In a cluster (high availability) setup, copy the ODIP backened directory connection configuration file dip-config.xml to all of the Managed Server nodes, by doing the following:

1. Go to the directory DOMAIN_HOME/config/fmwconfig/servers/managed_server_name/applications. For example, on Unix, use the command:

   cd DOMAIN_HOME/config/fmwconfig/servers/wls_ods1/applications

2. Create a named DIP_12.2.1.4.0/configuration using the following command:

   mkdir -p DIP_12.2.1.4.0/configuration 

3. Copy the dip-config.xml to the new directory using the following command:

   cp -f DIP_12.2.1.3.0/configuration/dip-config.xml DIP_12.2.1.4.0/configuration/dip-config.xml

4. Restart the servers.

Adding the 12c Cipher Suites (Optional)

Review the Secure Sockets Layer (SSL) modes available for Oracle Directory Integration Platform (ODIP).

See Secure Sockets Layer and Oracle Directory Integration Platform in the Administrator's Guide for Oracle Directory Integration Platform.

If Oracle Directory Integration Platform was configured in SSL mode for backend directories or was communicating with connected directories in SSL mode pre-upgrade, and if any of the connected and backend directories do not have ciphers or security protocol available in 12c (12.2.1.3.0), then add to the new cipher suites to the list.

For example, if OID was the backend directory and configured in SSL no-auth mode prior to upgrade, then OID recognizes only anonymous ciphers during SSL negotiation. The anonymous ciphers in ODIP 12.2.1.3.0 are not supported by default. Therefore, you have two options:

• Configure OID and ODIP in server auth mode. This is a recommended approach. Refer to the following sections for more information:

  • Configuring Secure Sockets Layer (SSL) in Administering Oracle Internet Directory

  • Configuring Oracle Directory Integration Platform for Oracle Internet Directory SSL Authentication in Administering Oracle Directory Integration Platform

• Configure these additional anonymous ciphers along with the default additional ciphers supported by ODIP 12.2.1.3.0. See, Adding Cipher Suites Configured for Oracle Internet Directory into Oracle Directory Integration Platform in the Administrator's Guide for Oracle Directory Integration Platform.

Note:

In case of a cluster setup, perform these steps for each of the Managed Servers where ODIP is deployed.

Copying the Custom Mapping Plug-ins to the Upgraded Environment

After you upgrade Oracle Directory Integration Platform to 12c (12.2.1.3.0), you must copy the custom mapping plug-ins to the upgraded environment.

To do this, complete the following steps:

1. Ensure that you have started the Oracle Directory Integration Platform Managed Servers.
2. Copy the folder DOMAIN_NAME/servers/MANAGED_SERVER_NAME/tmp/_WL_user/DIP_VERSION_NUMBER/RANDOM_CHARACTERS/APP-INF/lib/ from the 11g environment to the 12c environment.
3. Restart the Oracle Directory Integration Platform Managed Servers.

   Note:

   In case of a cluster setup, perform these steps for each of the Managed Servers where ODIP is deployed.

Updating the Database Profiles With Service Names

If you had created any database profiles in 11g, ensure that manually update existing value of SID with the service names, after upgrade.

See Editing Synchronization Profiles in the Administering Oracle Directory Integration Platform.

Note:

It would continue to work even if you do not replace SID with service name, with connection exception in the log. However, it is recommended that you update the database profile with service name.

Importing Administration Server Certificate of Oracle Unified Directory to ODIP Trust Store

If you are using Oracle Unified Directory as the backend directory, ensure that you import the Administration Server certificate of Oracle Unified Directory to Oracle Directory Integration Platform (ODIP) trust store.

See Configuring Oracle Directory Integration Platform for Oracle Unified Directory in the Administering Oracle Directory Integration Platform.

Note:

• If you are upgrading from DIP 11g or the truststore was not configured prior to the upgrade, perform step 1 (exporting the certificate for the Oracle Unified Directory Administration Server instance) through step 5 (creating a CSF credential) described in Configuring Oracle Directory Integration Platform for Oracle Unified Directory in the Administering Oracle Directory Integration Platform.
• If truststore was configured prior to upgrade, perform step 1 (exporting the certificate for the Oracle Unified Directory Administration Server instance) and step 2 (importing the trusted certificate) described in Configuring Oracle Directory Integration Platform for Oracle Unified Directory in the Administering Oracle Directory Integration Platform.