3 Upgrading an Oracle Data Integrator Standalone Agent Environment from 11g

You can upgrade an Oracle Data Integrator standalone agent environment that is not configured in a WebLogic domain from Oracle Fusion Middleware 11g to 12c (12.2.1.2).

• About the Oracle Data Integrator Standalone Agent Upgrade Process
  Review the flowchart and roadmap for an overview of the upgrade process for an Oracle Data Integrator Standalone agent that is not configured in a WebLogic domain.
• Installing the Oracle Data Integrator Standalone Agent Environment
  Before beginning your upgrade, download the Oracle Data Integrator 12c (12.2.1.2) distribution on the target system and install it using Oracle Universal Installer.
• Creating the Required 12c Schemas
  When upgrading from 11g, you must use the Repository Creation Utility (RCU) to create the required 12c schemas before you begin the upgrade.
• Stopping Servers and Processes
  Before running the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all 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.
• Upgrading Standalone System Component Configurations
  Use the Upgrade Assistant to upgrade the standalone agent’s component configurations when the agent is managed by OPMN. The standalone component configuration upgrade does not support upgrade of a standalone agent that is not managed by OPMN.
• Starting Servers and Processes
  After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.

3.1 About the Oracle Data Integrator Standalone Agent Upgrade Process

Review the flowchart and roadmap for an overview of the upgrade process for an Oracle Data Integrator Standalone agent that is not configured in a WebLogic domain.

Description of the illustration GUID-6A3B9ED2-5F3B-4FC1-AED7-62E04FC4549D-default.jpg

Table 3-1 Tasks for Upgrading an Oracle Data Integrator Standalone Agent from 11g

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: Introduction to Upgrading Oracle Data Integrator to 12c (12.2.1.2) Pre-Upgrade Requirements
Required Install Oracle Data Integrator Standalone 12c (12.2.1.2) in a new Oracle home.	Install the product software in a new Oracle home on the same host as the 11g production deployment before you begin the upgrade. In 12c, Oracle home is used to describe the 11g Middleware home. See Installing the Oracle Data Integrator Standalone Agent Environment.
Required Start the Repository Creation Utility (RCU) to create the required 12c database schemas.	Create the STB schema. See Creating the Required 12c Schemas.
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.2) environment, you can close the Upgrade Assistant. The closed instances will continue to upgrade through a background process.
Required if managed by OPMN Start the Upgrade Assistant (again) to upgrade standalone system component configurations.	Run the Upgrade Assistant to upgrade the standalone agent’s component configurations when the agent is managed by OPMN. The standalone component configuration upgrade does not support upgrade of a standalone agent that is not managed by OPMN. See Upgrading Standalone System Component Configurations.
Required Restart the servers and the 12c (12.2.1.2) instance.	When the upgrade process is complete, restart the 12c (12.2.1.2) instance. See Starting Servers and Processes.
Required Verify the upgrade.	Ensure all of the upgraded components are working as expected before deleting your backups.

3.2 Installing the Oracle Data Integrator Standalone Agent Environment

Before beginning your upgrade, download the Oracle Data Integrator 12c (12.2.1.2) distribution on the target system and install it using Oracle Universal Installer.

To install the 12c (12.2.1.2) distribution:

1. Sign in to the target system where you want to install the 12c (12.2.1.2) product distribution.
2. Download the following 12c (12.2.1.2) product distribution from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
   • Oracle Data Integrator (fmw_12.2.1.2.0_odi_Disk1_1of2.zip and fmw_12.2.1.2.0_odi_Disk1_2of2.zip )
3. Change to the directory where you downloaded the 12c (12.2.1.2) product distribution.
4. Unzip the installer fmw_12.2.1.2.0_odi_Disk1_1of2.zip and fmw_12.2.1.2.0_odi_Disk1_2of2.zip files.
5. Enter the following command to start the installer for your product distribution and repeat the steps above to navigate through the installer screens:
   (UNIX) JDK_HOME/bin/java -jar fmw_12.2.1.2.0_odi_generic.jar
   (Windows) JDK_HOME\bin\java -jar fmw_12.2.1.2.0_odi_generic.jar
6. On UNIX operating systems, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
   Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location and click Next.

   Note:

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

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

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

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

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

    Click Install to begin the installation.

13. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
14. The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.

3.3 Creating the Required 12c Schemas

When upgrading from 11g, you must use the Repository Creation Utility (RCU) to create the required 12c schemas before you begin the upgrade.

For the ODI environments described in this guide, the required schemas are:

• ODI standalone agent (no WebLogic domain): STB

• ODI standalone collocated agent (with WebLogic domain): STB, OPSS, IAU, IAU_VIEWER, and IAU_APPEND

• ODI Java EE agent: STB, OPSS, IAU, IAU_VIEWER, and IAU_APPEND

Note:

If you are upgrading from a previous 12c release of Oracle Fusion Middleware, you do not need to re-create these schemas if they already exist. Refer to the steps below to identify the existing schemas in your domain.

If you are upgrading from 11g, refer to the Pre-Upgrade Checklist to identify the existing schemas in your domain. The following schemas must exist before you upgrade to 12c:

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

• Oracle Platform Security Services (OPSS) schema (prefix_OPSS). This schema is required if you are using an OID-based security store in 11g. This schema is automatically created when you run the Repository Creation Utility (RCU). The only supported LDAP-based OPSS security store is Oracle Internet Directory (OID). An LDAP-based policy store is typically used in production environments. You do not need to reassociate an OID-based security store before upgrade. While the Upgrade Assistant is running, you can select the OPSS schema. The Upgrade Assistant upgrades the OID-based security store automatically. Note: The 12c OPSS database schema is required so that you can reference the 12c schema during the reconfiguration of the domain. Your domain continues to use the OID-based security store after the upgrade is complete.

• Audit schemas. When upgrading audit services (_IAU), make sure that you select _IAU_VIEWER and _IAU_APPEND in addition to _IAU. The Upgrade Assistant will handle their creation for you automatically when they are selected.

To create the 12c schemas with the RCU:

1. (Optional) If you are upgrading from 11g, and you would like to confirm which schemas are in your existing domain, 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.2), the certified JDK is 1.8.0_101 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_101
   • (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_101
   Add $JAVA_HOME/bin to $PATH.
3. Go to the oracle_common/bin directory:
   • (UNIX) ORACLE_HOME/oracle_common/bin
   • (Windows) 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 11g schemas. See the pertinent table below.

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

   Table 3-3 Connection Credentials for MySQL Databases

   Option	Description and Example
   Host Name	Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.
   Port	Specify the port number for your database.
   Database Name	Specify the name of your database.
   Username	Specify the name of a user with administrator privileges.
   Password	Enter the password for your database user.

   Table 3-4 Connection Credentials for Microsoft SQL Server Databases

   Option	Description and Example
   Unicode Support	Select Yes or No from the drop-down list.
   Server Name	Specify the host name, IP address, or complete server name in host\server format of the server where your database is running. MSSQL named instances: A named instance is identified by the network name of the computer plus the instance name that you specify during installation. The client must specify both the server name and the instance name when connecting.
   Port	Specify the port number for your database.
   Database Name	Specify the name of your database.
   Username	Specify the name of a user with administrator privileges.
   Password	Enter the password for your database user.

   Table 3-5 Connection Credentials for IBM DB2 Databases

   Option	Description and Example
   Server Name	Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.
   Port	Specify the port number for your database.
   Database Name	Specify the name of your database.
   Username	Specify the name of a user with DB Owner privileges. The default user name for IBM DB2 databases is db2admin.
   Password	Enter the password for your database user.

   If the prerequisite check is successful, click OK to continue to the next page. If the check fails, review the details you entered and try again.
8. On the Select Components screen, select Select existing prefix and 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.
   Note: The Common Infrastructure Services Service Table (prefix_STB) and Oracle Platform Security Services (prefix_OPSS) schemas are selected by default if they have 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.
    You see the Encrypt Tablespace check box only if you have enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU. Select the Encrypt Tablespace check box on the Map Tablespaces screen to encrypt all new tablespaces that the RCU creates.
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. You can 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.

3.4 Stopping Servers and Processes

Before running the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all 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 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 in Administering Oracle Fusion Middleware.

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

Step 1: Stop System Components

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

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

• (Windows) 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) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url

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

When prompted, enter your user name and password.

Step 3: Stop Oracle Identity Management Components

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

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

• (Windows) 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) DOMAIN_HOME/bin/stopWebLogic.sh

• (Windows) DOMAIN_HOME\bin\stopWebLogic.cmd

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

Note:

If external password storage is set up for the repository, then the server hosting the credential store should be up and running so that the work repository password can be retrieved during upgrade. For more information, see Setting Up External Password Storage in Oracle Fusion Middleware Administering Oracle Data Integrator.

Step 5: Stop Node Manager

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

Alternatively, after having set the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. For more information, see stopNodeManager in Oracle Fusion Middleware WLST Command Reference for WebLogic Server.

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

• Starting the Upgrade Assistant
  Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.
• Upgrading Product Schemas Using the Upgrade Assistant
  Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.
• Verifying the Schema Upgrade
  After completing all the upgrade steps, verify that the upgrade was successful by checking that the schema version in schema_version_registry has been properly updated.

3.5.1 Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). 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) ORACLE_HOME/oracle_common/upgrade/bin
   • (Windows) 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 Command-Line Parameters
  

3.5.1.1 Upgrade Assistant Command-Line Parameters

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

Table 3-6 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 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 will create log files and temporary files. The default locations are: (UNIX) ORACLE_HOME/oracle_common/upgrade/logs ORACLE_HOME/oracle_common/upgrade/temp (Windows) ORACLE_HOME\oracle_common\upgrade\logs ORACLE_HOME\oracle_common\upgrade\temp
-help	Optional	Displays all of the command-line options.

3.5.2 Upgrading Product Schemas Using the Upgrade Assistant

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

Notes

• If you are using external authentication, make sure that external authentication is changed to internal authentication.

• Edition-based redefinition (EBR) Users Only: Before upgrading an Edition-Based Redefinition (EBR) enabled schema, you must connect to the database server and create an edition on the database server for 12c. The new edition for 12c must be a child of your existing 11g edition. For more information on creating an edition on the server for redefinition, see Creating an Edition on the Server for Editions-Based Redefinition.

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

   Caution:

   Upgrade only those schemas that are used to support your 12c (12.2.1.2) 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.2).

   Click Next.

3. On the Available Components screen, select Oracle Data Integrator to upgrade the Master and Work Repository schema.
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 ODI Schema screen, specify the database connection details for each schema you are upgrading:

   • 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 ODI Options screen, select all of the options.

   Table 3-7 ODI Options

   Option	Description
   Replace Knowledge Modules with mandatory updates	This selection replaces standard Knowledge Modules with the newest version. Customizations to Oracle installed Knowledge Modules will be overwritten. But if you copy an installed Knowledge Module and customize the Knowledge Module, the customizations are not lost.
   Upgrade topology and security metadata	This selection replaces topology and security artifacts such as Technologies, Datatypes, Security Profiles and others with the newest version. Customizations of installed objects will be overwritten. If the object is copied and customized, then the customizations are not lost.

   For information on advanced upgrade options, see Advanced Upgrade Options.

7. On the ODI Supervisor screen, enter the Supervisor account credentials for the ODI repository to be upgraded.

   The installed Supervisor account is SUPERVISOR. Check with your ODI administrator for proper Supervisor account name and password, supplied when prompted by the Repository Creation Utility (RCU) when creating the Master and Work repositories for ODI.

   
   Description of the illustration GUID-7CDFA583-C70D-4F84-B6CC-783B36C85619-default.gif

   Note:

   When All Schemas Used by a Domain is selected, the Supervisor credentials for ODI are not pre-populated in the first instance as the domain does not contain them. If there are multiple ODI schemas, the Upgrade Assistant populates the user entry using the first set of credentials.
8. On the ODI Upgrade Key screen, use the auto-generated upgrade key to convert 11g IDs for repository objects into unique GUIDs, or specify your own key in the Upgrade Key field.

   Recommendations

   • Edit the auto-generated key to provide a meaningful key that is easier to remember.

   • Note down the upgrade key so that the same upgrade key can be provided when the ODI objects are imported from the XML file.

   ODI objects exist in ODI repositories and also in XML files exported from such repositories, which can be used, for example, in metadata exchanges between repositories. As such, there may be multiple copies of the same object, in different repositories and XML files.

   In 12c, ODI uses GUIDs instead of internal numeric IDs for object identification. In order to make sure the object identity is preserved after upgrade, a deterministic algorithm is applied to calculate GUIDs from the internal IDs for existing objects (note that for new objects, ODI will generate random GUIDs).

   Because the internal numeric IDs were not really universally unique, and were dependent on the repository ID to achieve a "pseudo-uniqueness," ODI allows the user to specify the upgrade key in order to reduce the likelihood of generating duplicated GUIDs. The upgrade key is fed into the GUID generation algorithm together with the internal numeric ID, to calculate the GUID.

   Thus, choosing different upgrade keys protects from getting duplicated GUIDs for objects that accidentally have the same internal numeric IDs. However, when multiple copies of the same object exists (in a repository or exported in XML files), the same GUID should be produced for all copies of the object. For this reason, the same upgrade key must be used for all upgrade operations involving the copies of that particular object.

   For example, suppose you have a project with 1001 as the ID in the 11g repository, and you also have a file exported from the same repository, which contains the same project (ID = 1001). In this case, the upgrade key used to upgrade the repository should be the same as the upgrade key used to import the XML file into the upgraded 12c repository. This ensures that the project object in the import file will be properly matched with the project object in the repository (when using one of SYNONYM import modes). However, if there is an 11g XML export file provided from a source containing objects created in another repository of which you have no information, there is a chance that it may contain a project that accidentally has the same internal ID (1001). In this case, to protect from erroneous object matching, which may corrupt the metadata, a different, custom upgrade key should be used when importing that file into the repository.

9. 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 Oracle Fusion Middleware Upgrading with the Upgrade Assistant Upgrade Guide 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.

10. On the Upgrade Summary screen, review the summary of the options you have selected for schema upgrade.
    Verify that the correct Source and Target Versions are listed for each schema you intend to upgrade.
    If you want to save these options to a response file to run the Upgrade Assistant again later in response (or silent) mode, click Save Response File and provide the location and name of the response file. A silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again.
    Click Upgrade to start the upgrade process.
11. 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.

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

3.5.3 Verifying the Schema Upgrade

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

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

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

In the query result:

• Check that the number in the VERSION column matches the latest version number for that schema. For example, verify that the schema version number is 12.2.1.2.0 . Note, however, that not all schema versions will be updated. Some schemas do not require an upgrade to this release and will retain their pre-upgrade version number.

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

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

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

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

3.6 Upgrading Standalone System Component Configurations

Use the Upgrade Assistant to upgrade the standalone agent’s component configurations when the agent is managed by OPMN. The standalone component configuration upgrade does not support upgrade of a standalone agent that is not managed by OPMN.

• Starting the Upgrade Assistant
  Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.
• Upgrading Standalone System Component Configurations Using the Upgrade Assistant
  Navigate through the screens in the Upgrade Assistant to upgrade standalone system component configurations.

3.6.1 Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). 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) ORACLE_HOME/oracle_common/upgrade/bin
   • (Windows) 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 Command-Line Parameters
  

3.6.1.1 Upgrade Assistant Command-Line Parameters

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

Table 3-8 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 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 will create log files and temporary files. The default locations are: (UNIX) ORACLE_HOME/oracle_common/upgrade/logs ORACLE_HOME/oracle_common/upgrade/temp (Windows) ORACLE_HOME\oracle_common\upgrade\logs ORACLE_HOME\oracle_common\upgrade\temp
-help	Optional	Displays all of the command-line options.

3.6.2 Upgrading Standalone System Component Configurations Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade standalone system component configurations.

Note:

Use the Upgrade Assistant to upgrade the standalone agent’s component configurations only when the agent is managed by OPMN. The standalone component configuration upgrade does not support upgrade of a standalone agent that is not managed by OPMN.

To upgrade standalone system 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 Standalone System Component Configurations, then select Create a new domain.

     Note:

     Beginning with 12c, standalone system components will have their own standalone domain. When you are upgrading your 11g standalone system components (which had no previous domain associations), you must first create a new standalone domain for your system components.
   • In the Domain Directory field, specify the full path of the domain you are creating. Oracle recommends that you locate your domain home in accordance with the directory structure summarized in Understanding the Recommended Directory Structure in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware, where the domain home is located outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or reinstall your software.

     Tip:

     The Update an existing domain option might be used in a situation where an upgrade was already performed and the domain created, either from another system component upgrade, or from a partial previous Oracle Data Integrator upgrade. These are examples of a situation where you would not need to create a new domain.

   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 Instance Directories screen, specify the location of one or more Oracle instance directories to be upgraded.
6. On the Node Manager screen, specify the credentials of the Node Manager that will be used to create a domain during the upgrade of standalone system components.
7. On the Examine screen, review the status of the Upgrade Assistant as it examines each standalone component, verifying that the standalone 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 Oracle Fusion Middleware Upgrading with the Upgrade Assistant Upgrade Guidefor 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.

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

10. If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard. The Post-Upgrade Actions window describes the manual tasks you must perform to make components functional in the new installation. This window appears only if a component has post-upgrade steps.

    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at ORACLE_HOME/oracle_common/upgrade/logs. Note If the upgrade fails you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

3.7 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) DOMAIN_HOME/bin/startWebLogic.sh

• (Windows) DOMAIN_HOME\bin\startWebLogic.cmd

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

Step 2: Start Node Manager

To start Node Manager, use the startNodeManager script:

• (UNIX) DOMAIN_HOME/bin/startNodeManager.sh

• (Windows) 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) DOMAIN_HOME/bin/startComponent.sh component_name

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

Step 4: Start the Managed Servers

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

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

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

When prompted, enter your user name and password.

Note:

The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.

Step 5: Start System Components

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

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

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

You can start system components in any order.