3 Update the Oracle Fusion Applications and Oracle Identity Management Databases

To apply the certified database (DB) bundle patch and to upgrade the fusionapps database on Solaris platforms, perform the following steps:

1. Apply the version of OPatch that is delivered in the repository on the database host as follows:

   export  ORACLE_HOME=<Fusionapps DB oracle home >
   cd $ORACLE_HOME 
   mv -f  OPatch OPatch_orig 
   unzip 
   <REPOSITORY>/installers/database_upgrade/opatch/p6880880_112000_SOLARIS64.zip 
   

2. Execute catsem.sql as shown in the following example and confirm the MDSYS schema creation is successful:

    @$ORACLE_HOME/md/admin/catsem.sql 
   
   SQL> select namespace, attribute, value, description 
   from mdsys.rdf_parameter 
   where namespace = 'MDSYS' and attribute = 'SEM_VERSION';
   
           NAMESPACE                      ATTRIBUTE              VALUE             DESCRIPTION 
   -------------------------------------------------------------------------------------------------------- 
           MDSYS                          SEM_VERSION            11204             VALID
   

3. Shutdown the Fusion Applications (FA) DB.
4. Apply the DB patches as follows:

   cd <REPOSITORY>/installers/database_upgrade/psu  
   $ORACLE_HOME/OPatch/opatch napply
   
    cd  <REPOSITORY>/installers/database_upgrade/patch  
   $ORACLE_HOME/OPatch/opatch napply
   

5. Restart the FA DB and perform the following post installation steps:
   1. Connect to the FA DB and execute the following sql script with the given arguments:

       @$ORACLE_HOME/rdbms/admin/catbundle.sql  exa apply
      

   2. Run the following sql script to recompile the invalid objects created in the DB:

      @$ORACLE_HOME/rdbms/admin/utlrp.sql
      

6. Execute the following query to check if any invalid objects are present in the database after the upgrade:

   SELECT owner, object_type, object_name FROM dba_objects WHERE status = 'INVALID' ORDER BY owner, object_type, object_name;
   

   Proceed to Steps 7 and 8 only if the query returns any rows.
7. Log in to the FA DB as sys user and execute the following grants:

   GRANT SELECT ON CRM_FUSION_SOAINFRA.WFTASK TO FUSION; 
   GRANT SELECT ON CRM_FUSION_SOAINFRA.WFMESSAGEATTRIBUTE TO FUSION; 
   GRANT SELECT ON CRM_FUSION_SOAINFRA.WFASSIGNEE TO FUSION; 
   GRANT SELECT ON CRM_FUSION_SOAINFRA.WFTASK TO FUSION_RUNTIME; 
   GRANT SELECT ON CRM_FUSION_SOAINFRA.WFMESSAGEATTRIBUTE TO FUSION_RUNTIME; 
   GRANT SELECT ON CRM_FUSION_SOAINFRA.WFASSIGNEE TO FUSION_RUNTIME; 
   

8. Run the following script to re-compile the invalid objects:

   @$ORACLE_HOME/rdbms/admin/utlrp.sql
   

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_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.

1. Get opatch patch from the rdbms_12.1.0.2.0/exadata/linux64/opatch/ directory.

2. Apply the Exadata bundle that is located under the rdbms_12.1.0.2.0/exadata/linux64/exadata_bundles/ directory.

3. 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.

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:

1. Copy or mount the Oracle Fusion Applications Release 12 Repository on a Linux machine.

2. 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.

3. 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 
   

4. 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:

1. Download the ojvmctrl patch 23341410 from My Oracle Support.
2. Unzip the patch to a stage directory, for example, STAGE_DIR.
3. Run the following command:

   cd $STAGE_DIR/bin
   

4. Enable JAVA Development by running the following command:

   sh ojvmctrl.sh -mode enable -appbase APPLICATIONS_BASE -stage
   

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.