The Oracle Fusion Middleware Upgrade Assistant automates many upgrade tasks. This chapter describes how to use the Upgrade Assistant.
This chapter describes the following:
Section 1.2, "Verifying Your Database is Supported for Upgrade"
Section 1.3, "Using the Upgrade Assistant in the Overall 12c Upgrade Process"
Section 1.4, "Identifying Schemas that Can be Upgraded with the Upgrade Assistant"
Section 1.5, "Identifying Component Configurations to be Upgraded with the Upgrade Assistant"
Section 1.9, "Upgrading Oracle WebLogic Component Configurations"
Section 1.10, "Upgrading Standalone System Component Configurations"
Note:
Before starting the Upgrade Assistant, refer to Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware and your component-specific upgrade documentation for detailed information about the supported upgrade starting points, as well as the prerequisites and upgrade paths for specific installation types.The Oracle Fusion Middleware Upgrade Assistant is used to upgrade supported 11g and 12c component schemas, component configurations, and standalone system component configurations to Fusion Middleware 12c (12.1.3).
When you run the Upgrade Assistant from the oracle_common/upgrade/bin/ua directory of your Fusion Middleware 12c (12.1.3) installation, it performs the following tasks:
For schema upgrades, the Upgrade Assistant examines the current install directory and identifies the list of possible component schemas to be upgraded. It also determines the order of schema upgrade based on certain dependency information present.
The Administration server is offline during the configuration upgrade. The list of component configurations to upgrade are determined by reading the domain configuration in an offline manner.
The database that hosts the schemas used in Fusion Middleware must be supported. For more information, see "Verifying Your Database and Schemas are Ready for Upgrade" in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.
The Upgrade Assistant is used in conjunction with other Fusion Middleware tools and processes to complete an upgrade of supported 11g and 12c components to 12c (12.1.3) upgrade. Supported versions are described in Table 1-1.
The 11g to 12c upgrade process is very different from previous releases. To understand how the Upgrade Assistant and the other upgrade tools are used in the upgrade process, see "Understanding the 12c Upgrade Process" in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.
At a high level, the Upgrade Assistant is used twice during a typical upgrade. The general steps are as follows:
You will launch the Upgrade Assistant the first time to upgrade the available schemas to the latest version. Depending on which schemas you select to upgrade, you will be presented with a series of standard and schema-specific Upgrade Assistant screens.
If you are upgrading from 11g, you will need to create the Service Table schema for use in 12c (12.1.3). For more information on which schemas you will need to create for 12c, see "Creating Schemas Before You Upgrade" in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.
Once the schemas are upgraded, you will use the Reconfiguration Wizard to reconfigure the existing domain.
For more information on using the Reconfiguration Wizard, see "Reconfiguring WebLogic Domains" in Upgrading Oracle WebLogic Server.
After the domain has been reconfigured, you will use the Upgrade Assistant again to upgrade any component configurations.
The Upgrade Assistant identifies schemas for which an upgrade is available. You can upgrade multiple schemas in a single session of running the Upgrade Assistant.
When the schemas are created in your database, RCU creates and maintains a table called schema_version_registry. This table contains schema information such as version number, component name and ID, date of creation and modification, and custom prefix.
Note:
The Upgrade Assistant identifies all of the schemas that are available for an upgrade, but it allows you to select which schemas should be upgraded.If you determine that an upgrade is not needed for a schema, the schema_version_registry table will retain the schemas at their pre-upgrade version after the 12.1.3.0.0 upgrade. Table 1-1 shows what the pre- and post-upgrade version numbers will be when the schemas are selected for an upgrade.
To determine which of your 11g or 12.1.2 schemas can be upgraded to 12.1.3.0.0, execute the following:
If you are using an Oracle database, connect to the database as SYSTEM or as any user who has the Oracle DBA role and run the following from SQL*Plus to get the current version numbers. The following report is generated when saved to a SQL script, for example version.sql:
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 ;
If the number in the "VERSION" matches that mentioned in the table below, the STATUS column is 'VALID', and the schema is listed in Table 1-1, then the schema is supported for upgrade.
The component schemas listed in Table 1-1 (default names shown) can be upgraded to 12c (12.1.3.0.0) using this version of the Upgrade Assistant.
Note:
The Schema(s) column in Table 1-1 shows the default schema name format of prefix and schema name separated by an underscore (_) character. The default prefix isDEV, but you may have created new prefixes for your schemas while using the RCU.Notes About the Schemas That Need to Be Upgraded:
For most components, the only schema versions that are valid for updating are 11g Release 1 (11.1.1.6 or 11.1.1.7) or 12c (12.1.2). If your schemas are not at a supported version, then you must upgrade them before using the 12c (12.1.3) upgrade procedures.
Some components, such as Oracle Enterprise Data Quality and Oracle Golden Gate Veridata, support an upgrade from versions other than the standard Oracle Fusion Middleware supported versions. See Table 1-1 for more information on supported schems and starting points for these components.
Refer to your component-specific installation and upgrade documentation for additional information about the schemas that are required for your upgrade.
If you used a file-based policy store in 11g, then you must reassociate the file-based policy store with a database-based security store before running the Upgrade Assistant. For more information see "Reassociating a File-Based Policy Store Before Upgrade" in Oracle Fusion Middleware Upgrading to the Oracle Fusion Middleware Infrastructure.
If you used an OID-based policy store in 11g, make sure that you have created new OPSS schemas before upgrade.
Table 1-1 lists only the schemas for products that are available for upgrade in the Oracle Fusion Middleware 12c (12.1.3) release. Do not attempt to upgrade a domain that includes components that are not yet available for upgrade to 12c (12.1.3). For more information, see Oracle Fusion Middleware Understanding Interoperability and Compatibility.
Table 1-1 Oracle Component Schemas That Require an Upgrade
| Component Name | Schema(s) | Schema Version Before Upgrade | Schema Version After Upgrade | Dependencies and Additional Information |
|---|---|---|---|---|
|
AS Common Schemas |
||||
|
Audit ServicesFoot 1 |
|
11.1.1.6 11.1.1.7 12.1.2. |
12.1.3.0.0 |
No dependencies. Requires |
|
Metadata Services |
|
11.1.1.6. 11.1.1.7 12.1.2 |
12.1.3.0.0 |
No dependencies. Requires |
|
Platform Security ServicesFoot 2 |
|
11.1.1.6 11.1.1.7 12.1.2 |
12.1.3.0.0 |
The Requires |
|
Common Infrastructure Services (LocalSvcTbl) |
|
12.1.2 |
12.1.3.0.0 |
The 12.1.2.0.0 |
|
User Messaging Service |
|
11.1.1.6 11.1.1.7 12.1.2 |
12.1.3.0.0 |
When upgrading a system that is a new installation of 12.1.2 the schema name will be called |
|
WebLogic Diagnostic Framework |
|
11.1.1.6 11.1.1.7 |
12.1.2.0.0 |
|
|
Oracle Data Integrator |
||||
|
Data Integrator (Master and Work Repository) |
|
11.1.1.6 11.1.1.7 12.1.2 |
12.1.3.0.0 |
None. Requires |
|
Oracle SOA Suite |
||||
|
SOA Core ExtensionFoot 3 NOTE: In 11g SOA Core Extension was called the Application Integration Architecture Foundation Pack (AIAFP). AIAFP has been rebranded in 12c to SOA Core Extension. |
|
11.1.1.6 11.1.1.7 |
12.1.3.0.0 |
When the 11g schema is upgraded, the AIAFP schema is retained and a new 12c schema is created. After the upgrade, you have two sets of AIAFP schemas as the old one is not deleted. |
|
SOA Infrastructure |
|
11.1.1.6 11.1.1.7 |
12.1.3.0.0 |
|
|
Oracle Enterprise Data Quality |
||||
|
Enterprise Data Quality |
|
11.1.1.7.3 |
12.1.3.0.0 |
|
|
Oracle Golden Gate Monitor |
||||
|
Golden Gate Monitor |
|
11.1.1.7 |
12.1.3.0.0 |
|
|
Oracle Golden Gate Veridata |
||||
|
Veridata |
|
11.2.1 |
12.1.3.0.0 |
|
Footnote 1 When upgrading _IAU from 11g starting points, the Upgrade Assistant will update two auxilary schemas, IAU_APPEND and IAU_VIEWER and add them to the schema_version_registry for 12.1.3.0.0. These schemas were not part of the 11.1.1.6 or 11.1.1.7 schema_version_registry table.
Footnote 2 As of release 11.1.1.7, OPSS audit data is stored in IAU common tables instead of the JPS table. When upgrading _OPSS schemas to 12.1.3.0.0 from 11.1.1.6, any existing data in the JPS table can remain unchanged for reporting or auditing purposes, and there is no need to upgrade JPS table with extra columns.
Footnote 3 In 11g, the AIAFP schema was a separate, non-RCU schema, but in 12c it is now part of RCU and is part of the SOAINFRA schema. When the 11g schema is upgraded, the AIAFP schema is retained and a new 12c schema is created. After the upgrade, you have two sets of AIAFP schemas because the old one is not deleted. This is specific to 12.1.3 release.
When you use the Upgrade Assistant to upgrade your component configurations, it automatically determines the list of components that are configured and can be upgraded to the latest version. After you run the Upgrade Assistant for schema upgrades, you will use the Reconfiguration Wizard to reconfigure your domain. The Upgrade Assistant is used again, after the reconfiguration, to upgrade any remaining configuration properties.
You can use the Upgrade Assistant to upgrade the following component configurations to 12c (12.1.3.0.0):
Oracle HTTP Server
Oracle Web Services Manager
Oracle Data Integrator
Oracle SOA Core Extension
JRF Infrastructure
Oracle MapViewer
Oracle Golden Gate Veridata
Oracle User Messaging Service
Caution:
If you have existing Fusion Middleware 11g components that are not available in the 12.1.3.0.0 upgrade, and you want to continue to use them with your upgraded components, review Oracle Fusion Middleware Understanding Interoperability and Compatibility before you upgrade. You will need to determine if an upgrade will cause any incompatibility issues with your Fusion Middleware 11g components.This section describes the procedures you must perform before you run the Upgrade Assistant:
The Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware guide provides detailed information on the tasks that you will need to perform before you begin the upgrade process.
Review "Developing an Upgrade Strategy" to make sure that all pre-upgrade requirements have been met.
The Upgrade Assistant is included in the 12c (12.1.3) Fusion Middleware software Infrastructure distribution. The 12.1.3 product distributions must be installed before executing your upgrade. For more information on 12c (12.1.3) installations, including the standard 12c (12.1.3) installation topologies, see Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware. This guide also discusses additional prerequisites and links to component-specific Installation Guides.
You can also see a complete list of Installation Guides in the Oracle Fusion Middleware 12c (12.1.3) documentation library.
If your starting point is 11g, after installing your 12.1.3.0.0 components, you will need to create the new 12c schemas, such as the new Service Table schema (prefix_STB) in a supported database certified for use with this release of Oracle Fusion Middleware.
For more information on determining which schemas should be created for your upgrade, see "Creating Schemas Before You Upgrade" in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.
Note:
Before upgrading an EBR-enabled schema from Fusion Middleware 11g Release 1 (11.1.1.6 or 11.1.1.7) or 12c (12.1.2), you must first connect to the database server and create an edition on the database server for 12c (12.1.3). The new edition for 12.1.3 must be a child of your 11.1.1.6, 11.1.1.7 or 12.1.2 edition.For more information on creating an edition on the server for edition-based redefinition, see "Creating an Edition on the Server for Edition-Based Redefinition" in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.
Before running Upgrade Assistant to upgrade your schemas, shut down all Oracle Fusion Middleware Managed Servers, Administration Servers, and system components (such as OHS) that may be using the schemas you want to upgrade. The databases that contain Fusion Middleware database schemas must be quiesced before running Upgrade Assistant. You can either shutdown and restart the database server, or ensure that there are no other database users operating on the same database instance that will be upgraded by Upgrade Assistant. Failure to do so may result in an incomplete or failed upgrade.
If you are running Node Manager, you should also stop 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 Oracle Fusion Middleware Administering Oracle Fusion Middleware.
Upgrade Assistant will be installed by the 12c (12.1.3) version of the Oracle Universal Installer (OUI) into the oracle_common area of the Fusion Middleware home in the oracle_common/upgrade/bin directory.
To start the Upgrade Assistant using the graphical user interface, navigate to the oracle_common directory of your the Oracle home where your Middleware products are installed. For information on launching the Upgrade Assistant from the command line with arguments, see Using the Upgrade Assistant Command-Line Interface.
Note:
Oracle recommends that you successfully complete the upgrade of schemas and component configurations for a single domain before beginning the upgrade of another domain.Change directory to ORACLE_HOME/oracle_common/upgrade/bin on Unix operating systems or ORACLE_HOME\oracle_common\upgrade\bin on Windows operating systems.
Enter the following command to start the Upgrade Assistant.
On UNIX operating systems:
./ua
On Windows operating systems:
ua.bat
The Upgrade Assistant displays the Welcome screen. Provide the required information in each of the Upgrade Assistant screens. The screens you see will vary depending on the type of upgrade you select. The sections below describe the upgrade options and the information you will need to provide.
If you are running the Upgrade Assistant from an Oracle home that contains components with any schemas listed in Table 1-1, then the Schemas upgrade option is shown. The Upgrade Assistant will only list components that are candidates for schema upgrade. You can select which schemas to upgrade from the component list.
The Upgrade Assistant will display the following screens when upgrading schemas:
Table 1-2 Upgrade Assistant Screens: Upgrading Schemas
| Screen | When Screen Appears | Description |
|---|---|---|
|
Always. |
This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. |
|
|
When Schemas is selected as the upgrade type, the screen name is Schemas. |
Use this screen to select the option to upgrade schemas for your installed components. |
|
|
Always. |
This screen provides a list of installed Oracle Fusion Middleware components that have schemas that can be upgraded. When you select a component, the schemas and any dependencies are automatically selected. |
|
|
Always. |
This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade. You must check the boxes before you can continue. |
|
|
Only when Schemas is selected as the upgrade type. |
Use this screen to enter information required to connect to the selected schema and the database that hosts the schema. The screen name changes based on the type of schema selected ("MDS Schema", for example). Note that since the component ID or schema name is changed for UCSUMS schema in 12.1.2, the UA does not automatically recognize the possible schemas and display them in a drop-down list. The user has to manually enter the name in a text field. The name can be either prefix_ |
|
|
Only when upgrading OPSS or Audit schemas. |
Use this screen to specify the existing Oracle WebLogic 11g domain directory or 12c (if the starting point is 12.1.2)domain directory for The Upgrade Assistant requires the 11g domain location to access the |
|
|
Always. |
This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. |
|
|
Always. |
Use this screen to review a summary of the options you have selected and to start the upgrade process. |
|
|
Always. |
This screen shows the status of the upgrade process. |
|
|
Or |
Always. |
The upgrade was successful. The Post-Upgrade Actions window describes the manual tasks you must perform to make the component function in the new installation. Or: The upgrade failed for the specified component(s) and Upgrade Assistant will have to be restarted. Note: UA logs are populated at |
Note:
For SOA Suite and BPM Upgrades:The upgrade of active and closed SOA instance data to 12c (12.1.3) happens automatically as part of the SOA schema upgrade process with the Upgrade Assistant. For more information, see "Administering and Monitoring the Upgrade of SOA Instance Data" in Fusion Middleware Upgrading SOA Suite and Business Process Management
If you are running the Upgrade Assistant from an Oracle home that contains managed WebLogic domain components, then the WebLogic Component Configuration upgrade option is available.
Note:
After upgrading the component schemas, you must run the Reconfiguration Wizard to reconfigure the domain. For more information, see "Reconfiguring an Oracle WebLogic Domain with the Reconfiguration Wizard". After the domain reconfiguration, use the Upgrade Assistant again to upgrade the component configurations as described in Upgrading Oracle WebLogic Component Configurations.The Upgrade Assistant will display the following screens when upgrading a WebLogic component configurations, such as Oracle Web Services Manager (OWSM).
Table 1-3 Upgrade Assistant Screens: Upgrading Oracle WebLogic Component Configurations
| Screen | When Screen Appears | Description |
|---|---|---|
|
Always. |
This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. |
|
|
When WebLogic Component Configurations is selected as the upgrade type, the screen name is WebLogic Components. |
Select the WebLogic Component Configurations option to upgrade component configurations for a managed WebLogic Server domain. Configuration upgrades are offline in 12.1.3. You must enter the domain directory for the domain that you are upgrading now. |
|
|
Only when AIAFP 11g is installed on the domain which is being upgraded. |
If your domain has AIAFP 11g then you need to provide AIA 11g home path and the 11g AIAFP instance name. |
|
|
When the domain being upgraded is a cluster domain and AIAFP 11g is installed on the domain. |
If AIAFP 11g is installed on a cluster you need to provide a shared location path accessible to all the nodes of the cluster. |
|
|
Only when upgrading Oracle Web Services Manager (OWSM) configuration in a cross-domain topology. |
If your enviroment has multiple WebLogic Server domains, but the OWSM Policy Manager is only in one WLS domain and the OWSM agents are on other domains, you will use this screen to enter the credentials for the WebLogic Administration Server domain where the Oracle Web Services Manager (OWSM) Policy Manager is deployed. |
|
|
Always. |
This screen provides a list of components that will be included in the WebLogic domain's component configuration upgrade. The name of the domain is provided along with the list of components located within the domain. |
|
|
Always. |
This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade. You must check the boxes before you can continue. |
|
|
When there are remote managed servers hosting UMS 11g configuration files, that is, when the required configuration files are not locally accessible at the Administration Server. |
This screen specifies the login credentials of the remote managed servers hosting your UMS 11g configuration files. The Upgrade Assistant automatically copies remote configuration files if all necessary prerequisites are met and the required login information is provided. |
|
|
Always. |
This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. |
|
|
Always. |
Use this screen to review a summary of the options you have selected and to start the upgrade process. |
|
|
Always. |
This screen shows the status of the upgrade process. |
|
|
Or |
Always. |
The upgrade was successful. The Post-Upgrade Actions window describes the manual tasks you must perform to make the component function in the new installation. Or: The upgrade failed for the specified component(s) and Upgrade Assistant will have to be restarted. |
If you are running the Upgrade Assistant from an Oracle home that contains only standalone system components, such as Oracle Data Integrator or Oracle HTTP Server (OHS), then the Standalone Components upgrade option is shown. Standalone components are not associated with a managed WebLogic domain.
Note:
As of 12c (12.1.2), the Upgrade Assistant will create a separate standalone domain for your system components. This domain can be managed by Node Manager, but has no Administration Servers. For more information on using the new system component domain, see Oracle Fusion Middleware Understanding Oracle Fusion Middleware.The Upgrade Assistant will display the following screens when upgrading a standalone system component, such as Oracle HTTP Server (OHS), for example. The screens that you use will vary depending on the system components you are upgrading and the options you select. See your component-specific upgrade documenation for information on the screens related to your specific component upgrade.
Table 1-4 Upgrade Assistant Screens: Upgrading Standalone System Component Configurations
| Screen | When Screen Appears | Description |
|---|---|---|
|
Always. |
This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. |
|
|
Only when you have a standalone system component to upgrade and no schemas available to upgrade. |
Beginning with 12c (12.1.2), standalone system components will have their own standalone domain. Use this screen to specify the domain option you want to apply to the standalone system component you are upgrading. You will have two options:
|
|
|
Always. |
Lists the standalone system components that are available to upgrade. |
|
|
Always. |
This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade. You must check the boxes before you can continue. |
|
|
Always. |
When upgrading system components, such as OHS, you must provide the directory locations of the 11g instances that will be used as a starting point for creating new 12c component instances. |
|
|
Only when Create a New Domain is selected. |
Use this screen to specify the credentials of the Node Manager that will be used to create a domain during the upgrade of standalone system components. |
|
|
Always. |
This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. |
|
|
Always. |
Use this screen to review a summary of the options you have selected and to start the upgrade process. |
|
|
Always. |
This screen shows the status of the upgrade process. |
|
|
Or |
Always. |
The upgrade was successful. The Post-Upgrade Actions window describes the manual tasks you must perform to make the component function in the new installation. Or: The upgrade failed for the specified component(s) and Upgrade Assistant will have to be restarted. |
This section contains information about basic tasks performed after the 12.1.3.0.0 upgrade is complete. Some of the tasks may not apply to your environment, as you may not be upgrading the products listed.
Always refer to your component-specific upgrade documentation for more information on post-upgrade procedures.
Note:
You should be able to successfully complete the tasks described in this section after an upgrade. If you are unable to complete one or more of these tasks in your newly upgraded environment, see Troubleshooting Your Upgrade.Table 1-5 lists some common administration tasks you will likely want to perform on your newly upgraded domain.
Note:
The administrative tasks in the table below are optional. Only perform those tasks that apply to your upgraded environment.Table 1-5 Basic Post-Upgrade Administration Tasks
| Task | Description | More Information |
|---|---|---|
|
Starting and stopping products and servers |
Learn how to start and stop Oracle Fusion Middleware, including the Administration Server, Managed Servers, and components. Performing these tasks will validate that the upgrade was successful. |
"Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administering Oracle Fusion Middleware. |
|
Starting and stopping upgraded applications. |
Learn how to start your upgraded applications in the new 12.1.3 environment to verify they are working as expected. |
"Starting and Stopping Applications" in Oracle Fusion Middleware Administering Oracle Fusion Middleware. |
|
Configuring Secure Sockets Layer (SSL) |
Learn how to set up secure communications among between Oracle Fusion Middleware components using SSL. |
"Configuring SSL in Oracle Fusion Middleware" in Oracle Fusion Middleware Administering Oracle Fusion Middleware. |
|
Deploying Applications |
Learn how to deploy your applications to Oracle Fusion Middleware. |
"Deploying Applications" part in Oracle Fusion Middleware Administering Oracle Fusion Middleware. |
|
Monitoring Oracle Fusion Middleware |
Learn how to keep track of the status of Oracle Fusion Middleware components. |
"Monitoring Oracle Fusion Middleware" in Oracle Fusion Middleware Administering Oracle Fusion Middleware. |
|
Adding a Web Tier front-end to your WebLogic domain |
Oracle Web Tier hosts Web pages (static and dynamic), provides security and high performance along with built-in clustering, load balancing, and failover features. In particular, the Web Tier contains Oracle HTTP Server. |
Oracle Fusion Middleware Installing and Configuring Oracle HTTP Server. |
|
Tuning and configuring Coherence for your topology. |
The standard installation topology includes a Coherence cluster that contains storage-enabled Managed Coherence Servers. This configuration is a good starting point for using Coherence, but depending upon your specific requirements, consider tuning and reconfiguring Coherence to improve performance in a production environment. |
For information about Coherence clusters, see "Configuring and Managing Coherence Clusters" in Administering Clusters for Oracle WebLogic Server. For information about tuning Coherence, see Administering Oracle Coherence. For information about storing HTTP session data in Coherence, see "Using Coherence*Web with WebLogic Server" in Administering HTTP Session Management with Oracle Coherence*Web. For more information about creating and deploying Coherence applications, see Developing Oracle Coherence Applications for Oracle WebLogic Server. |
You can use the following SQL command to verify that the schema version in schema_version_registry has been properly upgraded:
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 ;
All the numbers in the "VERSION" column should be the versions specified in the "Schema Version After Upgrade" column of Table 1-1, that is 12.1.3.0.0.
In the query results, the STATUS field will be either "UPGRADING" or "UPGRADED" during the schema patching operation, and will become "VALID" when the operation is finished.
If the status appears as "INVALID" then the schema upgrade failed. You should examine the logs files to determine the reason for the failure.
If you are using an Oracle database, you should recompile database objects after running the Upgrade Assistant by connecting to the database as SYS and running the following from SQL*Plus:
SQL>@/rdbms/admin/utlrp.sql
This will compile the database objects that were upgraded by Upgrade Assistant.
Then issue the following query to ensure there are no longer any invalid database objects:
SELECT owner, object_name FROM all_objects WHERE status='INVALID';
None of the database objects for the upgraded schema should be invalid at this point. If there are any, run the utlrp.sql command again and check again. If the problem persists, you should file a service request.