4 Upgrading and Preparing Your Oracle Databases for 12c (12.1.2)
This chapter contains the following sections:
4.1 Understanding the 12c (12.1.2) Database Requirements
It is important that you review the very latest information on database requirements for Oracle Fusion Middleware before proceeding with your database upgrade. For more information, see the Certification Matrix for 12c (12.1.2).
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.
For the most up-to-date information about the specific Oracle and third-party database versions supported for Oracle Fusion Middleware 12c (12.1.2), as well as other important system requirements, see Section 2.8.1, "Verifying Certification and System Requirements".
4.2 Verifying Your Database and Schemas are Ready for Upgrade
Before running Upgrade Assistant, you should make sure that your database is up and running and that the schemas you want to upgrade are at versions that are supported for upgrade.
Verifying Schema Versions
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.
If you are using an Oracle database, connect to the database as SYS and run the following from SQL*Plus to get the current version numbers:
SELECT OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY;
If the number in the "VERSION" column is 18.104.22.168.0 or 22.214.171.124.0 and the STATUS column is 'VALID', then the schema is supported for upgrade.
Only the Repository Creation Utility and Upgrade Assistant should modify the contents of the schema version registry table.
Users should not issue any INSERT, UPDATE, DELETE, GRANT or ALTER TABLE statements against the schema version registry with interactive SQL statements or scripts.
Checking for Invalid Database Objects
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.
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('1212_IAU'); PL/SQL procedure successfully completed
These procedures should be used again after running the Upgrade Assistant for verification.
4.3 Determining the Upgrade Path for Upgrading Oracle Database
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:
Upgrade release 126.96.36.199 to release 10.2.0.4 using the instructions in Oracle Database Upgrade Guide Release 2 (10.2).
Upgrade release 10.2.0.4 to the new Oracle Database 11g release using the instructions in Oracle Database Upgrade Guide.
Table 4-1 contains the required upgrade path for each release of Oracle Database. Use the upgrade path and the specified documentation to upgrade your database.
Table 4-1 Supported Upgrade Paths for Upgrading Oracle Database
|Current Release||Upgrade Path|
188.8.131.52 (or earlier)
Direct upgrade is not supported. Upgrade to an intermediate Oracle Database release before you can upgrade to the new Oracle Database 11g release, as follows:
When upgrading to an intermediate Oracle Database release, follow the instructions in the intermediate release's documentation. Then, upgrade the intermediate release database to the new Oracle Database 11g release using the instructions in "Upgrading to the New Release of Oracle Database" in Oracle Database Upgrade Guide.
Direct upgrade to Oracle Database 11g release is supported from 184.108.40.206 or higher, 10.1.0.5 or higher, 10.2.0.2 or higher, and 220.127.116.11 or higher.
For release 18.104.22.168, you must first upgrade to an intermediate Oracle Database release, as follows:
22.214.171.124 (or earlier) -> 126.96.36.199 -> 188.8.131.52
184.108.40.206 (or earlier) -> 220.127.116.11 -> 11.2
To upgrade to a new Oracle Database release, follow the instructions in "Upgrading to the New Release of Oracle Database" in Oracle Database Upgrade Guide.
4.4 Applying the Latest Patch Set Updates and Any Required Patches
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 Fusion Middleware Release Notes for Linux x86.
For additional information about database patching requirements, see "Review System Requirements and Specifications" in the Planning an Installation of Oracle Fusion Middleware.