Note:
Depending on which Oracle SOA 11g products are being upgraded, you may need to perform additional pre-upgrade tasks.
The tasks describe the general pre-upgrade tasks required when upgrading to SOA Suite and BPM 12c (12.2.1). Review the product-specific upgrade chapters for each product that is being upgraded to determine if additional tasks are required for your upgrade.
In addition to the Oracle Fusion Middleware pre-upgrade requirements, you may also be required to complete additional SOA-specific upgrade tasks depending on your pre-upgrade environment.
This section includes pre-upgrade tasks that apply to any SOA, Business Process Management, or integrated products being upgraded to 12c (12.2.1). Perform only those tasks that apply to your environment.
Caution:
Failure to properly prepare for an upgrade may lead to unrecoverable errors and upgrade failures. Make sure that you have completed ALL applicable pre-upgrade tasks before beginning the upgrade.
The general pre-upgrade tasks include the following:
| Pre-Upgrade Task | More Information |
|---|---|
|
Complete all general pre-upgrade tasks described in the Oracle Fusion Middleware 12c Upgrade Checklist (Required) CAUTION: DO NOT continue with the upgrade until this task has been completed. |
|
|
Run 11g Purge scripts before starting the upgrade to reduce downtime during the upgrade. |
|
|
Understand the Oracle Database requirements for upgrading to Oracle SOA Suite and BPM 12.2.1 |
Upgrading and Preparing the Fusion Middleware Database for a SOA Suite Upgrade |
|
Verify that your tablespaces are sized appropriately (insufficient sizing will result in a failed upgrade). |
|
| SOA Composer Users Only: Note that uncommitted changes are not available after upgrade. | Committing SOA Composer Changes Before Upgrade |
|
Complete the required pre-upgrade tasks for User Messaging Service (UMS) if you are upgrading UMS as part of your SOA Suite upgrade. |
Performing pre-Upgrade Tasks for User Messaging Service (UMS) |
|
Complete the required pre-upgrade tasks for Oracle Service Bus (OSB) if you are upgrading OSB as part of your SOA Suite upgrade. |
|
|
Upgrade your standalone Oracle HTTP Server (if necessary). |
|
|
Install Oracle SOA Suite or Oracle Business Process Management Quick Start for Developers if you are upgrading custom applications |
|
|
Stop all 11g FMW servers and processes before you launch the Upgrade Assistant. |
Stopping SOA Servers and Processes NOTE: All middle tier servers, such as soa_server1, MUST be stopped before starting the Upgrade Assistant. |
Purging unused data before an upgrade can optimize the upgrade process.
Purging unused data before an upgrade can optimize the upgrade process by reducing the number of instances, fault alerts, or adapter reports that will be upgraded to the new 12c deployment. Purging your closed instances can greatly improve the duration of the upgrade. Note, however, that if you purge your closed instances, you will not be able to view or report on them using Enterprise Manager 12c.
Caution:
Do not start the Upgrade Assistant while the purge scripts are running. Wait until the purge is complete before starting the upgrade process. The upgrade will fail if the purge scripts are running while using the Upgrade Assistant to upgrade your schemas. For more information on using purge scripts with the Upgrade Assistant, see Using Purge Scripts Before You Upgrade.
For more information on using Auto Purge or purge scripts, see Managing Database Growth..
Note:
If a large amount of data needs to be purged, consider partitioning tables or employing other data optimization strategies. Using the scripts to remove large amounts of data may impact performance.
For more information, see Developing a Purging and Partitioning Methodology" and Developing a Database Growth Management Strategy.
You must have a supported database configured with the required schemas before you can run Fusion Middleware 12c (12.2.1).
It is imperative that you understand the Oracle Database requirements for upgrading to Oracle SOA Suite and BPM 12.2.1, and ensure that the database hosting Oracle Fusion Middleware is supported and has sufficient space to perform an upgrade. You must have a supported database configured with the required schemas before you can run Fusion Middleware 12c (12.2.1). Always refer to the latest database certification matrix for the most current information.
Verifying database requirements is part of the pre-upgrade checklist for Oracle Fusion Middleware 12c. If you have not reviewed these requirements, see "Upgrading and Preparing Your Oracle Databases for 12c (12.2.1)" in Planning an Upgrade of Oracle Fusion Middleware.
Note:
In 11g it was possible to run Oracle Service Bus without a database, as the SOA schema was not required. In 12c, however, you must have a supported database configured with the required SOA schemas before you can run OSB 12c (12.2.1).
For more information, see Preparing to Upgrade SOA Schemas.
Oracle recommends that you add more data files to the existing SOA database tablespace to prevent a failed upgrade.
While important for all tablespaces, it is especially important to make sure that the 11g SOAINFRA tablespace and IAS_TEMP tablespace are sized for a successful upgrade.
Note:
Once a database schema upgrade has failed due to a sizing error, you cannot simply add more disk space and retry the upgrade. The schemas have been left in an inconsistent state and may have been marked "INVALID". You cannot recover from this error without restoring the original, pre-upgrade environment from backups.
Two sample commands are provided below. Size the files according to your own use case scenarios.
To add datafiles to SOAINFRA tablespace:
Connect to the database as sysdba and run the following command:
alter tablespace <PREFIX>_SOAINFRA add datafile '<DB_HOME>/oradata/orcl/<New_SoaInfra_DBF_FileName>' size 1000M autoextend on next 30M maxsize unlimited; commit;
To add tempfiles to IAS_TEMP tablespace:
Connect to the database as sysdba and run the following command:
alter tablespace PREFIX_IAS_TEMP add tempfile '<DB_HOME>/oradata/orcl/<New_iastemp_dbf_filename>' size 1000M autoextend on next 30M maxsize unlimited; commit;
For more information on sizing your tablespaces before upgrade, see Creating Datafiles and Adding Datafiles to a Tablespace.
Complete the required pre-upgrade tasks for User Messaging Service (UMS) if you are upgrading UMS as part of your SOA Suite upgrade.
If you are Upgrading User Messaging Service from 11g to 12c, you may need to perform additional pre-upgrade tasks such as manually copying the configuration files from the managed server to the Admin server. If you are upgrading UMS from a previous 12c release, then you will not have to perform this task again.
For more information, see Upgrading User Messaging Service.
You must complete the required pre-upgrade tasks for Oracle Service Bus (OSB) if you are upgrading OSB as part of your SOA Suite upgrade.
If you are upgrading a SOA domain with Oracle Service Bus, you must preform several required pre-upgrade tasks. See Performing Pre-Upgrade Tasks for Oracle Service Bus (OSB).
If you are upgrading a standalone Oracle HTTP Server, then you should follow the instructions in Upgrading Oracle HTTP Server.
This guide explains how to upgrade Oracle HTTP Server 11g instances that have been configured so they are "associated with" an Oracle WebLogic Server domain. The HTTP server upgrade is performed automatically when upgrading the domain to which the Oracle HTTP Server has been associated.
To upgrade a standalone Oracle HTTP Server instance (one that is not associated with an 11g domain) or to upgrade the HTTP server at another time, refer to Upgrading Oracle HTTP Server.
If you have deployed custom applications to a SOA 11g domain, then the application deployments should function as they did in Oracle Fusion Middleware 11g after the upgrade procedure is complete.
If you want to take advantage of new Oracle 12c features, download and install the Oracle SOA Suite or Oracle Business Process Management Quick Start for Developers.
The Quick Start for Developers distributions provide Oracle JDeveloper 12c users with the required extensions for developing Oracle SOA Suite and Oracle Business Process Management applications.
For more information, see Installing Oracle SOA Suite Quick Start for Developers.
Note:
Oracle QuickStart is required if you want to use new Oracle SOA 12c features.Before running Upgrade Assistant, you must shut down ALL Oracle Fusion Middleware Managed Servers, Administration Servers, and system components (such as OHS) that may be using the schemas or configurations you want to update.
Failure to shut down servers and processes may result in an incomplete or failed upgrade.
If you are running Node Manager, you should also stop the Node Manager. You can do this by closing the console window in which Node Manager is running, or by using the stopNodeManager WLST command.
Stop SOA servers and processes in this order:
Business Activity Monitoring (BAM) Managed Server
Oracle Service Bus (OSB) Managed Server
Service-Oriented Architecture (SOA) Managed Server
Oracle Web Services Manager (OWSM) Managed Server
Administration Servers
Node Managers
Webtier (including the Oracle HTTP Server)
Instructions for stopping an Oracle Fusion Middleware environment are provided in Stopping an Oracle Fusion Middleware Environment.
If you do not commit or rollback your changes to the SOA Composer sandbox before you upgrade, your changes may not be propagated to the new environment.
Before you start the upgrade, make sure that you have committed or rolled back any changes that you do or do not want propagated to the upgraded environment.
Install all of the required 12c distributions in a new Oracle home before upgrading to Oracle SOA Suite and Business Process Management 12c.
Oracle SOA Suite and Business Process Management and the integrated SOA components require the Fusion Middleware Infrastructure and Oracle HTTP Server (if applicable). These distributions must be installed before you install and configure Oracle SOA Suite and BPM 12c (12.2.1).
For more information, see Installing Oracle Fusion Middleware Infrastructure.
Before you can upgrade your existing SOA 11g components, you must first install an Oracle WebLogic Server and JRF using the 12c (12.2.1) Infrastructure distribution.
See Installing and Configuring the Oracle Fusion Middleware Infrastructure for detailed instructions.
Caution:
When installing the Infrastructure distributions, do not use the Configuration Wizard to configure the domain. You will use the new Reconfiguration Wizard to configure the 11g domain during the upgrade process.
Note:
You must have the 12c (12.2.1) Infrastructure distribution installed before you can upgrade to SOA 12c (12.2.1). The only application server that Oracle Fusion Middleware 12c (12.2.1) supports is the Oracle WebLogic Server.
If you previously installed and configured the Infrastructure components using the 12c (12.1.2) release, you must first upgrade to Infrastructure 12c (12.2.1).
For more information, see Upgrading from a Previous Infrastructure 12c Release.
If your 11g domain includes Oracle HTTP Server instances that are associated with the domain, you must install Oracle HTTP Server 12.2.1 on the following machines:
On machines where 11g Oracle HTTP Server instances are running
On the machine where Administration Server is running
For more information about installing Oracle HTTP Server 12.2.1, see Installing the Oracle HTTP Server Software.
You must install the 12c product distributions for each SOA integrated component you will be upgrading.
Before you upgrade SOA to this release, you must first install all of the integrated component distributions for the components you will be upgrading. Install only those distributions that will be used in your upgraded environment.
Refer to the product-specific installation guides for more information:
Caution:
When installing the SOA 12c distributions, do not use the Configuration Wizard to configure the domain. You will use the new Reconfiguration Wizard to configure the existing 11g or 12c domain during the upgrade process.
It is important that you understand how to prepare your schemas for an upgrade before you start the upgrade process.
You must determine which of the schemas will be upgraded and which schemas you will need to create prior to upgrade. .
Note:
As part of the schema upgrade, all active and closed instances will be automatically upgraded. You will not lose your active or "in flight" 11g work flow instances during the upgrade.
If you do not want to upgrade instances, you must prevent the instance upgrade before you start the Upgrade Assistant.
For more information, See Administering and Monitoring the Upgrade of SOA Instances .
Before you upgrade, review the Oracle Fusion Middleware 11g schemas that are already installed in your database.
If you used the Repository Creation Utility (RCU) to create your 11g schemas, then you can connect to the database as SYSTEM, or as any other database user with DBA privileges, and use the following SQL command to see a list of the Oracle Fusion Middleware 11g schemas that are already installed in your database:
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 ;
The schemas that can be upgraded to 12.2.1 must be at versions 11.1.1.6.x or higher. You can use this list to review your domain schemas and to help you determine which schemas to create and which schemas you need to upgrade.
For a complete list of schemas that are available for upgrade to Oracle Fusion Middleware 12c (12.2.1), see Identifying Schemas that Can be Upgraded with the Upgrade Assistant.
You may need to create the new 12c required schemas in a supported database before you can upgrade.
Note:
If you are upgrading from a previous 12c release, you do not have to create new schemas before upgrading. For information on upgrading from a previous 12c release, see Upgrading Oracle SOA Suite and Business Process Management from a Previous 12c ReleaseTable 3-1 Required Schemas for SOA and SOA integrated products
| If you are upgrading... | Create these 12c schemas before you upgrade... |
|---|---|
|
SOA Suite (SOA) |
Service Table (_STB) Audit Services (_IAU) NOTE: If you created a 12.1.2 version of the _STB schema, you will have to upgrade it to 12.2.1. |
|
Business Process Monitoring (BPM) |
Schemas required for SOA Suite |
|
Business Activity Monitoring (BAM) |
Schemas required for SOA Suite And: WebLogic Services (_WLS) |
| Managed File Transfer (MFT) | Schemas required for SOA Suite |
|
Oracle Service Bus (OSB) |
SOA Infrastructure (_SOAINFRA) Service Table (_STB) User Messaging (_UMS) NOTE: It is possible to install Oracle Service Bus without running Oracle SOA, but you must create the _SOAINFRA and _STB schemas. For more information, see Upgrading an OSB Domain (Without SOA) |
|
User Messaging Service (UMS) |
Schemas required for SOA Suite |
For more information, see the following sections of the Upgrading to the Oracle Fusion Middleware Infrastructure:
Note:
Oracle Fusion Middleware only supports schemas in a byte-mode database. The nls_length_semantics initialization parameter, on the database where the schemas reside, must be set to BYTE; setting this parameter to CHAR is not supported.
To check the values of this parameter using SQL*Plus, you can use the show parameters command:
prompt> sqlplus "sys/<password> as sysdba"SQL> show parameters nls_length_semantics
Replace <password> with the actual password for the SYS user.
Alternatively, you can check the values by querying the V$PARAMETER view:
prompt> sqlplus "sys/password as sysdba"SQL> select name,value from v$parameter;
For more information, refer to you database administration documentation.