Make sure that the databases that are hosting your schemas are at supported versions. You cannot perform the upgrade on unsupported databases.
Note:
When upgrading to 12c (12.2.1.1) your existing database must be used for the upgrade. Do not create a new database.
SYSTEM.SCHEMA_VERSION_REGISTRY$ table.Many Oracle Fusion Middleware products require database schemas prior to domain configuration.
To find a certified database for your operating system, see the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.
To make sure your database is properly configured for schema creation, see "Verifying Requirements for Oracle Repository Creation Utility" in the Oracle Fusion Middleware System Requirements and Specifications document.
Note:
Only a certified database can be used for the Oracle Fusion Middleware Infrastructure standard installation topology.
The Oracle Platform Security Services (OPSS) schema is not supported on third-party databases for this release.
It is important that you review the very latest information on certified databases for Oracle Fusion Middleware before proceeding with your database upgrade. For more information, see the Certification Matrix for 12c (12.2.1.1).
The certification matrix and system requirements documents should be used in conjunction with each other to verify that your environment meets the necessary requirements for installation. The Oracle Fusion Middleware 12c software requirements included in this guide were accurate at the time this manual was published.
Note the following important changes for 12c:
Oracle XE is not supported.
Oracle Database Users: 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:
SQL> 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:
SQL> sqlplus "sys/password as sysdba" SQL> select name,value from v$parameter;
For more information, refer to you database administration documentation.
Note:
The information provided in this chapter was accurate at time of publication. Always refer to the Oracle Fusion Middleware 12c Certifications Matrix for the latest information.
The path that you must take to upgrade to a new Oracle Database release depends on the release number of your current database. It might not be possible to directly upgrade from your current release of Oracle Database to the latest release. Depending on your current release, you might be required to upgrade through one or more intermediate releases to upgrade to the new Oracle Database.
For example, if the current database is running release 9i, then follow these steps:
Table 2-1 contains the required upgrade path for each release of Oracle Database. Use the upgrade path and the specified documentation to upgrade your database. The information provided below was accurate at time of publication. Always refer to the Oracle Fusion Middleware 12c Certifications Matrix for the latest information.
|
Table 2-1 Supported Upgrade Paths for Upgrading Oracle Database
|
Your system backup must include the SYSTEM.SCHEMA_VERSION_REGISTRY$ table.
Each Fusion Middleware schema has a row in the SYSTEM.SCHEMA_VERSION_REGISTRY$ table. If you run the Upgrade Assistant to update an existing schema and it does not succeed, you must restore the original schema before you can try again. Make sure you back up your existing database schemas before you run the Upgrade Assistant.
Note:
Performing these backups prior to performing a schema upgrade is a prerequisite for running Upgrade Assistant. In the Upgrade Assistant prerequisites GUI screen, you will be required to acknowledge that backups have been performed, before proceeding with the actual upgrade.Before running Upgrade Assistant, you should make sure that your supported database is up and running and that the schemas you want to upgrade are at versions that are supported for upgrade.
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.
Before you run the Upgrade Assistant, make sure that you have verified that the schemas you want to upgrade are supported for an upgrade to this version of Oracle Fusion Middleware.
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 ;
If the number in the "VERSION" is at 11.1.1.7.0 or higher, and the STATUS column is 'VALID', then the schema is supported for upgrade.
If an upgrade is not needed for a schema, the schema_version_registry table retains the schemas at their pre-upgrade version after the 12.2.1 upgrade.
If you are using an Oracle database, you should recompile database objects before running the Upgrade Assistant to check for invalid objects before the upgrade. Connect to the database as SYS and run the following from SQL*Plus:
SELECT owner, object_name FROM all_objects WHERE status='INVALID';
Take note of any invalid objects and run the following query for more information. The existence of invalid database objects may prevent the upgrade from completing successfully.
/rdbms/admin/utlrp.sql
To recompile just the objects that belong to a single Oracle Fusion Middleware schema, you can use the Oracle Database stored procedure dbms_utility.compile_schema as shown in the example below:
SQL> execute
dbms_utility.compile_schema('1213_IAU');
PL/SQL procedure successfully completed
Note:
These procedures should be used again after running the Upgrade Assistant for verification.
Potential interoperability and upgrade issues can be avoided by making sure you have applied the latest patch sets, and that you have reviewed the list of recommended patches that are designed to help you avoid any problems during upgrade.
For more information, see the Upgrade chapter of the Release Notes for your platform. For example, if you are using a Linux operating system, refer to "Patches Required to Address Specific Upgrade and Compatibility Requirements" in the Oracle® Application Server Release Notes .
For additional information about database patching requirements, see "Review System Requirements and Specifications" in the Planning an Installation of Oracle Fusion Middleware.