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) .
Follow the steps in the following topics to perform this upgrade:
Parent topic: Upgrading Oracle Data Integrator from 11g
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.
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: |
Required Install Oracle Data Integrator Standalone 12c (12.2.1) 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 |
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 Using the Upgrade Assistant to Upgrade 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) 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. |
Required Restart the servers and the 12c (12.2.1) instance. |
When the upgrade process is complete, restart the 12c (12.2.1) instance. |
Required Verify the upgrade. |
Ensure all of the upgraded components are working as expected before deleting your backups. |
Before beginning your upgrade, download the Oracle Data Integrator 12c (12.2.1) distribution on the target system and install it using Oracle Universal Installer.
When upgrading from 11g, you must use the Repository Creation Utility (RCU) to create the required 12c schemas before you begin the upgrade.
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.
Before running the Upgrade Assistant to upgrade your schemas and config, 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 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 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 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 WLST Command Reference for WebLogic Server.
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.
schema_version_registry
has been properly updated.Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.
oracle_common/upgrade/bin
directory:
ORACLE_HOME/oracle_common/upgrade/bin
ORACLE_HOME\oracle_common\upgrade\bin
For information about other parameters that you can specify on the command line, such as logging parameters, see:
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 |
---|---|---|
|
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 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). |
|
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 will create log files and temporary files. The default locations are: (UNIX) (Windows) |
|
Optional |
Displays all of the command line options. |
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 or 12c edition. For more information on creating an edition on the server for redefinition, see Creating an Edition on the Server for Editions-Based Redefinition in Planning an Upgrade of Oracle Fusion Middleware.
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.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.
Use the Upgrade Assistant to upgrade the 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.
Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.
oracle_common/upgrade/bin
directory:
ORACLE_HOME/oracle_common/upgrade/bin
ORACLE_HOME\oracle_common\upgrade\bin
For information about other parameters that you can specify on the command line, such as logging parameters, see:
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 |
---|---|---|
|
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 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). |
|
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 will create log files and temporary files. The default locations are: (UNIX) (Windows) |
|
Optional |
Displays all of the command line options. |
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.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.
After completing all the upgrade steps, verify that the upgrade was successful.
To verify the upgrade:
Start the Node Manager and standalone agent.
For more information, see Starting a Standalone Agent with Node Manager in Installing and Configuring Oracle Data Integrator.