The steps in this and the following sections are downtime activities and can be planned and performed in a separate downtime window prior to the upgrade.
Before proceeding, ensure that the Oracle Database version is 11.2.0.4. All of the patches discussed in this section require this database version. If you are upgrading from Release 8 (11.1.8.0.0), you must upgrade the Fusion Applications and IDM databases from Oracle Database version 11.2.0.3 to 11.2.0.4. This is a pre-requisite to upgrade to Fusion Applications Release 12 (11.12.x.0.0).
It is a best practice to apply these patches on Identity Management databases to keep both the Oracle Fusion Application database and Identity Management database synchronized. It is also a best practice to back up both of these databases before patching. See Back Up and Recover Oracle Fusion Applications in the Oracle Fusion Applications Administrator's Guide.
To apply the certified database (DB) bundle patch and to upgrade the fusionapps
database on Solaris platforms, perform the following steps:
To upgrade to Oracle Fusion Applications Release 12 (11.12.x.0.0), use the certified RDBMS patch 11.2.0.4.160811FA-DBBP (11gR2).
rdbms_version
directory, where version
is the database version. An example of the directory path is as follows:
rdbms_12.1.0.2.0/exadata
After downloading and unzipping the latest P4FA, perform the following steps:
The examples in this procedure use linux64 as the platform.
Get opatch patch from the rdbms_12.1.0.2.0/exadata/linux64/opatch/
directory.
Apply the Exadata bundle that is located under the rdbms_12.1.0.2.0/exadata/linux64/exadata_bundles/
directory.
Apply the one-off patches from the generic and linux64 directories as shown in the following example:
The one-off patches can be applied in any order.
rdbms_12.1.0.2.0/exadata/generic/one_off_patches/*
rdbms_12.1.0.2.0/exadata/linux64/one_off_patches/*
See Apply Technical Patch Bundles: P4FA in the Oracle Fusion Applications Patching Guide.
This section provides the parameters that need to be manually tuned in both the Fusion Applications (FA) database and the Oracle Identity Manager (IDM) database.
FA Database
The following table displays the FA database parameters to be tuned manually. Update these parameters to the recommended values:
Table 3-1 Recommended Values for FA Database Parameters for Manual Tuning
Parameter | Type | Location | Recommended Value |
---|---|---|---|
|
Initialization |
Spfile/pfile |
FALSE |
|
Initialization |
Spfile/pfile |
TRUE |
|
Disk IO |
Spfile/pfile |
FUSIONAPPS_PLAN |
|
Disk IO |
Spfile/pfile |
Unset so the database chooses a default value based on the platform |
|
Connection timeout |
|
120 |
|
Connection timeout |
|
130 |
|
Initialization |
Spfile/pfile |
12 |
|
Initialization |
Spfile/pfile |
12 |
|
Initialization |
Spfile/pfile |
DB, EXTENDED |
|
Automated Maintenance Tasks |
Database |
Disable |
|
Automated Maintenance Tasks |
Database |
Disable |
IDM Database
11g Database: The default is 0.05GB but 2GB for each redo log file is recommended for improving the redo log performance.
12c Database: The default is 0.05GB but 2GB for each redo log file is recommended for improving the redo log performance. The 12c database recommended parameters will apply after the upgrade to Release 12 is done and the 11g database is upgraded to 12c.
The following table displays the IDM database parameters to be tuned manually. Update these parameters to the recommended values:
Table 3-2 Recommended Values for IDM Database Parameters for Manual Tuning
Parameter | Type | Location | Recommended Value |
---|---|---|---|
|
Initialization |
Spfile |
12 |
|
Initialization |
Spfile |
0 |
|
Initialization |
Spfile |
TRUE |
Perform this step if you are upgrading from a Release 11.1.8.x.0 environment to Release 11.12.x.0.0.
select * from schema_version_registry where OWNER='FUSION_OTBI' and COMP_ID='ATGLITE_OTBI';
INSERT INTO SCHEMA_VERSION_REGISTRY (COMP_ID,COMP_NAME,MRC_NAME,MR_NAME,MR_TYPE,OWNER,VERSION,STATUS,UPGRADED,START_TIME,MODIFIED) values ('ATGLITE_OTBI','Oracle Transactional Business Intelligence- ATGLITE','FUSION_OTBI','ATGLITE_OTBI','ATGLITE_OTBI','FUSION_OTBI','11.1.1.7.0','VALID','N',null,null)
If Oracle Fusion Applications Release 8 is being run on a Solaris platform only, perform the following steps to add schemas that are introduced between Release 8 and Release 11 along with new schemas introduced in Release 12:
Copy or mount the Oracle Fusion Applications Release 12 Repository on a Linux machine.
Locate the rcuHome_fusionapps_linux.zip
file in REPOSITORY_LOCATION/
installers/apps_rcu_11g/linux
and unzip its contents. This location is referred to as RCU_HOME
.
Run the following command from RCU_HOME
to create the required schemas:
RCU_HOME/bin/rcu -silent -createRepository -databaseType ORACLE -connectString db_server:db_port/db_sid -dbUser sys -dbRole sysdba -schemaPrefix FUSION -component FUSION_EDQCONFIG2 -component FMW_RUNTIME -component FUSION_EDQRESULTS1 -component FUSION_INTG_CURRENT -component FUSION_EDQRESULTS2 -component FUSION_RDF -component LCM_SUPER_ADMIN -component DVACCTMGR -component FUSION_INTG_PREVIOUS -component FUSION_INTG_FINAL -component FUSION_GRC -component DVOWNER -component FUSION_EDQCONFIG1 -component LCM_OBJECT_ADMIN -component LCM_EXP_ADMIN -component FUSION_EDQFUSION -component FUSION_RO -component LCM_USER_ADMIN -component FUSION_BIA_CLOUD -component FUSION_ERO -component HED_FUSION_MDS_SOA -component FUSION_OPSS -component HED_FUSION_SOAINFRA
Provide the passwords for the following components:
Sys password FUSION_EDQCONFIG2 password FMW_RUNTIME password FUSION_INTG_CURRENT password FUSION_EDQRESULTS1 password FUSION_EDQRESULTS2 password FUSION_RDF password LCM_SUPER_ADMIN password DVACCTMGR password FUSION_INTG_PREVIOUS password FUSION_INTG_FINAL password FUSION_GRC password DVOWNER password FUSION_EDQCONFIG1 password LCM_OBJECT_ADMIN password LCM_EXP_ADMIN password FUSION_EDQFUSION password FUSION_RO password LCM_USER_ADMIN password FUSION_BIA_CLOUD password FUSION_ERO password HED_FUSION_MDS_SOA password FUSION_OPSS password HED_FUSION_SOAINFRA password
Enable Oracle Java Virtual Machine (OJVM) by performing the following steps:
Perform this step only after you complete the Enable Oracle Java Virtual Machine in the Database step and if the upgrade to Release 12 is from Release 8 or Release 9. Skip this step if the upgrade starting point is Release 10. OSN components introduced in 11.1.10.x.0 require the enablement of the Resource Description Framework (RDF) option in the database prior to the upgrade. This option must be enabled only in the Oracle Fusion Applications database.
To enable RDF, connect to the database as the SYS user with SYSDBA privileges (SYS AS SYSDBA, and enter the SYS account password when prompted). Then, start SQL*Plus, and enter the following statement:
Unix: @$ORACLE_HOME/md/admin/catsem.sql
For more information, see Enabling RDF Semantic Graph Support in a New Database Installation in the Oracle Spatial and Graph RDF Semantic Graph Developer's Guide.