This chapter describes the required pre-upgrade tasks for most upgrades. Product-specific pre-upgrade tasks are described in the other chapters of this book.
NOTE:
Depending on which Oracle SOA 11g products are being upgraded, you may need to perform additional pre-upgrade tasks.The tasks in this chapter describe the general pre-upgrade tasks required when upgrading to SOA Suite and BPM 12c (12.1.3). Review the product-specific upgrade chapters for each product that is being upgraded to determine if additional tasks are required for your upgrade.
This section includes pre-upgrade tasks that apply to any SOA, Business Process Management, or integrated products being upgraded to 12c (12.1.3). 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 |
|---|---|
| CAUTION: Oracle strongly recommends that you perform the upgrade on a cloned copy of your production environment before you upgrade your actual production environment. | Section 2.1.1, "Creating, Upgrading, and Testing a Development Copy of Your Production Environment" |
| Create a complete backup of your existing environment before you start any pre-upgrade procedures. | Section 2.1.2, "Backing Up Your Existing Oracle Fusion Middleware 11g Environment" |
| Back up the database that hosts the schema repository before you upgrade. | Section 2.1.3, "Backing Up Your Database" |
| Run 11g Purge scripts before starting the upgrade to reduce downtime during the upgrade. | Section 2.1.4, "Purging Unused Data" |
| Make sure that you have sufficient disk space | Section 2.1.5, "Ensuring You Have Sufficient Free Space" |
| Plan for using enhanced encryption. | Section 2.1.6, "Using Enhanced Encryption (AES 256)" |
| Backup your setDomainEnv file. | Section 2.1.7, "Maintaining Custom setDomainEnv Settings" |
| Upgrade to 64-bit operating system. | Section 2.1.8, "Upgrading from a 32-Bit to a 64-Bit Operating System" |
| Verify that your Oracle database is supported (version 11.2.0.3 or higher). | Section 2.1.9, "Upgrading and Preparing the Fusion Middleware Database" |
| Verify that your tablespaces are sized appropriately (insufficient sizing will result in a failed upgrade). | Section 2.1.10, "Adding Datafiles to the SOAINFRA and IAS_TEMP Tablespaces" |
| Complete the required pre-upgrade tasks for User Messaging Service (UMS) if you are upgrading UMS as part of your SOA Suite upgrade. | Section 2.1.11, "Upgrading 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. | Section 2.1.12, "Upgrading a SOA Domain with Oracle Service Bus (OSB)" |
| Upgrade your standalone Oracle HTTP Server (if necessary). | Section 2.1.13, "Upgrading a Standalone Oracle HTTP Server" |
| Reassociate any file-based policy stores to database-based stores. | Section 2.1.14, "Reassociating a File-Based Policy Store Before Upgrade" |
| Understand the schema requirements when using an Oracle Internet Directory-based security store. | Section 2.1.15, "Using an Oracle Internet Directory-based Security Store" |
| Install Oracle SOA Suite or Oracle Business Process Management Quick Start for Developers if you are upgrading custom applications | Section 2.1.16, "Upgrading Custom Applications Using Oracle JDeveloper 12c" |
| Stop all 11g FMW servers and processes before you launch the Upgrade Assistant. | Section 2.1.17, "Stopping Servers and Processes"
NOTE: All middle tier servers, such as soa_server1, MUST be stopped before starting the Upgrade Assistant. |
Oracle strongly recommends that you create a copy of your actual production environment, upgrade the cloned environment, verify that the upgraded components work as expected, and then (and only then) upgrade your production environment.
For more information on creating a test environment to use to roll out an upgrade, see "Moving from a Test to a Production Environment" in Administering Oracle Fusion Middleware.
Upgrades cannot be reversed. In most cases, if an error occurs, you must stop the upgrade and restore the entire environment from backup and begin the upgrade process from the beginning. Identifying potential upgrade issues in a development environment can eliminate unnecessary downtime.
Performing pre-upgrade testing on a cloned environment provides important data that can be applied to your overall production upgrade plan. Planning an Upgrade of Oracle Fusion Middleware provides detailed information on forming and executing a complete pre-upgrade plan.
Additional benefits of running an upgrade in a cloned production environment include the following:
Uncover and correct any upgrade issues.
Practice completing an end-to-end upgrade.
Understand the upgrade performance and how purge scripts can help.
Understand the time required to complete the upgrade.
Understand the database resource usage (such as temporary tablespace; PGA, etc).
Before you upgrade SOA 11g to SOA 12.1.3, you must back up your existing 11g environment.
If the upgrade fails you may have to restore your environment from the pre-upgrade backups. While planning your backup strategy, make sure that you include the following in your SOA backups:
Schema version registry table
All product-specific schemas
Domain and application directories
Inventory directory created by the installer
A complete list of backup considerations and procedures is described in "Backup and Recovery Strategies for Upgrade" in the Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware. Make sure that you have reviewed this information and executed a complete backup before starting the upgrade.
As with any database repository upgrade, standard procedure dictates that you back up your database before you upgrade to a new database version.
Note that you should also consider backing up the database again, after you have successfully upgraded to a new database version. This way, your backup will reflect the newly upgraded state of the database.
For more information on backing up your database, see "Backup Strategies for Database Upgrades" in Planning an Upgrade of Oracle Fusion Middleware.
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 Section 9.3, "Using Purge Scripts Before You Upgrade".For more information on using Auto Purge or purge scripts, see "Managing Database Growth" in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
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" in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
Before you begin the upgrade it is recommended that you secure sufficient free space to complete the upgrade.
F or a typical upgrade, the following is recommended:
At least 25% free table space
At least 800MB free temp space
The Java platform defines a set of APIs spanning major security areas, including cryptography, public key infrastructure, authentication, secure communication, and access control. These APIs allow developers to easily integrate security mechanisms into their application code.
Some of the security algorithms used in Fusion Middleware 12.1.3 require additional policy files for the JDK. If you plan to use enhanced encryption (such as AES 256), Oracle recommends that you apply these policy files to the JDK before you upgrade. For more information, see the following:
Java Cryptography Architecture Oracle Providers Documentation
If you do not apply these policy files to the JDK before you begin the upgrade, the upgrade can fail and you will have to restore the entire pre-upgrade environment and start the upgrade from the beginning.
Changes made to the setDomainEnv script - or any other startup script - before an upgrade will be overwritten by new, regenerated scripts during the domain reconfiguration process. Consider creating a separate file to store your domain customizations before you upgrade as described in "Maintaining Your Custom setDomainEnv Settings (Optional)".
Note:
If you are unable to create thesetUserOverrides script before an upgrade, you will need to reapply your settings as described in "Reapplying Customizations to setDomainEnv".If you are running a 32-bit operating system, then you must upgrade your 32-bit environment to a 64-bit software environment before you upgrade. Make sure to validate the migration to ensure all your Oracle Fusion Middleware 11g software is working properly on the 64-bit machine, and only then perform the upgrade to Oracle Fusion Middleware 12c.
For detailed instructions on how to upgrade your 32-bit system to 64-bit, see "Upgrading from a 32-Bit to a 64-Bit Operating System" in Planning an Upgrade of Oracle Fusion Middleware.
It is imperative that you understand the Oracle Database requirements for upgrading to Oracle SOA Suite and BPM 12.1.3, 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.1.3). Always refer to the latest database certification matrix for the most current information.
Note the following important changes for 12c (12.1.3):
As of 12c (12.1.3), the only supported database is Oracle. Oracle XE is not supported. For more information see "Upgrading and Preparing Your Oracle Databases for 12c (12.1.3)" in the Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.
This release of 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.
If NLS_LENGTH_SEMANTICS is set to CHAR, then the Upgrade Assistant will report the following exception:
JDBC SQLException - ErrorCode: 1450SQLState:72000 Message: ORA-01450: maximum key length (6398) exceeded
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.
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.1.3). For more information, see Section 2.5, "Preparing to Upgrade Schemas".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. Oracle recommends that you add more data files to the existing SOA database tablespace to prevent a failed upgrade.
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" in the Oracle Database Administrator's Guide.
CAUTION:
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.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.
For more information, see "Upgrading User Messaging Service" in Administering Oracle User Messaging Service.
If you are upgrading a SOA domain with Oracle Service Bus, you must preform several required pre-upgrade tasks. See Section 6.3, "Performing Pre-Upgrade Tasks for Oracle Service Bus (OSB)".
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 upgrade is performed as you are 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) refer to Upgrading a Standalone Oracle HTTP Server.
If you are using a file-based policy store in your existing 11g environment, you must reassociate to database-based policy store before you begin the upgrade process.
Refer to the following tasks for more information:
Create new 11g Oracle Platform Security Services (OPSS) and Audit Schemas (IAU) schemas in a supported Database using the 11g Repository Creation Utility.
For more information about creating 11g schemas, see "Obtaining and Running Repository Creation Utility" in the Oracle Fusion Middleware Repository Creation Utility User's Guide for 11g Release 1 (11.1.1.7.0).
If you are using a file-based policy store in your 11g environment, then reassociate the file-based store with the database-based repository and OPSS schema.
For information about reassociating a file-based policy store, see "Reassociating the OPSS Security Store" in the Oracle Fusion Middleware Application Security Guide in the 11g Release 1 (11.1.1.7.0) documentation library.
If you are using an Oracle Internet Directory (Oracle Internet Directory)-based security store in 11g, use the 12c Repository Creation Utility to create the new 12c OPSS schema. In the Upgrade Assistant, select the OPSS schema; the Upgrade Assistant upgrades the Oracle Internet Directory-based security store. You do not need to reassociate an Oracle Internet Directory-based security store before upgrade.
Note:
The 12c OPSS database schema is required only so you can reference the 12c schema during the reconfiguration of the domain. Your domain will continue to use the Oracle Internet Directory-based security store after the upgrade.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.
However, if you want to take advantage of new Oracle Application Development Framework (Oracle ADF) 12c (12.1.3) 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 (12.1.3) 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" in Installing SOA Suite and Business Process Management Quick Start for Developers.
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 do so may result in an incomplete or failed upgrade. Upgrades are performed completely 'offline'.
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.
Instructions for stopping an Oracle Fusion Middleware environment are provided in "Stopping an Oracle Fusion Middleware Environment" in Administering Oracle Fusion Middleware.
Before upgrading the OPSS security store, back it up so that it can be recovered in case the upgrade fails. For details about backing up the security store, see Backing Up and Recovering the OPSS Security Store.
The upgrade procedure varies depending on the type of security store you start from. The security store to be upgraded can be file-, Oracle Internet Directory-, or DB-based. Note the procedures vary according to the type of source audit data store (file- or DB-based).
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.1.3).
Before you can upgrade your existing SOA 11g components, you must first install an Oracle WebLogic Server and JRF using the 12c (12.1.3) 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.1.3) Infrastructure distribution installed before you can upgrade to SOA 12c (12.1.3). The only application server that Oracle Fusion Middleware 12c (12.1.3) 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.1.3).
For more information, see "Upgrading from a Previous Infrastructure 12c Release" in Upgrading to the Oracle Fusion Middleware Infrastructure.
If your 11g domain includes Oracle HTTP Server instances that are associated with the domain, you must install Oracle HTTP Server 12.1.3 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.1.3, see "Installing the Oracle HTTP Server Software" in the Oracle Fusion Middleware Installing and Configuring Oracle HTTP Server.
You must install the 12c (12.1.3) product distributions for each SOA 11g integrated component you will be upgrading.
Refer to the product-specific installation guides for more information:
Caution:
When installing the SOA 12c (12.1.3) 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.You must determine which of the 11g schemas will be upgraded and which schemas you will need to create prior to upgrade. This section describes how to prepare your schemas for an upgrade.
Section 2.5.1, "Using the Schema Version Registry to Identify Existing 11g Schemas"
Section 2.5.2, "Creating the Required Schemas Before You 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 Chapter 9, "Administering and Monitoring the Upgrade of SOA Instances".
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.1.3 must be at versions 11.1.1.7.x or 11.1.1.6.x. 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.1.3), see "Identifying Schemas that Can be Upgraded with the Upgrade Assistant" in Upgrading with the Upgrade Assistant.
After installing your 12.1.3.0.0 components, you will need to create the new 12c required schemas in a supported database certified for use with this release of Oracle Fusion Middleware. Table 2-1 describes which schemas should be created based on the upgrade:
Table 2-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.1.3. |
|
Business Process Monitoring (BPM) |
Schemas required for SOA Suite |
|
Business Activity Monitoring (BAM) |
Schemas required for SOA Suite And: WebLogic Services (_WLS) |
|
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 For more information, see Upgrading an OSB Domain (Without SOA) |
|
Application Integration Architecture Foundation Pack (AIAFP) |
Schemas required for SOA Suite |
|
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: