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.
Parent topic: In-Place Upgrade of Oracle Internet Directory
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. |
|
Required Install Oracle Fusion Middleware Infrastructure and Oracle Internet Directory 12c (12.2.1.3.0) in the new Oracle home. |
|
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. |
Optional Run 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. |
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:
|
Required Start the Reconfiguration Wizard to reconfigure the domain. |
Run the Configuration Wizard to update the existing domain to use the newly installed software. |
Required Start the Upgrade Assistant (again) to upgrade domain component configurations. |
Run the Upgrade Assistant to upgrade the reconfigured domain’s 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. |
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).Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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:
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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:
Note:
For more information about installing Oracle Internet Directory, see Installing the Oracle Internet Directory Software in the Installing Oracle Internet Directory.
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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.
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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 4-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 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
|
The directory location of the generated log file. |
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. |
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: machinename@yourcompany.com
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.Parent topic: Running a Pre-Upgrade Readiness Check
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.
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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.
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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.
- Go to the
oracle_common/upgrade/bin
directory:- (UNIX)
NEW_ORACLE_HOME/oracle_common/upgrade/bin
- (Windows)
NEW_ORACLE_HOME\oracle_common\upgrade\bin
- (UNIX)
- 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.
Parent topic: Upgrading Product Schemas
Upgrading Oracle Directory Integration Platform Schemas
Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.
Parent topic: Upgrading Product Schemas
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-->
-
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.- 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.
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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:
Parent topic: About Reconfiguring the Domain
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:
Parent topic: About Reconfiguring the Domain
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.Parent topic: About Reconfiguring the Domain
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.
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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.
- Go to the
oracle_common/upgrade/bin
directory:- (UNIX)
NEW_ORACLE_HOME/oracle_common/upgrade/bin
- (Windows)
NEW_ORACLE_HOME\oracle_common\upgrade\bin
- (UNIX)
- 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.
Parent topic: Upgrading Domain Component Configurations
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.
Parent topic: Upgrading Domain Component Configurations
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.
Parent topic: Upgrading Domain Component Configurations
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:
- 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.
- (UNIX)
- On the Welcome screen, select Extend an Existing WebLogic Domain, and then click Next.
- In the configuration wizard, from available templates list, select Oracle Directory Integration platform (DIP).
- Click Continue and complete the upgrade.
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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.
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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.
Parent topic: Upgrading Oracle Directory Integration Platform from 11g
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:
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:
-
Start the WebLogic Administration Server. See Starting Servers and Processes.
-
Log in to the WebLogic Administration console using the following URL:
http://admin_host:admin_port/console
-
Click Lock & Edit.
-
Click Environments, and then click Servers.
-
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. -
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 forwls_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.
-
-
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:
-
Go to Services, and click Data Sources.
-
Select a data source that is targeted to
wls_ods1
. -
Go to the Targets tab, and deselect wls_ods1.
-
Select All Servers in the Cluster.
-
Click Save.
-
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.
-
-
In case of cluster (high availability) setup, do the following:
-
Click Environments and then click Coherence Clusters.
-
Select defaultCoherenceCluster and then click Members.
-
Select Cluster.
-
Select All Servers in the cluster.
-
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:
-
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
-
Create a named
DIP_12.2.1.4.0/configuration
using the following command:mkdir -p DIP_12.2.1.4.0/configuration
-
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
-
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.
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.
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.
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.