5 Using RUP Installer to Upgrade to Release 5

This chapter describes how to run RUP Installer to upgrade to Oracle Fusion Applications 11g Release 5.

This chapter contains the following topics:

Introduction to Oracle Fusion Applications RUP Installer
Changes to Manual Steps in Release 5
Prepare to Upgrade - Before Down Time
Prepare to Upgrade - During Down Time
Run RUP Installer
Complete the Post Upgrade Tasks
Troubleshoot RUP Installer Sessions

5.1 Introduction to Oracle Fusion Applications RUP Installer

This section provides an introduction to the following concepts related to Oracle Fusion Applications RUP Installer (RUP Installer):

RUP Installer
RUP Installer User Interface
RUP Installer Configuration Tasks

5.1.1 RUP Installer

RUP Installer is a Java-based installer that enables you to install a group of patches across all product families to upgrade your installation to the next release of Oracle Fusion ApplicationsF. RUP Installer can patch existing content and can also copy and deploy new artifacts, depending on the contents of the release. RUP Installer is comprised of two installers that are chained together. The first installer manages updates to Oracle Fusion Applications Patch Manager and Oracle Fusion Middleware. The second installer manages updates to Oracle Fusion Applications. You can run RUP Installer in GUI mode or silent mode.

5.1.2 RUP Installer User Interface

In GUI mode, RUP Installer provides a graphical user interface which allows you to control the behavior of the installer by the use of buttons, in cases where it encounters a failure. Note that the behavior of these buttons may vary, depending on whether it is a task, or a step within a task, that fails. The behavior also depends on whether a task or step is mandatory. All mandatory configuration tasks must complete successfully before proceeding to the next configuration task. For information about which tasks are mandatory, see Section 5.1.3, "RUP Installer Configuration Tasks".

You can exit out of RUP Installer in the event of a failure and restart from the point of failure. If a non-mandatory task fails, and you continue to the next task, you must restart RUP Installer after it finishes running the subsequent tasks. When you restart, RUP Installer retries all failed configuration tasks and steps. For more information about what to do when a configuration action fails, see Section 5.7.4, "General Troubleshooting During the Configuration Phase in GUI Mode".

An explanation of the usage of each button follows. Note that the buttons are available only in GUI mode, and not in silent mode.

5.1.2.1 Abort Button

The Abort button allows you to skip a failed task or step within a task, and records the failure so it reruns when you restart the installation. For mandatory tasks, after you abort the task, RUP Installer does not proceed and only the Cancel button is enabled. You must then resolve the cause of the failure and start RUP Installer from this failure point. In the case of non-mandatory tasks, RUP Installer proceeds to the next configuration task after you abort the task. This button is enabled only after a failure.

5.1.2.2 Cancel Button

The Cancel button allows you to stop a RUP Installer session after a failure. This button is enabled only after a failure.

5.1.2.3 Close Button

The Windows Close button allows you to stop a RUP Installer session after a failure. This is enabled only after a failure.

5.1.2.4 Continue Button

The Continue button allows you to skip a failed non-mandatory task or non-mandatory step within a task, and records the failure. RUP Installer then proceeds with the next step. When you rerun this RUP Installer session, the failed configuration actions are attempted again.

Note that this button is enabled only for non-mandatory configuration actions.

5.1.2.5 Next Button

The Next button allows you to proceed to the next screen. This button is enabled only when all tasks complete successfully in the current screen.

5.1.2.6 Retry Button

The Retry button allows you to attempt to rerun a failed configuration task, or a step within a task. Use Retry when you know the cause of the failure and can resolve the issue during the current RUP Installer session.

5.1.3 RUP Installer Configuration Tasks

During the installation phase, RUP Installer copies all files for the release to the appropriate locations, such as Oracle Fusion Middleware home and Oracle Fusion Applications Oracle home. After the file copy completes, RUP Installer calls its first installer to install Oracle Fusion Applications Patch Manager and apply Oracle Fusion Middleware patches. When the first installer completes successfully, RUP Installer calls the second installer, which performs the Policy Store Analysis, as described in Table 5-13. Upon successful completion of the Policy Store Analysis, RUP Installer calls Configuration Assistants to perform the remaining tasks required to update and deploy the artifacts to Oracle Fusion Applications. Depending on the contents of the release, not all tasks run.

All mandatory configuration tasks must complete successfully before proceeding to the next configuration task. For more information, see Section 5.7.4, "General Troubleshooting During the Configuration Phase in GUI Mode" or Section 5.7.5, "General Troubleshooting During the Configuration Phase in Silent Mode".

If any tasks fail during the installation phase, refer to Section 5.7.2, "Troubleshooting Failures During the Installation Phase in GUI Mode" for more information.

Table 5-1 provides a list of configuration tasks that the first installer runs. The Retry Behavior and Troubleshooting column describes what RUP Installer does after a configuration task fails and you restart RUP Installer after you resolve the cause of the failure. If available, links are provided to the relevant troubleshooting sections.

Table 5-1 Configuration Tasks Run by Oracle Fusion Applications 11g Release 5 (11.1.5) RUP Installer Part 1 of 2

Name	Mandatory	Description	Retry Behavior and Troubleshooting
Configure Patch Manager	Yes	Configures Oracle Fusion Applications Patch Manager.	Starts from the beginning of the task.
Update Patch Manager	Yes	Applies Patch Manager Repository Patches. Applies Patch Manager Downloaded Patches, as described in Section 5.3.6, "Download Mandatory Post Release 5 Patches".	Applies failed patches.
Reconfigure Patch Manager	Yes	Reconfigures Oracle Fusion Applications Patch Manager.	Starts from the beginning of the task.
Bootstrap Patch Manager	Yes	Updates the data model for Oracle Fusion Applications Patch Manager by running the `fapmgr` `bootstrap` command.	Starts from the beginning of the task. See Section 5.7.8, "Troubleshooting Bootstrapping Patch Manager".
Apply Middleware Patch Sets	Yes	Applies Oracle Fusion Middleware patch sets, which include schema changes and installers.	Installs failed patch sets.
Apply Pre-PSA Middleware Patches	Yes	Applies Pre-PSA Repository Patches. Applies Pre-PSA Downloaded Patches, as described in Section 5.3.6, "Download Mandatory Post Release 5 Patches". For more information, see Section 5.1.3.1, "Middleware Installers Invoked by the Apply Pre-PSA Middleware Patches Task" and Section 5.1.3.2, "Patches Not Supported by the Apply Pre-PSA and Post-PSA Middleware Patches Tasks".	Applies the failed patches. See Section 5.7.9, "Troubleshooting Applying Middleware Patches".
Verify Middleware PSA Schema Credentials	Yes	Verifies users and logins for schemas.	Starts from the beginning of the task.
Upgrade Middleware Schemas	Yes	Runs Oracle Fusion Middleware patch set assistants (PSA) to upgrade schemas.	Runs failed tasks. See Section 5.7.10, "Troubleshooting Upgrading Middleware Schema".
Apply Post-PSA Middleware Patches	Yes	Applies Post-PSA Repository Patches. Applies Post-PSA Downloaded Patches, as described in Section 5.3.6, "Download Mandatory Post Release 5 Patches". See Section 5.1.3.2, "Patches Not Supported by the Apply Pre-PSA and Post-PSA Middleware Patches Tasks".	Applies the failed patches. See Section 5.7.9, "Troubleshooting Applying Middleware Patches".
Extend Certificate Validity	Yes	Extends certificate validity by three years from the date of the upgrade.	Starts from the beginning of the task.
Deploy BI Application Policies	Yes	Deploys updated applications policies for Oracle Business Intelligence.	Retries failed steps.
Apply Domain Configuration	Yes	Deploys EM Selective Applications Trace Library. Deploys Application Core Logger Library. Changes Startup Parameter File Location. Applies Startup Parameter Changes. Applies Domain Environment Variable Changes. Changes Identity and Trust File Location. Reassigns WSM-PM Targets. Deploys Click History Library.	Retries failed steps.
Propagate Domain Configuration	Yes	Unzips RUP Lite for Domain Configuration into `APPLICATIONS_CONFIG/fapatch/admin/ruplitedomain/`version. Updates properties in the RUP Lite `env.properties` file and prepares RUP Lite so you can run RUP Lite for Domain Configuration.	Starts from the beginning of the task. See Section 5.7.12, "Troubleshooting Failure During Propagating Domain Configuration".

Table 5-2 provides a list of configuration tasks that the second installer runs. The Retry Behavior and Troubleshooting column describes what RUP Installer does after a configuration task fails and you restart RUP Installer after you resolve the cause of the failure. If available, links are provided to the relevant troubleshooting sections.

Table 5-2 Configuration Tasks Run by Oracle Fusion Applications 11g Release 5 (11.1.5) RUP Installer Part 2 of 2

Name	Mandatory	Description	Retry Behavior and Troubleshooting
Configure Patch Manager	Yes	Configures Oracle Fusion Applications Patch Manager.	Starts from the beginning of the task.
Bootstrap Patch Manager	Yes	Updates the data model for Oracle Fusion Applications Patch Manager by running the fapmgr `bootstrap` command.	Starts from the beginning of the task. See Section 5.7.8, "Troubleshooting Bootstrapping Patch Manager".
Offline Preverification	Yes	Performs the following validation checks: Policy Store Number of Database Workers Database Content Upload Business Process Management (BPM) Template Oracle Data Integrator (ODI)	Runs failed steps.
Grant Privileges to Application Schemas	Yes	Grants system privileges to database users and creates base object privileges.	Runs the failed script after you resolve the issue. See Section 5.7.14, "Failure During Grant Privilege Scripts".
Load Database Components	Yes	Uploads database content to the database, such as database objects, seed data, and package headers and bodies.	Runs failed database commands. See Section 5.7.15, "Troubleshooting Loading Database Components".
Create Grants/Synonyms on Application Database Objects	Yes	Creates synonyms between database objects and grants object privileges to database users.	Runs the failed script after you resolve the issue. See Section 5.7.14, "Failure During Grant Privilege Scripts".
Deploy Applications Policies (jazn-data.xml)	Yes	Deploys updated applications policies, based on your selections during the Policy Store Analysis task. This task does not run if you installed a Language Pack and chose to override the base English strings in the policy store by setting the `J-DupdateJAZNPolicyStore` option to `true`.	Deploys the failed stripes. See Section 5.7.16, "Troubleshooting Deployment of Applications Policies".
Deploy Data Security Grants	Yes	Performs GUID reconciliation in LDAP.	Starts from the beginning of the task.
Upgrade Topology Manager Data	Yes	Updates Topology Manager data to mark new applications as deployed.	Starts from the beginning of the task.
Generate ADF Domain Configuration Plan	Yes	Generates Oracle ADF domain configuration in Metadata Service (MDS) to be used by Expression Language (EL) expressions in `connections.xml`.	Starts from the beginning of the task.
Generate SOA Configuration Plan	Yes	Generates the configuration plan to be used for deploying SOA composites.	Starts from the beginning of the task.
Update Flexfield Configuration	Yes	Updates the `FndSetup` application for supporting new flexfields, new flexfield usages, and flexfield view links added by Oracle Fusion Application products.	Starts from the beginning of the task.
Deploy BPM Templates	Yes	Deploys BPM Templates to the MDS repository.	Deploys failed templates.
Deploy BI Publisher Artifacts	Yes	Using Catalog Manager, performs the following steps: Backs up BI Presentation Catalog under `FA_ORACLE_HOME/admin/BIP/version/language_code`, for example, `FA_ORACLE_HOME/admin/BIP/11.1.5.0.0/en_US/webcat.zip`. Copies captions to the Oracle Business Intelligence repository. Deploys BI Presentation Catalog to the Oracle Business Intelligence repository.	Starts from the beginning of the task. See Section 5.7.17, "Oracle BI Presentation Catalog Patch File Creation Failure" and Section 5.7.18, "Updating BI Presentation Catalog to Resolve a Failure During Deploying BI Publisher Artifacts".
Import Oracle Data Integrator Repositories	Yes	Imports ODI topology. Imports ODI model folders. Imports ODI models. Imports ODI projects. Drops ODI error tables.	Imports failed data.
Apply Offline Setting Changes	Yes	Applies Oracle Fusion Applications environment configuration setting changes while all servers are shut down.	Retries failed domains.
Verify Node Manager and OPMN Status	Yes	Verifies the following processes: Node Managers BI OPMN Processes GOP OPMN Processes Web Tier Processes You must not exit out of RUP Installer during this task.	Runs failed steps. See Section 5.7.19, "Troubleshooting Failure During Verifying Node Manager and OPMN Status".
Start All Admin Servers	No	Starts all Administration Servers.	Restarts failed Administration Servers. See Section 5.7.20, "Troubleshooting Server Start and Stop Failures".
Grant Application Role	No	Grants `SOA operator` privileges to the `HCM admin` role so BPM processes can be deployed.	Starts from the beginning of the task.
Apply Admin Server Online Setting Changes	Yes	Applies Oracle Fusion Applications environment configuration setting changes that are applicable to the Administration Servers.	Starts from the failed task.
Start Minimal Servers to Update Configuration	No	Bounces minimal set of servers in the Common Domain, including `UCM_SERVER, soa_server, FunctionalSetupServer`, and `AdminServer.`	Starts failed servers.
Apply WebCenter Worklist Connection Changes	Yes	Applies connection changes for the Oracle WebCenter Worklist.	Starts from the beginning of the task.
Start All Servers	No	Starts all servers in all domains, including the BI servers. Also performs the `opmnctl` start for OHS and `BIInstance`.	Restarts failed servers. See Section 5.7.20, "Troubleshooting Server Start and Stop Failures".
Online Preverification	Yes	Performs steps described in Section 5.1.3.3, "Steps Performed During Online Preverification Task".	Runs failed steps. See Section 5.7.21, "Failures During Online Preverification".
Generate OHS Reference Configuration File	No	Generates Oracle HTTP Server (OHS) configuration files for installed product families in the `APPLICATIONS_BASE/fusionapps/applications/admin/OHS/patched_moduleconf` directory.	Starts from the beginning of the task.
Apply OAM Configuration	No	Applies changes to the Oracle Access Manager configuration.	Starts from the beginning of the task. See Section 5.7.23, "Location of GRC Policies in the OAM Applications Domain".
Apply OWSM Configuration	Yes	Upgrades Oracle Web Services Manager (Oracle WSM) policies after backing up the policies.	Restores the backup of the policies and starts from the beginning of the task.
Apply SES Configuration Changes	No	Updates additional configuration updates to SES running on the Common Domain.	Starts from the beginning of the task.
Deploy Flexfields	No	Deploys flexfields to the domain that hosts the `FndSetup` application.	Starts from the beginning of the task.
Import Image Routing (IPM) Artifacts	No	Deploys IPM artifacts to the IPM server.	Retries failed IPM artifacts. See Section 5.7.24, "Failure During IPM Import".
Deploy SPE Inline Service Artifacts	No	Deploys SPE Inline Service Artifacts.	Retries the deployment.
Deploy Data Role (RGX) Templates	No	Deploys RGX Template artifacts to the Common Domain.	Deploys failed templates.
Import Group Space Templates	No	Imports Group Space Templates.	Deploys failed templates.
SOA Preverification	Yes	Performs the steps described in Section 5.1.3.4, "Steps Performed During SOA Preverification".	Retries failed steps. See Section 5.7.22, "Merging SOA Composite JDeveloper Customizations During RUP Installation".
Deploy B2B Metadata	No	Deploys B2B Metadata.	Deploys failed B2B artifacts.
Deploy SOA Shared Repository	Yes	Deploys SOA shared repository artifacts to SOA servers.	Deploys failed SOA shared repository artifacts.
Deploy UpdateSOAMDS Composite	No	Deploys the `UpdateSOAMDS` composite to every domain.	Deploys composite on domains that failed.
Deploy SOA Composites	No	Deploys SOA composites to the corresponding SOA servers and performs server management steps.	Deploys failed SOA composites. See Section 5.7.25, "Troubleshooting SOA Composite Deployment Failures".
Deploy SOA Resource Bundles	Yes	Deploys SOA Resource Bundles to the corresponding SOA servers.	Deploys failed SOA resource bundles.
Restart All SOA Servers	No	Restarts all SOA servers in the environment.	Starts at the beginning of the task.
Apply Online Setting Changes	No	Applies Oracle Fusion Applications environment configuration setting changes during the online phase.	Starts from the failed task.
Generate RUP Lite for OHS	No	Generates the zip file that contains all files needed by RUP Lite for OHS for upgrading OHS.	Starts at the beginning of the task.
Apply BI Metadata Updates	Yes	Applies Oracle Business Intelligence Metadata updates.	Starts from the beginning of the task. If you made any customizations to the Oracle BI Repository, the Oracle BI Presentation Catalog, or JAZN settings related to Oracle Business Intelligence, you must merge your changes. For more information, see Section 5.6.14, "Resolve Conflicts That Occurred During BI Metadata Updates".
Apply Downloaded Patches	Yes	Applies the Oracle Fusion Applications patches that you downloaded in Section 5.3.6, "Download Mandatory Post Release 5 Patches".	Applies failed patches.
Post Configuration	No	Reactivates SES Index Optimization and the ESS Server from inactive or quiescent mode.	Retries failed domains.

5.1.3.1 Middleware Installers Invoked by the Apply Pre-PSA Middleware Patches Task

The following installers are invoked by the Apply Pre-PSA Middleware Patches configuration task:

Oracle Business Intelligence
Oracle Common
Oracle Data Integrator (ODI)
Oracle Database Client
Oracle Enterprise Content Management
Oracle HTTP Server (OHS)

OHS may be installed either beside the rest of the Oracle Fusion Middleware in the Oracle Fusion Applications middle tier or on a separate DMZ machine. For either case, patching OHS requires extra steps after running RUP Installer. You must patch OHS using RUP Lite for OHS as described in Section 5.6.1, "Complete the Web Tier Upgrade Using RUP Lite for OHS".
Oracle Fusion Middleware Extensions for Applications
Oracle Global Order Promising
Oracle Secure Enterprise Search (SES)
Oracle SOA Suite
Oracle WebCenter Suite
Oracle WebLogic Server
Oracle Web Tier

5.1.3.2 Patches Not Supported by the Apply Pre-PSA and Post-PSA Middleware Patches Tasks

The following patches are not supported by sleepily Pre-PSA and Post-PSA Middleware Patches configuration tasks:

Integrated Development Environment (IDE)
OHS installed in the DMZ

You must patch OHS using RUP Lite for OHS as described in Section 5.6.1, "Complete the Web Tier Upgrade Using RUP Lite for OHS".
Patching your Database Server

You patch your database server using RUP Lite for RDBMS. For more information, see Section 5.4.4, "Apply Mandatory Prerequisite RDBMS Patches".
Patching your Oracle Identity Management Server:

For more information, refer to Section 5.4.3, "Upgrade Oracle Identity Management Domain to 11g Release 5 (11.1.5)".

5.1.3.3 Steps Performed During Online Preverification Task

The following validation steps are performed during the Online Preverification task, if the release being installed contains artifacts related to the validation:

Taxonomy URL
Database validation
Flexfield

Checks for the HelpPortal Managed Server in the Common Domain and for the successful deployment of the FndSetup application
OAM Configuration
Image Routing (IPM)

Checks if the IPM server is up
SES Admin Server URL
SPE Inline Service

Checks if the Oracle CRM Performance application is deployed. If it is, the OracleRTD application must be deployed and at least one BI server must be running where the OracleRTD application is deployed.
Data Role (RGX) Template

Checks if the Administration Server for the Common Domain is up
Group Space Template

Checks if the following Managed Servers are up: WC_Spaces, WC_Collaboration, ucm_server1
Oracle WSM validation

5.1.3.4 Steps Performed During SOA Preverification

The following validation steps are performed during the SOA Preverification task:

B2B Metadata

Checks if the Common Domain SOA Managed Server and the LDAP Server are up
SOA Shared Repository

Verifies the taxonomy, checks if the Administration Server is up, and checks for SOA_SERVER and SOA_PLATFORM readiness
UpdateSOAMDS SOA Composite

Verifies the taxonomy, checks if the Administration Server is up, and if the SOA platform is ready
SOA Resource Bundle

Verifies the taxonomy, checks if the Administration Server is up, and if the SOA platform is ready
SOA Composites

Performs the following validation steps:
- Verifies the taxonomy
- Checks if the Administration Server is up
- Checks if the SOA platform is ready
- Checks if the base composite is deployed
- Checks if the default revision is deployed
- Checks if the new revision is not deployed
- Checks whether the SOA composites that will be affected by the patch have JDeveloper customizations. For more information, see Section 5.7.22, "Merging SOA Composite JDeveloper Customizations During RUP Installation".

5.2 Changes to Manual Steps in Release 5

This section describes changes that were made to manual steps in Release 5. The following updates are described:

Changes to Pre-Upgrade Steps Performed Before Down Time
Changes to Pre-Upgrade Steps Performed During Down Time
Changes to Post-Upgrade Steps

5.2.1 Changes to Pre-Upgrade Steps Performed Before Down Time

The following changes were made to the pre-upgrade steps that you perform before your down time:

Added a SQL*Plus command to confirm the installation of the previous release. See Section 5.3.2, "Confirm Installation of the Previous Release"
Added a step to set environment variables. See Section 5.3.4, "Set Environment Variables".
The step previously titled "Configure Oracle Metadata Services (MDS)" was replaced by Section 5.3.20.2, "Run Health Checker for DBMS Stats".
Steps for Windows were added to Section 5.3.9, "Confirm Host Name".
Steps for Solaris and Windows were added to Section 5.3.10, "Verify the Local Port Range Value".
Steps for Section 5.3.16, "Update Oracle Fusion Middleware Schema Credentials" were slightly modified.
The step previously titled "Verify Credentials in Oracle Directory Services Manager (ODSM)" was replaced by Section 5.3.20.1, "Run Health Checker for IDM Setup".
The step titled "Move the userpref_currencies.xml File" is no longer required.
The step for Section 5.3.18, "Verify the OHS Instance Is Registered (Oracle VM Hosts Only)" was added.
The step for Section 5.3.5, "Find Conflicting Patches" was added.
The step for Section 5.3.23.4, "Applying Patches to the ATGPF and Secure Enterprise Search Components (Solaris)" was added.

5.2.2 Changes to Pre-Upgrade Steps Performed During Down Time

The following changes were made to the pre-upgrade steps that you perform during your down time:

The step previously titled "Stop Running SES Schedules" was replaced by Section 5.4.1, "Stop Index Schedules and Deactivate Index Optimization".
The step titled "Confirm the Upgrade of Security Application Policies" is no longer required.
The step for Section 5.4.7, "Remove Conflicting Patches From the Primordial Host" was added.
The step titled "Install Third-Party GCC Libraries (Linux and Solaris Operating Systems Only)" is no longer required.
The steps for Section 5.4.4, "Apply Mandatory Prerequisite RDBMS Patches" are performed by running RUP Lite for RDBMS.
The step titled "Validate That All Database Server Patches Were Applied" was removed because RUP Lite for RDBMS runs this step.
The step for Section 5.4.4.4, "Apply Exadata Patches" was added.
The examples in Section 5.4.2.3, "Stop the Node Manager and the OPMN Control Process" were updated.
The step for Section 5.4.9, "Run the Inventory Cleanup Script" was added.

5.2.3 Changes to Post-Upgrade Steps

The following changes were made to the post-upgrade steps:

The step titled "Confirm the Oracle Web Services Manager Upgrade Was Successful" was removed.
The steps in Section 5.6.1, "Complete the Web Tier Upgrade Using RUP Lite for OHS" were modified.
The step for Section 5.6.2, "Run RUP Lite for OVM - Online (Oracle VM Hosts Only)" was added.
The step for Section 5.6.3, "Run RUP Lite for BI" was added.
The step titled "Validate That All OHS Patches Were Applied (Optional)" was removed.
The step titled "Validate That All Middleware Patches Were Applied" was removed.
The step titled "Update the wsm-pm Application Targeting" was removed.
The step titled "Activate the SES Schedules and Index Optimizer" was removed.
The step titled "Confirm the ESS Request Processer is Running" was removed.
The step titled "Perform Tasks Required in the IDM Domain" was removed.
The step for Section 5.6.14, "Resolve Conflicts That Occurred During BI Metadata Updates" was added.

5.3 Prepare to Upgrade - Before Down Time

This section describes the following preparation steps for upgrading to Release 5, all of which can be performed before your scheduled down time:

Before You Begin
Confirm Installation of the Previous Release
Download the Release Repository
Set Environment Variables
Find Conflicting Patches
Download Mandatory Post Release 5 Patches
Verify Your OPatch Version
Confirm Memory Settings
Confirm Host Name
Verify the Local Port Range Value
Confirm Database Settings
Confirm All Oracle Homes Are Registered in the Central Inventory
Confirm That JDeveloper Customizations Can Be Merged
Maintain Versions of Customized BI Publisher Reports
Validate Domain Directories
Update Oracle Fusion Middleware Schema Credentials
Verify the Default Realm Name is myrealm
Verify the OHS Instance Is Registered (Oracle VM Hosts Only)
Save WebLogic Configuration Changes
Run Health Checker
Run Script for DatabaseItemSD.xml
Verify Ownership and Permissions on Domains
Platform Specific Steps

5.3.1 Before You Begin

Before you begin the upgrade, you should have access to the following documentation:

RUP Installer documentation from the previous release
Oracle Fusion Applications release notes from the previous release
Oracle Fusion Applications release notes from the release you are upgrading to

You should also have a clear understanding of the following host and directories:

Primordial host: The primordial host is where the Administration Server for the Common Domain runs
APPLICATIONS_CONFIG: The top-level directory for the Oracle Fusion Applications configuration files
APPLICATIONS_BASE: The top-level directory for the Oracle Fusion Applications binaries
FA_ORACLE_HOME: Directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home

Figure 5-1 shows the relationship of the home directories using the Oracle Fusion Financials product family on a UNIX environment as an example. This figure does not show all the subdirectories under APPLICATIONS_BASE and APPLICATIONS_CONFIG. For example, the APPLICATIONS_CONFIG directory contains several more directories for component-specific configuration files. Also, Oracle Database and Oracle Identity Management are not represented in this figure, as they are installed separately. For more information, see "Provisioned Oracle Fusion Applications Home Directories" in the Oracle Fusion Applications Administrator's Guide.

Figure 5-1 Relationship of Home Directories

5.3.2 Confirm Installation of the Previous Release

Ensure that you have successfully installed 11g Release 1, Update 3 (11.1.4.0.0) by running the following SQL*Plus command as the FUSION user from the Oracle Fusion Applications database to confirm that your current release is 11.1.4.0.0:

select release_name from ad_product_groups;

Ensure that you have followed all post installation tasks in the 11g Release 1, Update 3 (11.1.4.0.0) documentation and in the release notes. For more information about release notes, see Oracle Fusion Applications Release Notes, 11g Release 1, Update 3 (11.1.4.0.0).

5.3.3 Download the Release Repository

The Release repository contains RUP Installer and Oracle Fusion Middleware patches that are required to upgrade to the next release in an existing Oracle Fusion Applications environment. You download the repository from the Oracle Fusion Applications Product Media Package to a location of your choice. This directory is referred to as REPOSITORY_LOCATION.

5.3.3.1 Obtaining the Software

Oracle groups its software releases by product area. A Product Media Pack refers to those groupings. Each media pack may also include a zipped file containing electronic documentation files or "Quick Install" files, which facilitate the initial installation of the software.

Once you have completed the software licensing agreements, you can obtain the Oracle Fusion Applications software using one of these two methods:

Oracle Software Delivery Cloud Portal: Provides you with a readme document that helps you to determine which media you need to fulfill the license you have purchased. You download only the media you need. This is the default delivery method.
Oracle Store: Provides a complete set of the software in DVD format. You use only the DVDs covered by your software licensing agreement.

Using either method, you can obtain the Oracle Fusion Applications Release repository and gain access to the Oracle Fusion Applications documentation library.

5.3.3.2 Downloading from the Oracle Software Delivery Cloud Portal

Go to http://edelivery.oracle.com/ and follow these instructions:

Complete the Export Validation process by entering basic identification information using the online form.
On the Media Pack Search page, specify the product pack and platform to identify the media pack you want to download. If you do not know the name of the product pack, you can search for it using the license list.
Choose the appropriate media pack from the search results and download the RUP repository (in zipped format). You can download the repository to a location of your choice.
Extract the contents of all zipped files to the same target directory. The directory must be on a networked drive or shared disk so that it will be accessible to all the hosts in your new environment. The installers are normally located in the installers subdirectory under REPOSITORY_LOCATION.

Note:

You should avoid creating the repository in a deeply nested directory on Windows. The Windows PATH variable has a limited size, and long directory names may cause it to overflow. For example, c:\work\my_repository is a better choice than c:\Work\WorkInProgress\FusionApps\FusionAppsv1\Nov2011\tempfiles\my_repository.

5.3.3.3 RUP Installers

Table 5-3 lists the installers in the repository.

Table 5-3 RUP Installers

Media Label Name Staging Destination

Media Label Name	Staging Destination
RUP Installer	(Unix) `REPOSITORY_LOCATION`/installers/farup/Disk1/runInstaller (Windows) `REPOSITORY_LOCATION`\installers\farup\Disk1\setup.exe

RUP Installer

(Unix) REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller

(Windows) REPOSITORY_LOCATION\installers\farup\Disk1\setup.exe

5.3.4 Set Environment Variables

Set the APPLICATIONS_BASE and REPOSITORY_LOCATION environment variables. Set the APPLICATIONS_BASE environment variable to point to the directory that contains Oracle Fusion Applications. For example, if Oracle Fusion Applications is installed in /server01/APPTOP/fusionapps, then set the environment variable APPLICATIONS_BASE to /server01/APPTOP. Set the REPOSITORY_LOCATION environment variable to point to the root directory where the repository is staged.

Examples follow:

(Unix)
setenv APPLICATIONS_BASE /server01/APPTOP/
setenv REPOSITORY_LOCATION /server01/REL5Repo/


(Windows)
SET APPLICATIONS_BASE=\server01\APPTOP\
SET REPOSITORY_LOCATION=\server01\REL5Repo\

Note:

Set these environment variables on all hosts that share the same APPLICATIONS_BASE before executing all upgrade tools and utilities mentioned in this guide.

5.3.5 Find Conflicting Patches

If you installed any post-Release 4 Oracle Fusion Middleware one-off patches on your Oracle Fusion Applications environment, they may conflict with patches in the Release 5 repository. To avoid this issue, you must obtain the list of conflicting patches, download the equivalent post-Release 5 one-off patches, and run the patch removal script.

Perform the following steps to obtain the list of conflicting patches:

Download patch 14543240 from My Oracle Support.
Follow the instructions in the README.txt file of the patch to run the script to obtain the list of conflicting patches. You must run this script on the following hosts: RDBMS, IDM, OHS, and the primordial host.

Keep a copy of the conflicting patches report for retrieval in the case of failure or restore.
Contact Oracle Support to obtain any post-Release 5 patches that provide equivalent functionality that will be lost when the conflicting patches are rolled back. Download these patches to the location mentioned in Section 5.3.6, "Download Mandatory Post Release 5 Patches".

5.3.6 Download Mandatory Post Release 5 Patches

Note:

If there are no post installation patches in Oracle Fusion Applications release notes when you run RUP Installer, there is no action required for this step.

RUP Installer can apply mandatory post installation patches that are required by Oracle Fusion Applications if you download the patches from My Oracle Support before you start the installation. Note that this feature relates only to patches that are documented in Oracle Fusion Applications release notes and that are specifically required for the Release that you are installing, in this case, Release 5. You download only RDBMS, OHS and Oracle Fusion Applications in this step. You do not download IDM patches in this step.

Perform the following steps to download the patches:

Download patch 16065686 from My Oracle Support and unzip the patch to any directory. After unzipping, the patch directory contains two files, PostRepoPatchDirs.zip and postRepoPatchDirsREADME.txt.
Review the postRepoPatchDirsREADME.txt file to confirm the location for the post_repo_patches directory. Create the directory named post_repo_patches in the parent directory of your APPLICATIONS_BASE directory. For example, if APPLICATIONS_BASE is /u01/APPTOP, create the patch directory, /u01/post_repo_patches.
Unzip PostRepoPatchDirs.zip in the post_repo_patches directory to create the directory structure for the patches you download.

Oracle recommends you use this exact directory name and location because upgrade-related utilities will find it automatically.

Note:

If you choose to download the patches to a different directory, you must use the -J-DpatchDownloadLocation option when you start RUP Installer. See Section 5.5.1, "Run RUP Installer in GUI Mode" or Section 5.5.2, "Run RUP Installer in Silent Mode" for more information.
Review the README file that was created when you unzipped PostRepoPatchDirs.zip to learn how the subdirectories under the post_repo_patches directory map to the corresponding components, such as Oracle Fusion Middleware, database client, and database server components.

Refer to the appropriate section in Oracle Fusion Applications release notes for Oracle Fusion Applications Release Notes, 11g, Release 5 (11.1.5), to find any additional patches to be downloaded from My Oracle Support.

Table 5-4 describes the types of patches that you download and where to find the list of patches in Oracle Fusion Applications release notes.

Table 5-4 Mandatory Patches to be Downloaded

Type of Patches	Location in Oracle Fusion Applications release notes	Configuration Task or Utility That Applies Patches
Oracle Database	Upgrade Known Issues, Pre-Upgrade Known Issues, Mandatory Patches to be Downloaded, Oracle Database	RUP Lite for RDBMS utility
Oracle Fusion Middleware	Upgrade Known Issues, Pre-Upgrade Known Issues, Mandatory Patches to be Downloaded, Oracle Fusion Middleware	Apply Pre-PSA Middleware Patches and Apply Post-PSA Middleware Patches configuration task
Oracle HTTP Server (OHS)	Upgrade Known Issues, Pre-Upgrade Known Issues, Mandatory Patches to be Downloaded, Oracle HTTP Server (OHS)	RUP Lite for OHS utility
Oracle Fusion Applications	Upgrade Known Issues, Pre-Upgrade Known Issues, Mandatory Patches to be Downloaded, Oracle Fusion Applications	Apply Downloaded Patches configuration task

Download and unzip the patches into the appropriate subdirectory under the post_repo_patches directory, based on the mapping information in the README file described in Step 3. If you do not download a patch to the correct directory, this could result in failure. Note that when you download the Oracle Fusion Applications patches, you must use the Patch Plan feature in My Oracle Support. If you cannot create a patch plan because you do not have Oracle Configuration Manager (OCM) configured, you can create the patch plan by running the script in Step 6.

An excerpt from a sample My Oracle Support patch plan follows:

<results>
<generated_date in_epoch_ms="..."></generated_date>
<plan>
<name>patchplan</name>
<type>patch</type>
<description/>
<last_analyzed></last_analyzed>
<oracle_home></oracle_home>
<host_name></host_name>
<org_id></org_id>
<conflict_free_list>
<patch>
<id>6530099</id>
<name>6530099</name>
<abstract>db</abstract>
<status></status>
<platform></platform>
<release></release>
<language></language>
<install_step></install_step>
</patch>
<patch>
<id>16021106</id>
<name>16021106</name>
<abstract>db</abstract>
<status></status>
<platform></platform>
<release></release>
<language></language>
<install_step></install_step>
</patch>
<patch>
<id>6712</id>
<name>6712</name>
<abstract>soa</abstract>
<status></status>
<platform></platform>
<release></release>
<language></language>
<install_step></install_step>
</patch>
<patch>
<id>731301</id>
<name>731301</name>
<abstract>db</abstract>
<status></status>
<platform></platform>
<release></release>
<language></language>
<install_step></install_step>
</patch>
<patch>
<id>9912345</id>
<name>9912345</name>
<abstract>soa</abstract>
<status></status>
<platform></platform>
<release></release>
<language></language>
<install_step></install_step>
</patch>
<patch>
<id>11112</id>
<name>11112</name>
<abstract>db</abstract>
<status></status>
<platform></platform>
<release></release>
<language></language>
<install_step></install_step>
</patch>
</conflictfree_list>
</plan>
</results>

Run this step if you cannot create a My Oracle Support patch plan. This step assumes that you have downloaded the patches as described in Step 5, without using the Patch Plan feature.

The Perl script, adCreateMosPlan.pl, reads the patch metadata from the downloaded patches to generate the patch plan file, mosdownload.xml. To run this script, use the Perl executable from APPLICATIONS_BASE/dbclient/perl/bin for Unix platforms and APPLICATIONS_BASE\dbclient\perl\5.8.3\bin\MSWin32-x64-multi-thread for Windows.

Use the following command syntax to create the patch plan file:

(Unix)
setenv PERL5LIB $APPLICATIONS_BASE/dbclient/perl/lib/5.8.3:$APPLICATIONS_BASE/dbclient/perl/lib/site_perl/5.8.3/:$APPLICATIONS_BASE/dbclient/perl/lib/site_perl

$APPLICATIONS_BASE/dbclient/perl/bin/perl $REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/bin/adCreateMosPlan.pl patches_download_location

(Windows)
SET PERL5LIB=%APPLICATIONS_BASE%\dbclient\perl\5.8.3;%APPLICATIONS_BASE%\dbclient\perl\site\5.8.3\;%APPLICATIONS_BASE%\dbclient\perl\site
 
%APPLICATIONS_BASE%\dbclient\perl\5.8.3\bin\MSWin32-x64-multi-thread\perl %REPOSITORY_LOCATION%\installers\farup\Disk1\upgrade\bin\adCreateMosPlan.pl patches_download_location

5.3.7 Verify Your OPatch Version

Follow this step only if you have updated OPatch in FA_ORACLE_HOME outside of what Oracle Provisioning and RUP Installer installs.

Oracle Fusion Applications is compatible with a specific version of OPatch instead of the generic version of OPatch. If an incompatible version of OPatch exists in FA_ORACLE_HOME, errors can occur while applying patches and running RUP Installer. The compatible version of Opatch is available on My Oracle Support under patch 14044793.

You can check if a specific file exists, for example, the file, FA_ORACLE_HOME/OPatch/ocm/lib/emocmclnt.jar. If this file exists, then you have an incompatible version of OPatch, and you must contact Oracle Support to fix this issue. On Windows, look for FA_ORACLE_HOME\OPatch\ocm\lib\emocmclnt.jar.

5.3.8 Confirm Memory Settings

Confirm that memory requirements are met on the primordial host that RUP Installer is launched from. The primordial host is where the Administration Server for the Common Domain runs.

RUP Installer requires at least 6GB of free memory on the 64-bit domains to be up during the upgrade. RUP Installer also requires at least 6GB of free memory on the 64-bit primordial host that the installer is launched from, for the duration of the upgrade. This requirement of 6GB of free memory is in addition to the memory requirement for all servers, including the Administration Servers on the primordial host that is already up and running. Oracle also recommends at least 1GB of additional free memory on the primordial host during the upgrade as a safety net.

For example, if the BI domain is provisioned on the primordial host, then RUP Installer requires this 64-bit primordial host to have a minimum of 12GB of RAM. If you have two 64-bit hosts with the BI domain provisioned on a different host from the primordial host, then one host runs the Administration Server and the BI servers, while the other host runs RUP Installer, which requires a connection to the Administration Server that is running. If you run RUP Installer and the Administration Server on the same primordial host with insufficient memory, then the Administration Server and Managed Servers may fail.

5.3.9 Confirm Host Name

For Unix platforms, confirm that the host names are correctly formatted in the /etc/hosts file, and that this file contains entries for all hosts used by Oracle Fusion Applications to ensure that all hosts are visible from the primordial host. The /etc/hosts file is a network configuration file that associates IP addresses with host names and host alias names, if used. Every hosts file should have an entry for the IP address 127.0.0.1, with the name localhost following it.

For more information, see "Edit Host Names (Linux)" in the Oracle Fusion Applications Installation Guide.

For Windows, perform the following steps to confirm the host name:

Right click on the computer name, which is on the desktop.
Click on Properties, then Advanced System Settings, and then Computer Name.
Ensure the entries in C:\Windows\System32\drivers\etc\hosts are correct.

5.3.10 Verify the Local Port Range Value

The recommended local port range value is 32768 61000. If the range is not set properly, a system process could potentially use a port that was assigned to one of the Managed Servers. Since RUP Installer requires all domains to be down, those ports are available for the system to use. The steps to check and modify local port range settings vary by platform. Follow the steps for your platform:

Local Port Range Value for Linux
Local Port Range Value for Oracle Solaris
Local Port Range Value for Windows

5.3.10.1 Local Port Range Value for Linux

Check the local port range value in /proc/sys/net/ipv4/ip_local_port_range before starting the installation.

To set the correct local port range, log in as the root user and run the following command:

echo "32768 61000" > /proc/sys/net/ipv4/ip_local_port_range

5.3.10.2 Local Port Range Value for Oracle Solaris

Perform the following steps for Oracle Solaris:

To view the settings:

/usr/sbin/ndd /dev/tcp tcp_smallest_anon_port tcp_largest_anon_port

To modify the settings:

/usr/sbin/ndd -set /dev/tcp tcp_smallest_anon_port 16202
/usr/sbin/ndd -set /dev/tcp tcp_largest_anon_port 65535

Note that 65535 is the default port for AIX and Solaris.

5.3.10.3 Local Port Range Value for Windows

The default port range for Windows is 49152 through 65535. Use the following command to view the settings:

C:\Users\mwport>Netsh int ipv6 show dynamicport udp

Sample output follows:

Protocol udp Dynamic Port Range
---------------------------------
Start Port      : 49152
Number of Ports : 16384

5.3.11 Confirm Database Settings

Perform the following steps to confirm that your database settings are optimized for the installation:

Refer to Oracle Fusion Applications release notes to verify that your database parameters are set properly to avoid timeout errors during the upgrade.
Confirm that the open file limit is set properly.

RUP Installer uses multiple workers for uploading database content. The number of workers used dictates the open file limit setting for the machine where you run RUP Installer. To understand how the number of workers are calculated and the requirement for the open file limit setting for the workers, see Section 3.1.2, "Patching Database Artifacts". For more information, see "Increase the Open Files Limit" in the Oracle Fusion Applications Installation Guide.
Confirm that the SQL*Net Timeout Configuration is set properly.

The exact setting in your environment depends on your network configuration and machine resources. Refer to "SQLNET.EXPIRE_TIME Parameter" and "INBOUND_CONNECT_TIMEOUT Parameter" in the Oracle Fusion Applications Performance and Tuning Guide to determine the parameters that need to be set.

5.3.12 Confirm All Oracle Homes Are Registered in the Central Inventory

Note:

You must perform this step if you are a freshly provisioned Release 4 (RUP3) customer upgrading to Release 5.

Oracle Provisioning records installation information about the following Oracle homes separately from information about other products: Oracle Business Intelligence (Oracle BI), Oracle Global Order Processing (GOP), Web Tier, and Web Tier Common Oracle home. RUP Installer expects information about all products to be recorded in the same place. To transfer information about the Oracle BI, GOP, and Web Tier installations to the same location as information about other products, perform the following steps. For more information about home directories, see "Provisioned Oracle Fusion Applications Home Directories" in the Oracle Fusion Applications Administrator's Guide.

Verify that the default Inventory Pointer file points to the central inventory on the primordial host on which RUP Installer runs. The default Inventory Pointer is in the following locations:
- Unix: /etc/oraInst.loc
- Solaris: /var/opt/oracle/oraInst.loc
- Windows: located in the registry key, \\HKEY_LOCAL_MACHINE\\Software\Oracle\inst_loc
Note:

If the attachHome command hangs, see Section 5.7.27, "AttachHome Script Hangs".

Run attachHome from the BI Oracle home, for example, APPLICATIONS_BASE/fusionapps/bi.

(Unix) BI_HOME/oui/bin/attachHome.sh -jreLoc JAVA_HOME_LOCATION
(Windows) BI_HOME\oui\bin\attachHome.cmd -jreLoc JAVA_HOME_LOCATION

Run attachHome from the GOP Oracle home, for example, APPLICATIONS_BASE/fusionapps/gop.

(Unix) GOP_HOME/oui/bin/attachHome.sh -jreLoc JAVA_HOME_LOCATION
(Windows) GOP_HOME\oui\bin\attachHome.cmd -jreLoc JAVA_HOME_LOCATION

Run attachHome from the Web Tier Oracle home, for example, APPLICATIONS_BASE/webtier_mwhome/webtier.

(Unix) WEBTIER_HOME/oui/bin/attachHome.sh -jreLoc JAVA_HOME_LOCATION
(Windows) WEBTIER_HOME\oui\bin\attachHome.cmd -jreLoc JAVA_HOME_LOCATION

Run attachHome from the Web Tier Common Oracle home, for example, APPLICATIONS_BASE/webtier_mwhome/oracle_common.

(Unix) WEBTIER_COMMON_HOME/oui/bin/attachHome.sh -jreLoc JAVA_HOME_LOCATION
(Windows) WEBTIER_COMMON_HOME\oui\bin\attachHome.cmd -jreLoc JAVA_HOME_LOCATION

Run attachHome from the Web Tier Webgate Oracle home, for example, APPLICATIONS_BASE/webtier_mwhome/webgate.

(Unix) WEBTIER_WEBGATE_HOME/oui/bin/attachHome.sh -jreLoc JAVA_HOME_LOCATION
(Windows) WEBTIER_WEBGATE_HOME\oui\bin\attachHome.cmd -jreLoc JAVA_HOME_LOCATION

Run attachHome from the Oracle Common Oracle home, for example, APPLICATIONS_BASE/fusionapps/oracle_common.

(Unix) COMMON_HOME/oui/bin/attachHome.sh -jreLoc JAVA_HOME_LOCATION
(Windows) COMMON_HOME\oui\bin\attachHome.cmd -jreLoc JAVA_HOME_LOCATION

Register the dependency between the BI Oracle home and Oracle Common Oracle home. If the runinstaller -updateHomeDeps command hangs, see Section 5.7.28, "The runInstaller.sh -updateHomeDeps Command Hangs".

Run Oracle Universal Installer with the -updateHomeDeps option and pass a dependency list. The syntax for the dependency list is:

HOME_DEPENDENCY_LIST={ORACLE_HOME:DEPENDENT_ORACLE_HOME}

Example for Business Intelligence:

(Unix) BI_HOME/oui/bin/runInstaller -updateHomeDeps "HOME_DEPENDENCY_LIST=
{APPLICATIONS_BASE/fusionapps/bi:APPLICATIONS_BASE/fusionapps/oracle_common}"
-jreLoc JAVA_HOME_LOCATION

(Windows) BI_HOME\oui\bin\setup.exe -updateHomeDeps "HOME_DEPENDENCY_LIST=
{APPLICATIONS_BASE\fusionapps\bi:APPLICATIONS_BASE\fusionapps\oracle_common}"
-jreLoc JAVA_HOME_LOCATION

(Unix) WEBTIER_HOME/oui/bin/runInstaller -updateHomeDeps "HOME_DEPENDENCY_LIST=
{APPLICATIONS_BASE/webtier_mwhome/webtier:APPLICATIONS_BASE/webtier_mwhome/oracle_common}"
-jreLoc JAVA_HOME_LOCATION

(Windows) WEBTIER_HOME\oui\bin\setup.exe -updateHomeDeps "HOME_DEPENDENCY_LIST=
{APPLICATIONS_BASE\webtier_mwhome\webtier:APPLICATIONS_BASE\webtier_mwhome\oracle_common}"
-jreLoc JAVA_HOME_LOCATION

Verify that the central inventory now contains the correct GOP, BI, and Web Tier information. Open the inventory.xml file from the ContentsXML subdirectory in your central inventory directory using a text editor. You can find your central inventory directory by looking in the default Oracle Inventory pointer file mentioned in Step 1. Verify that there are entries for GOP and for BI, and that the BI entry lists the Oracle Common dependency you specified in Step 6. Do the same for Web Tier information. Ensure that you do not modify inventory.xml in any way, as this may corrupt your system.

Example entries in inventory.xml:

<HOME NAME="OH1109401105" LOC="APPLICATIONS_BASE/fusionapps/gop" TYPE="O" IDX="11">
<HOME NAME="OH198367808" LOC="APPLICATIONS_BASE/fusionapps/bi" TYPE="O" IDX="12">
   <DEPHOMELIST>
      <DEPHOME LOC="APPLICATIONS_BASE/fusionapps/oracle_common"/>
   </DEPHOMELIST>
</HOME>
<HOME NAME="OH987588708" LOC="APPLICATIONS_BASE/webtier_mwhome/webtier" TYPE="O" IDX="13">
   <DEPHOMELIST>
      <DEPHOME LOC="APPLICATIONS_BASE/webtier_mwhome/oracle_common"/>
   </DEPHOMELIST>
</HOME>
<HOME NAME="OH1271096710" LOC="APPLICATIONS_BASE/webtier_mwhome/oracle_common" TYPE="O" IDX="14">
   <REFHOMELIST>
      <REFHOME LOC="APPLICATIONS_BASE/webtier_mwhome/webtier"/>
   </REFHOMELIST>
</HOME>

Note:

Rerunning the attachHome command does not cause any issues.

5.3.13 Confirm That JDeveloper Customizations Can Be Merged

If you performed JDeveloper customizations to a SOA composite and then you deployed the composite to the SOA runtime, you must perform manual steps to merge your customizations during the installation. To ensure that your customizations can be merged successfully, review the recommendations in "Merging Runtime Customizations from a Previously Deployed Revision into a New Revision" in the Oracle Fusion Applications Extensibility Guide before you start RUP Installer.

You will merge your customizations after the SOA Preverification configuration task fails during the installation. For more information, see Section 5.7.22, "Merging SOA Composite JDeveloper Customizations During RUP Installation".

5.3.14 Maintain Versions of Customized BI Publisher Reports

Ensure that you have your own versions of any customized BI Publisher reports. If a release includes an update to a catalog object that was delivered with an Oracle Fusion application, RUP Installer will overwrite any customizations applied to the original report. For more information, see "Before You Begin Customizing Reports" in the Oracle Fusion Applications Extensibility Guide.

5.3.15 Validate Domain Directories

If you followed steps to scaleout hosts, you may have added the Administration Server of the scaled out host to a new machine. This section provides the steps to temporarily add the Administration Server back to the originally provisioned machine so that all domain directories can be found by RUP Installer. During post-upgrade steps, you add the Administration Server back to the machine that was created during scaleout.

Perform the following steps to run the validation for domain directories and to temporarily update the machine for Administration Servers, if needed.

Unzip validatedomains.zip into any directory on the primordial host.

Run the validatedomains utility:

(Unix) ./validatedomains.sh APPLICATIONS_BASE
(Windows) validatedomains.bat APPLICATIONS_BASE

If the utility reports any domains that failed the validation, perform the following steps on the Administration Server of each of the reported domains:
1. Log in to the WebLogic console for the domain.
2. Navigate to Environment, then Machines.
3. Find the machine that corresponds to the host_name for which the Administration Server was initially provisioned.
4. Click on the machine and go to the Servers tab. Note that the Administration Server should not appears on the list of servers. If it does appear on the list, either this domain passed validation or this is not the originally provisioned machine for the Administration Server.
5. Click Lock & Edit to make changes.
6. Click Add.
7. Select the AdminServer and click Finish.
8. Click Activate Changes to apply the changes.

5.3.16 Update Oracle Fusion Middleware Schema Credentials

Run the preRupSeeding.py script to perform updates to seed several Oracle Fusion Middleware schema credentials for the schema upgrade. Before you run this script, confirm the following:

The CommonDomain Administration Server is running.
You have the sysdba user name and password for the Oracle Fusion Applications database.
You have the database connect string to the Oracle Fusion Applications database.

Perform the following steps to run the preRupSeeding.py script:

Create the directory FA_ORACLE_HOME/admin/preupg if it does not exist.
Copy the script from REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/bin to FA_ORACLE_HOME/admin/preupg, for example:
```
cp REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/bin/preRupSeeding.py FA_ORACLE_HOME/admin/preupg/
```
Run the utility using following command syntax.
```
(Unix)
$APPLICATIONS_BASE/fusionapps/oracle_common/common/bin/wlst.sh FA_ORACLE_HOME/admin/preupg/preRupSeeding.py 

(Windows)
%APPLICATIONS_BASE%\fusionapps\oracle_common\common\bin\wlst.cmd %REPO_LOCATION%\installers\farup\Disk1\upgrade\bin\preRupSeeding.py
```
This script connects to the Administration Server and prompts you for the following values.
- WLST credentials, including the user name, password and server URL (for example, t3://host_name:7001, for the Common Domain Administration server.
- Oracle Fusion Applications database credentials, including the Oracle Database host name, port number, and sid or service. These values can be found in the DB_CONNECT_STRING row of FA_ORACLE_HOME/admin/FUSION_env.properties.
- SYSDBA user name and password.
- Various schema credentials including:
  - CRM_FUSION_MDS_SOA Schema Owner
  - CRM_FUSION_SOAINFRA Schema Owner
  - FIN_FUSION_MDS_SOA Schema Owner
  - FIN_FUSION_SOAINFRA Schema Owner
  - FUSION_ACTIVITIES Schema Owner
  - FUSION_APM Schema Owner
  - FUSION_BIPLATFORM Schema Owner
  - FUSION_OCSERVER11G Schema Owner
  - FUSION_ORA_ESS Schema Owner
  - FUSION_WEBCENTER Schema Owner
  - HCM_FUSION_MDS_SOA Schema Owner
  - HCM_FUSION_SOAINFRA Schema Owner
  - OIC_FUSION_MDS_SOA Schema Owner
  - OIC_FUSION_SOAINFRA Schema Owner
  - PRC_FUSION_MDS_SOA Schema Owner
  - PRC_FUSION_SOAINFRA Schema Owner
  - PRJ_FUSION_MDS_SOA Schema Owner
  - PRJ_FUSION_SOAINFRA Schema Owner
  - SCM_FUSION_MDS_SOA Schema Owner
  - SCM_FUSION_SOAINFRA Schema Owner
  - SEARCHSYS Schema Owner
  - SETUP_FUSION_SOAINFRA Schema Owner

5.3.17 Verify the Default Realm Name is myrealm

RUP Installer expects the default realm name to be myrealm for the Common Domain. Verify that you have not changed this value to any other name, because changing the name to anything other than myrealm causes RUP Installer to fail. Log in to the WLS Console for the Common Domain and click Security Realms on the domain structure pane. A list of realms displays, where you can verify that there is an entry for myrealm and that it is the default realm.

5.3.18 Verify the OHS Instance Is Registered (Oracle VM Hosts Only)

Follow the steps in this section only if all of the following requirements apply to your applications OHS environment:

You are running Oracle Fusion Applications in an Oracle VM environment.
You initially provisioned Oracle Fusion Applications with Release 4 (RUP3).
You are upgrading to Release 5.

Verify that opmn and server components are registered with the Administration Server of the Common Domain. You can verify this by reviewing the <ias-instance> element in the topology.xml file. There should be an entry for the server instance with <ias-instance> in this file. You can view the topology file at this location: COMMON_DOMAIN_HOME/opmn/topology.xml. Registration is typically done when setting up the environment.

The entry should be similar to the following example:

<topology xmlns='http://www.oracle.com/fmw-nonj2ee-topology'>
   <ias-instance id="CommonDomain_webtier" oracle-home="APPLICATIONS_BASE\
 webtier_mwhome\webtier "
 instance-home="APPLICATIONS_CONFIG\CommonDomain_webtier" host="<hostname>"
 port="<port_number>">
     <ias-component id="ohs1" type="OHS"
 mbean-class-name="oracle.ohs.OHSGlobalConfig"
 mbean-interface-name="oracle.ohs.OHSGlobalConfigMXBean"
 port="="<port_number>">
       <properties>
         <property name="ORACLE_HOME" value=" APPLICATIONS_BASE\
 webtier_mwhome\webtier "/>
         <property name="INSTANCE_HOME" value="
 APPLICATIONS_CONFIG\CommonDomain_webtier"/>
         <property name="ComponentType" value="ohs"/>
       </properties>
       <em-properties>
         <property name="EMTargetType" value="oracle_apache"/>
         <property name="ProxyMBeanObjectName"
 value="oracle.as.management.mbeans.register:type=component,name=ohs1,instance=
 CommonDomain_webtier"/>
         <property name="version" value="11.1.1.6.0"/>
       </em-properties>
     </ias-component>
   </ias-instance>
</topology>

If this entry is not present in your file or opmn/topology.xml is not available, run the following command to register the OHS Instance:

APPLICATIONS_CONFIG/CommonDomain_webtier/bin/opmnctl registerinstance -adminHost admin_host_name -adminPort admin_port -adminUsername admin_username

5.3.19 Save WebLogic Configuration Changes

RUP Installer makes WebLogic configuration changes using WLST, which may overwrite any unsaved changes. Ensure that any pending WebLogic configuration changes are either activated or discarded. For more information, see "Configuring Existing WebLogic Domains" in Oracle Fusion Middleware Oracle WebLogic Scripting Tool.

5.3.20 Run Health Checker

Health Checker is a command line utility that assists you in confirming that your system is in a state that would allow RUP Installer to run successfully. This utility is delivered in the REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/bin directory as hcplug.sh and hcplug.cmd. In Release 5, run Health Checker for IDM setup and to check DBMS_STATS.

If the Health Checker utility fails, see Section 5.7.26, "Troubleshooting Health Checker".

Before running Health Checker, ensure that you set the environment variables, as described in Section 5.3.4, "Set Environment Variables"

5.3.20.1 Run Health Checker for IDM Setup

Health Checker for IDM Setup validates that the cn=PolicyRWUser user is part of cn=DirectoryAdminGroup.

Run Health Checker for IDM Setup from the primordial host using the following command syntax. Primordial host is defined in Section 5.3.1, "Before You Begin".

$REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/bin/hcplug.sh -manifest 
$REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/config/idmrupautomation_plugin.xml 
-properties APPLICATIONS_BASE/fusionapps/applications/admin/FUSION_env.properties
[-recover] [-DlogLevel=log_level]

If the cn=PolicyRWUser user is not part of cn=DirectoryAdminGroup, validation fails with the following error message:

User 'cn=PolicyRWUser' is not member of cn=DirectoryAdminGroup

To resolve this issue, verify that the following credentials are present in ODSM by performing the following steps:

Log in to Oracle Internet Directory using ODSM: http://ldap_host:port/odsm, for example, http://IDM_HOST:7005/odsm. (Note that you cannot do this using jexplorer.)
Connect to a directory. Use the OID-OID connection, for example, where the User name is cn=orcladmin and the Password is password.
Go to the Data Browser tab. Go to the cn=oracle internet directory and within the cn=oracle internet directory, go to cn=DirectoryAdminGroup.
Verify that the following user entry is present in the Members section:
```
cn=PolicyRWUser,cn=users,dc=us,dc=oracle,dc=com
```
Note the value of cn is not case sensitive.
If the entry is not present, click the add [+] button in the Members section and add the entry. Then apply the changes.

5.3.20.2 Run Health Checker for DBMS Stats

Health Checker for DBMS Stats confirms whether DBMS_STATS has recently been run on the MDS schema in the Oracle Fusion Applications database. Run the following command from the primordial host to determine the schemas for which schema statistics need to be gathered:

$REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/bin/hcplug.sh -manifest 
$REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/config/sql_plugin.xml 
-properties APPLICATIONS_BASE/fusionapps/applications/admin/FUSION_env.properties
[-recover] [-DlogLevel=log_level]

Run DBMS_STATS on any schemas that are returned by the preceding command. This step optimizes the performance of starting servers.

For more information, see "Collecting Optimizer Statistics" in the Oracle Fusion Applications Administrator's Guide.

Then follow the steps in "Configuring Oracle Metadata Services" in the "Common" chapter of the Oracle Fusion Applications Post-Installation Guide.

Note:

For the Windows platform only, instead of running Health Checker for DBMS Stats, you must manually confirm that DBMS_STATS has recently been run on the MDS schema in the Oracle Fusion Applications database.

5.3.21 Run Script for DatabaseItemSD.xml

Run the following script as the FUSION user to prevent a failure during the upload of seed data in the file, DatabaseItemSD.xml.

update ff_database_items_b set user_entity_id =
  (select user_entity_id from ff_user_entities_vl 
   where base_user_entity_name = 'PER_ASG_PERSON_DETAILS_UE') 
 where base_user_name = 'PER_ASG_LEGISLATION_CODE'; 
commit;

5.3.22 Verify Ownership and Permissions on Domains

Verify that all files under the APPLICATIONS_CONFIG directory are owned and readable by the Operating System user running the upgrade.

5.3.23 Platform Specific Steps

The following steps must be performed for specific non-Linux platforms:

Add -d64 Option to JRE_MEMORY_OPTIONS (Solaris x64 and Solaris Sparc)
Update Permission of the oraInst.loc File to Read-only Mode (Solaris x86)
Set the Value for the SKIP_ROOTPRE Environment Variable (AIX)
Applying Patches to the ATGPF and Secure Enterprise Search Components (Solaris)

5.3.23.1 Add -d64 Option to JRE_MEMORY_OPTIONS (Solaris x64 and Solaris Sparc)

Add the -d64 option to JRE_MEMORY_OPTIONS in the following file:

APPLICATIONS_BASE/fusionapps/applications/oui/oraparam.ini

Adding this option prevents OPatch from failing with this error:

APPLICATIONS_BASE/fusionapps/applications/oui/lib/intelsolaris/liboraInstaller.so:
wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch)

5.3.23.2 Update Permission of the oraInst.loc File to Read-only Mode (Solaris x86)

On Oracle Solaris on x86-64 (64-bit) systems, change the permission of the oraInst.loc file to Read-only mode before starting RUP Installer. This will prevent a failure during the Database Content Upload step of the Offline Preverification configuration task.

5.3.23.3 Set the Value for the SKIP_ROOTPRE Environment Variable (AIX)

On IBM AIX on POWER Systems (64-bit), set the value for the SKIP_ROOTPRE environment variable as follows:

setenv SKIP_ROOTPRE=TRUE

This prevents an Oracle Web Tier installation failure.

5.3.23.4 Applying Patches to the ATGPF and Secure Enterprise Search Components (Solaris)

When applying patches to the ATGPF or SES component on Oracle Solaris systems, the following warning message is seen in the runProvisioning-install.log file for the Opatch utility:

-d64: not found

You can ignore this error message, or use the Opatch utility that is located in the fusionapps/applications directory.

Set the PATH environment variable to point to the Opatch utility that is located in the APPLICATIONS_BASE/fusionapps/applications/OPatch directory and run the OPatch command to apply the patches.

5.4 Prepare to Upgrade - During Down Time

This section describes the following preparation steps for upgrading to Release 5, all of which must be performed during your system down time.

Stop Index Schedules and Deactivate Index Optimization
Upgrade Oracle Identity Management Domain to 11g Release 5 (11.1.5)
Apply Mandatory Prerequisite RDBMS Patches
Run "catmetx.sql"
Verify the Status of Servers and Processes
Perform Required Backups
Remove Conflicting Patches From the Primordial Host
Enable Anonymous Binds in Oracle Internet Directory
Run the Inventory Cleanup Script
Upgrade JDK (Linux and Windows Platforms Only)
Run RUP Lite for OVM - Offline (Oracle VM Hosts Only)
Confirm the OPSS Security Store is Running
Start Servers That Were Added After Provisioning

5.4.1 Stop Index Schedules and Deactivate Index Optimization

This step is run by a shell script, runSESDisableIndexOptimizer.sh (runSESDisableIndexOptimizer.bat for Windows), located in the REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/bin directory. The script calls the Oracle Secure Enterprise Search (Oracle SES) searchadmin utility in order to stop Index Schedules that have one of the following statuses: LAUNCHING, EXECUTING, STOPPING, or RUNNING. After all Index Schedules have been stopped, Index Optimization is disabled.

Ensure the environment variables described in Section 5.3.4, "Set Environment Variables" are set and then run the script from the primordial host. Primordial host is define in Section 5.3.1, "Before You Begin".

Use the following command syntax:

(Unix)
setenv JAVA_HOME JAVA_HOME_location
$REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/bin/runSESDisableIndexOptimizer.sh

(Windows)
set JAVA_HOME=JAVA_HOME_location
%REPOSITORY_LOCATION%\installers\farup\Disk1\upgrade\bin\runSESDisableIndexOptimizer.bat

5.4.2 Verify the Status of Servers and Processes

This section contains steps to follow for all platforms. For Windows platforms, also follow the steps in Section 5.4.2.8, "Steps for Windows Platform". To prevent locks on patched objects and other data issues during patching, review and perform the tasks in this section.

5.4.2.1 Stop All Servers

Stop all servers and processes (including BI Presentation Servers), except the OPSS Security Store and the database, before starting the installation. If you want to use the fastartstop utility to do this, see "Understand the Starting and Stopping with the fastartstop Utility" in the Oracle Fusion Applications Administrator's Guide.

5.4.2.2 Update "CrashRecoveryEnabled" Property to False

If you successfully completed the steps in Section 5.4.2.1, "Stop All Servers" and all servers were cleanly shut down, then you can skip this step.

If servers were not cleanly shut down, update the CrashRecoveryEnabled property in nodemanager.properties to "false" for all hosts. The nodemanager.properties file exists in the following location:

APPLICATIONS_BASE/fusionapps/wlserver_10.3/common/nodemanager/host/nodemanager.properties

Note that there may be an extra nodemanager.properties file in the APPLICATIONS_BASE/fusionapps/wlserver_10.3/common/nodemanager/nodemanager.properties directory. This file is not used and can be ignored.

5.4.2.3 Stop the Node Manager and the OPMN Control Process

Stop the Node Manager and the OPMN control process. All OHS and Web Tier processes, including the Apache processes, must also be stopped if you are not running OHS from a separate installation (DMZ or otherwise). (On Windows, stop the Node Manager and OPMN services and follow steps 1 and 2 in Section 5.4.2.8, "Steps for Windows Platform".) Note that you must start the Node Manager for all domains and the OPMN control process after the first installer completes successfully and before proceeding to the steps in the second installer.

For more information, see "Stopping Node Manager" in Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.

Use the following procedure to stop the OPMN control processes for Oracle Business Intelligence, GOP, and Web Tier (OHS). This procedure also stops all BI server processes, all GOP processes, and the OHS process.

Note:

There should be no Web Tier processes on this installation if you are running OHS from a separate installation (DMZ or otherwise). In this case, you do not need to stop the Web Tier processes.

Set ORACLE_INSTANCE to the location of the target Oracle instance directory.
Go to the bin directory under the target Oracle instance directory.
Run the opmnctl program from the current directory with the stopall command.

The following example is for Oracle Business Intelligence, where BIInstance is the location of BIInstance. Depending on whether Local Application Config is enabled for your setup, BIInstance is located under either the Application Config directory or the Local Application Config directory of the BI host.

(Unix) setenv INSTANCE_HOME APPLICATIONS_CONFIG/BIInstance
cd $ORACLE_INSTANCE/bin
./opmnctl stopall

(Windows) set INSTANCE_HOME=APPLICATIONS_CONFIG\BIInstance
cd $ORACLE_INSTANCE\bin
.\opmnctl stopall

Example for GOP:

(Unix) setenv ORACLE_INSTANCE APPLICATIONS_CONFIG/gop_1
cd $ORACLE_INSTANCE/bin
./opmnctl stopall

(Windows) set INSTANCE_HOME=APPLICATIONS_CONFIG\gop_1
cd $ORACLE_INSTANCE\bin
.\opmnctl stopall

Example for Web Tier (OHS):

(Unix) setenv INSTANCE_HOME=APPLICATIONS_CONFIG/CommonDomain_webtier
cd $ORACLE_INSTANCE/bin
./opmnctl stopall

(Windows) set INSTANCE_HOME=APPLICATIONS_CONFIG\CommonDomain_webtier
cd $ORACLE_INSTANCE\bin
.\opmnctl stopall

For more information about the location of APPLICATIONS_CONFIG, see Section 5.3.1, "Before You Begin".

For more information about concepts related to INSTANCE_HOME and ORACLE_INSTANCE, refer to the "Understanding Oracle Fusion Middleware Concepts" chapter in the Oracle Fusion Middleware Administrator's Guide.

5.4.2.4 Confirm the Database is Running and in Idle State

Confirm there are no active jobs or processes running against the database. If you stop all servers, including ESS servers, most Oracle Fusion Applications processes are shut down. However, some database jobs could still be running or scheduled to start. These processes must be stopped so that they do not start while patching is in progress. Stop all background jobs, including jobs in the database and active processes.

To confirm if the database is running in idle mode, you can follow the steps below:

Start SQL*Plus and connect as the SYS user and run the following SQL*Plus queries.

To retrieve a list of active SQL processes:

select a.sid, a.serial#, b.sql_text
from v$session a, v$sqlarea b
where a.sql_address=b.address
and a.username in ('FUSION', 'FUSION_RUNTIME')
and a.sid <> sys_context('USERENV', 'SID');

To retrieve a list of scheduler jobs that are currently running:
```
select owner, job_name
from dba_scheduler_running_jobs;
```

To retrieve a list of scheduled jobs for the next 24 hours:

select owner, job_name from dba_scheduler_jobs
where state = 'SCHEDULED' and next_run_date
between sysdate and sysdate+1;

If all the queries return no rows, that indicates the database is in idle mode for the next 24 hours and you can safely proceed with the upgrade.

5.4.2.5 Confirm All Oracle Fusion Applications Patch Manager Processes Are Complete

From your operating system, check for processes that are running fapmgr, javaworker, adpatch, adadmin, and adworker. If an fapmgr session was interrupted, you may need to forcefail and abandon the session as follows:

Use the fapmgr forcefail command to update the patching tables.

(UNIX) FA_ORACLE_HOME/lcm/ad/bin/fapmgr.sh forcefail [-logfile log file name] [-loglevel level]

(Windows) FA_ORACLE_HOME\lcm\ad\bin\fapmgr.cmd forcefail [-logfile log file name] [-loglevel level]

Use the fapmgr abort command to abandon the session.

(UNIX) FA_ORACLE_HOME/lcm/ad/bin/fapmgr.sh abort [-logfile log file name] [-loglevel level]

(Windows) FA_ORACLE_HOME/lcm\ad\bin\fapmgr.cmd abort [-logfile log file name] [-loglevel level]

5.4.2.6 Confirm All Oracle Fusion Applications AutoPatch Processes Are Complete

If an AutoPatch session is running, you must abandon the session as follows.

Run the following command from ATGPF_ORACLE_HOME: (This is the directory under MW_HOME that contains the Applications Core code. For more information, see Section 7.1.2, "Running Oracle Fusion Applications AutoPatch".)

(Unix) lcm/ad/bin/adpatch.sh abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME/admin/TWO_TASK/defaults.txt logfile=logfile_name.log

(Windows) lcm\ad\bin\adpatch.cmd abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME\admin\LOCAL\defaults.txt logfile=logfile_name.log

The TWO_TASK value can be obtained from the ATGPF_env.properties file.

The LOCAL value can be obtained from the FUSION_env.properties file.

5.4.2.7 Confirm All AD Administration Sessions Are Complete

If an AD Administration session is running, you must abandon the session as follows:

From FA_ORACLE_HOME:

(Unix) lcm/ad/bin/adadmin.sh abandon=y interactive=n defaultsfile=FA_ORACLE_HOME/admin/TWO_TASK/defaults.txt logfile=log_file_name

(Windows) lcm\ad\bin\adadmin.cmd abandon=y interactive=n defaultsfile=FA_ORACLE_HOME\admin\LOCAL\defaults.txt logfile=log_file_name

The TWO_TASK and LOCAL values can be obtained from the FUSION_env.properties file.

From ATGPF_ORACLE_HOME

(Unix) lcm/ad/bin/adadmin.sh abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME/admin/TWO_TASK/defaults.txt logfile=log_file_name

(Windows) lcm\ad\bin\adadmin.cmd abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME\admin\LOCAL\defaults.txt logfile=log_file_name

The TWO_TASK and LOCAL values can be obtained from the ATGPF_env.properties file.

5.4.2.8 Steps for Windows Platform

Follow these steps before running RUP Installer on Windows platform.

Change the service type from Automatic to Manual for the following services: Node Manager, Web Tier, GOP, and BI. Restore the service type back to Automatic after the installation completes.
Stop the following services: Node Manager, Web Tier, GOP, and BI.
Reboot the Oracle Fusion Applications host.
Release Java Archive File Handles on System Process ID (PID) 4.

On the Windows WebLogic Server, the Node Manager runs as a service. Since the APPLICATIONS_BASE of Oracle Fusion Applications is in a symbolic folder, some of the jar file handles are loaded by Microsoft Windows System Process ID (PID) 4. The loaded file handles eventually cause Middleware patch application to fail when running RUP Installer. Before starting RUP Installer, make sure the Windows System Process ID (PID) 4 does not have handles to Oracle Fusion Applications jar files.

Check for file handles using the Windows utility Process Explorer. If file handles exist, make sure the Node Manager service is not running. If the file handles remain even after shutting down the Node Manager service, switch the Node Manager service from Automatic to Manual and reboot the machine to release the file handles.
Ensure that the Server service is up and running.
Increase the shared_pool_size in the init.ora file. If it seems large enough then improve segmentation in the shared pool by reserving part of the shared pool for large objects using the SHARED_POOL_RESERVED_SIZE parameter. The recommended value to start tuning is one third of the shared pool size. You can allow for large objects by using the SHARED_POOL_RESERVED_MIN_ALLOC parameter.

5.4.3 Upgrade Oracle Identity Management Domain to 11g Release 5 (11.1.5)

To upgrade the Oracle Identity Management domain to 11g Release 5 (11.1.5), perform the steps in all sections in this topic.

This topic includes the following sections:

Before Upgrading the Oracle Identity Management Domain
Verify Environment Status
Stop Services and Processes
Remove Conflicting IDM Patches
Create Backups
Download Required Patches
Upgrade the IDM Node
Upgrade the IAM Node
Upgrade the OHS Node
Upgrade Oracle _Common Home on All Nodes
Examine Oracle Fusion Applications Release Notes for Possible Required Updates
Start the Servers and Processes
Execute the patch_oim_wls Script
Verify the Oracle Identity Management Domain

Note:

The information in this topic includes example commands based on UNIX platforms. Be sure to adjust the example commands so they are specific to your platform.

5.4.3.1 Before Upgrading the Oracle Identity Management Domain

Before you start upgrading the Oracle Identity Management domain to 11g Release 5 (11.1.5), Oracle recommends first reading the following sections:

Upgrade Requirements
Understanding the Oracle Identity Management Domain
Related Documents

5.4.3.1.1 Upgrade Requirements

To upgrade the Oracle Identity Management domain to 11g Release 5 (11.1.5), your current environment must meet the following requirements:

Oracle Fusion Applications 11g Release 1 (11.1.4) and the equivalent Oracle Identity Management components are installed.
The patches described in Oracle Support Note 1455116.1 have been applied to the Oracle Identity Management components in your existing 11g Release 1 (11.1.4) environment. You can access Oracle Support Note 1455116.1 at My Oracle Support: https://support.oracle.com

5.4.3.1.2 Understanding the Oracle Identity Management Domain

A typical Oracle Identity Management domain includes the following nodes:

Oracle Identity Management (IDM) node: Table 5-5 lists the Oracle homes and products in the IDM Node.
Oracle Identity and Access Management (IAM) node: Table 5-6 lists the Oracle homes and products in the IAM Node.
Oracle HTTP Server (OHS) node: Table 5-7 lists the Oracle homes and products in the OHS Node.

Table 5-5 IDM Node

Oracle Home	Products in the Oracle Home
IDM_ORACLE_HOME Also known as the OID_ORACLE_HOME.	Oracle Internet Directory Oracle Virtual Directory Oracle Directory Services Manager
IDM_ORACLE_COMMON_HOME Typically exists at the same directory level as the IDM_ORACLE_HOME.	Oracle Platform Security Services Oracle Web Services Manager

Oracle Home

Products in the Oracle Home

IDM_ORACLE_HOME

Also known as the OID_ORACLE_HOME.

Oracle Internet Directory
Oracle Virtual Directory
Oracle Directory Services Manager

IDM_ORACLE_COMMON_HOME

Typically exists at the same directory level as the IDM_ORACLE_HOME.

Oracle Platform Security Services
Oracle Web Services Manager

Table 5-6 IAM Node

Oracle Home	Products in the Oracle Home
IAM_ORACLE_HOME Also known as the OIM_ORACLE_HOME.	Oracle Identity Manager Oracle Access Manager Oracle IDM Tools Oracle Identity Federation
IAM_ORACLE_COMMON_HOME Typically exists at the same directory level as the IAM_ORACLE_HOME.	Oracle Platform Security Services Oracle Web Services Manager
SOA_ORACLE_HOME Typically exists at the same directory level as the IAM_ORACLE_HOME.	Oracle SOA Suite

Oracle Home

Products in the Oracle Home

IAM_ORACLE_HOME

Also known as the OIM_ORACLE_HOME.

Oracle Identity Manager
Oracle Access Manager
Oracle IDM Tools
Oracle Identity Federation

IAM_ORACLE_COMMON_HOME

Typically exists at the same directory level as the IAM_ORACLE_HOME.

Oracle Platform Security Services
Oracle Web Services Manager

SOA_ORACLE_HOME

Typically exists at the same directory level as the IAM_ORACLE_HOME.

Oracle SOA Suite

Table 5-7 OHS Node

Oracle Home	Products in the Oracle Home
OHS_ORACLE_HOME Also known as the WEB_ORACLE_HOME.	Oracle HTTP Server
OHS_WEBGATE_ORACLE_HOME	Oracle Access Manager WebGate
OHS_ORACLE_COMMON_HOME Typically exists at the same directory level as the OHS_ORACLE_HOME.	Oracle Platform Security Services Oracle Web Services Manager

Oracle Home

Products in the Oracle Home

OHS_ORACLE_HOME

Also known as the WEB_ORACLE_HOME.

Oracle HTTP Server

OHS_WEBGATE_ORACLE_HOME

Oracle Access Manager WebGate

OHS_ORACLE_COMMON_HOME

Typically exists at the same directory level as the OHS_ORACLE_HOME.

Oracle Platform Security Services
Oracle Web Services Manager

5.4.3.1.3 Related Documents

This topic is the primary source of information for upgrading the Oracle Identity Management domain to 11g Release 5 (11.1.5). However, documents in the Oracle Fusion Applications Technology Library for 11g Release 5 (11.1.5) and the Oracle Fusion Middleware Documentation Library for 11g Release 1 (11.1.1.6) can help you while upgrading the Oracle Identity Management domain to 11g Release 5 (11.1.5).

Oracle Fusion Applications 11g Release 5 (11.1.5) Documents

The following is a list of documents in the Oracle Fusion Applications Technology Library for 11g Release 5 (11.1.5) that will help you while upgrading the Oracle Identity Management domain to 11g Release 5 (11.1.5):

Oracle Fusion Applications Release Notes
Oracle Fusion Applications Patching Guide
Oracle Fusion Applications Administrator's Guide
Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition)

Oracle Fusion Middleware Documents for 11g Release 1 (11.1.1.6)

You can access the Oracle Fusion Middleware Documentation Library for 11g Release 1 (11.1.1.6) on the Oracle Technology Network (OTN) web site:

http://www.oracle.com/technetwork/index.html

The following is a list of documents in the Oracle Fusion Middleware Documentation Library for 11g Release 1 (11.1.1.6) that will help you while upgrading to 11g Release 5 (11.1.5):

Oracle Fusion Middleware Patching Guide
Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management
Oracle Fusion Middleware Upgrade and Migration Guide for Oracle Identity and Access Management
Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server for 11g Release 1 (10.3.6)
Oracle Fusion Middleware Security and Administrator's Guide for Web Services
Oracle Fusion Middleware Application Security Guide

5.4.3.2 Verify Environment Status

To verify the status of your existing 11g Release 1 (11.1.4) environment:

Verify Oracle Identity Management components are at 11g Release 1 (11.1.4) level and operating properly. Specifically, verify Oracle Identity Manager and Oracle Access Manager are operating properly, and the Policy Store is running.
Verify Oracle Fusion Applications components are at 11g Release 1 (11.1.4) level and operating properly. Specifically, verify Oracle Fusion Applications components are redirecting to Oracle Identity Management for Single Sign-On (SSO) and user provisioning.

5.4.3.3 Stop Services and Processes

Stop existing services and processes as follows:

Stop all servers and processes in the Oracle Fusion Applications domain—do not stop the Oracle Platform Security Services Security Store and the database. For more information, see "Starting and Stopping" in the Oracle Fusion Applications Administrator's Guide.
Stop all Oracle BI presentation servers.
Stop the Oracle Enterprise Scheduler Service (ESS) server by performing the following steps:
1. Stop the ESS request processor and dispatcher to prevent new requests from being processed. For more information, see "Starting and Stopping Oracle Enterprise Scheduler Service Components" in the Oracle Fusion Applications Administrator's Guide.
2. Cancel any in-progress requests. For more information, see "Cancelling Oracle Enterprise Scheduling Service Job Requests" in the Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Scheduler.
3. Shutdown the ESS WebLogic Server Managed server. For more information, see "Starting and Stopping" in the Oracle Fusion Applications Administrator's Guide.
Stop all services and processes in the Oracle Identity Management domain using the following sequence. Do not stop the database.

Note:

Refer to the "Starting and Stopping Oracle Identity Management Components" section in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition) for specific commands for stopping components.
1. Stop Oracle HTTP Server.
2. Stop Oracle Identity Manager managed servers.
3. Stop Oracle SOA managed servers.
4. Stop Oracle Identity Federation managed servers.
5. Stop Oracle Access Manager managed servers.
6. Stop Oracle Directory Services Manager.
7. Stop the Oracle WebLogic Administration Server for the Oracle Identity Management domain.
8. Stop Oracle Virtual Directory.
9. Stop Oracle Internet Directory.

5.4.3.4 Remove Conflicting IDM Patches

Follow the steps in the README.txt file of patch 14543240 to run the script to remove conflicting patches on the IDM host. You downloaded patch 14543240 in Section 5.3.5, "Find Conflicting Patches". You must run this script on all IDM nodes.

Note:

Ensure that you run this script only before upgrading. If you run this script at any time other than before upgrading, the system may be left in an unstable state.

5.4.3.5 Create Backups

At a minimum, create the following backups. In addition to the following backups, Oracle recommends performing your organization's typical backup processes.

Note:

For detailed information about creating the backups, refer to the following sections in the Oracle Fusion Middleware Patching Guide:

"Backing Up Your Middleware Home, Domain Home and Oracle Instances"
"Backing Up Your Database and Database Schemas"
"Backing Up Additional Configuration Information"

You can access this document in the Oracle Fusion Middleware Documentation Library on the Oracle Technology Network (OTN): http://www.oracle.com/technetwork/index.html

Stop all servers and processes (including OPMN) on all machines that are part of any domain used from the Middleware home.
Create backups for your:
- Middleware home directory (including the Oracle home directories inside the Middleware home)
- Local domain home directory
- Local Oracle instances
- Domain home and Oracle instances on any remote systems that use the Middleware home
Back up your database and ensure the backup includes the schema version registry table, as each Fusion Middleware schema has a row in this table. The name of the schema version registry table is SYSTEM.SCHEMA_VERSION_REGISTRY$.
Back up your Configurations and Stores—specifically, all data under the root node of the LDAP store.
Back up any Oracle Identity Federation Java Server Pages (JSP) that you customized.

Note:

The patching process overwrites JSPs included in the oif.ear file. After you complete the patching process, restore your custom JSPs.

5.4.3.6 Download Required Patches

To download the required patches:

Create directories for the patches and libraries. For example:

mkdir /u01/patches/oracle_common
mkdir /u01/patches/pltsec
mkdir /u01/patches/idm
mkdir /u01/patches/webgate

Set the OPatch directory in your PATH. For example:
```
setenv PATH /u01/oim/oracle_common/OPatch:$PATH
```

Download the patches listed in Table 5-8 from My Oracle Support and unpackage each patch file. You can access My Oracle Support at: https://support.oracle.com.

Table 5-8 Required Patches, By Node

Node	Patch
IDM Node	Patch 14034245 for Oracle Virtual Directory On Microsoft Windows platforms, Patch 14297670 for Oracle Internet Directory. On UNIX-based platforms, Patch 14178750 for Oracle Identity Directory. On UNIX-based platforms only—Patch 14249414 for Oracle Internet Directory
IAM Node	Patch 14179564 for IDMTools Patch 14171065 for Oracle Access Manager Patch 14193741 for Oracle Identity Manager Patch 14248646 for IDMScripts Patch 13897549 for Oracle SOA Plugin Patch 14246779 for Oracle SOA
OHS Node	Patch 14329669 for Oracle Access Manager Webgate Patch 14264658 for Oracle HTTP Server (OHS) Patch 13897557 for OHS Plug-in fixes for T2P
All Nodes, apply to Common Oracle Home	Patch 14054792 for Oracle Virtual Directory Library (libOVD) Patch 14222702 for Oracle Platform Security Services Patch 13511837 for Oracle XML SQL Utility Patch 13897534 for Oracle Fusion Middleware Patch 14246779 for Oracle SOA Patch 14099904 for HTTP Client Patch 14109342 for Web Services Patch 14226604 for Web Center Patch 14326776 for Oracle Fusion Middleware Diagnostics Patch 14228599 for Oracle Access Manager Patch 14247121 for Oracle Identity Directory ClientTool Patch 14296054 for ADF Shared Components Patch 14051044 for Oracle Web Services Manager

5.4.3.7 Upgrade the IDM Node

To patch and upgrade the IDM node:

If your Oracle Internet Directory must run on a privileged port (such as 389, 636), log in as root and run the OID_ORACLE_HOME/oidRoot.sh script.
Apply patch 14034245 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/pltsec/14034245 
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oid_home
opatch apply
```
Apply patch 14297670 or patch 14178750 (depending on your platform) by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file. For example:
```
cd /u01/patches/pltsec/14178750
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oid_home
opatch apply
```
On UNIX-based platforms only—apply patch 14249414 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/pltsec/14249414
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oid_home
opatch apply
```

5.4.3.8 Upgrade the IAM Node

To patch and upgrade the IAM node:

Apply patch 14179564 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/idm/14179564
```
2. Set your ORACLE_HOME environment variable to IAM_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oim/oim_home
opatch apply
```
Apply patch 14171065 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/idm/14171065
```
2. Set your ORACLE_HOME environment variable to IAM_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oim/oim_home
opatch apply
```
Apply patch 14193741 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/idm/14193741
```
2. Set your ORACLE_HOME environment variable to IAM_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oim/oim_home
opatch apply
```
Apply patch 14248646 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/idm/14248646
```
2. Set your ORACLE_HOME environment variable to IAM_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oim/oim_home
opatch apply
```
Apply patch 13897549 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/idm/13897549
```
2. Set your ORACLE_HOME environment variable to SOA_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oim/oim_home
opatch apply
```
Apply patch 14246779 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/idm/14246779
```
2. Set your ORACLE_HOME environment variable to SOA_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oim/oim_home
opatch apply
```

5.4.3.9 Upgrade the OHS Node

To patch and upgrade the OHS node:

Apply patch 14329669 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/webgate/14329669
```
2. Set your ORACLE_HOME environment variable to OHS_WEBGATE_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/ohsauth/oracle_common
opatch apply
```
Apply patch 14264658 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/webgate/14264658
```
2. Set your ORACLE_HOME environment variable to OHS_WEBGATE_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/ohsauth/oracle_common
opatch apply
```
Apply patch 13897557 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/webgate/13897557
```
2. Set your ORACLE_HOME environment variable to OHS_WEBGATE_ORACLE_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/ohsauth/oracle_common
opatch apply
```

5.4.3.10 Upgrade Oracle _Common Home on All Nodes

To patch and upgrade the Oracle_Common Home, apply the following patches to the oracle_common Home directory on all nodes.

Note:

You must apply the patches to oracle_common Home on the IDM Node, IAM Node, and OHS Node.

Apply patch 14054792 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14054792 
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14222702 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14222702
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 13511837 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/13511837
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 13897534 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/13897534
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14246779 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14246779
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14099904 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14099904
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14109342 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14109342
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14226604 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14226604
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14326776 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14326776
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14228599 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14228599
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14247121 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14247121
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14296054 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14296054
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```
Apply patch 14051044 by performing the following steps:
1. Change to the directory where you downloaded the patch. Oracle recommends reviewing the patch README file.
```
cd /u01/patches/oracle_common/14051044
```
2. Set your ORACLE_HOME environment variable to IDM_ORACLE_COMMON_HOME and apply the patch. For example:
```
setenv ORACLE_HOME /u01/oid/oracle_common
opatch apply
```

5.4.3.11 Examine Oracle Fusion Applications Release Notes for Possible Required Updates

The Oracle Fusion Applications Release Notes document contains the most recent information about any particular Oracle Fusion Applications release. If additional patches or steps are required to perform a task, such as upgrading to 11g Release 5 (11.1.5), the Oracle Fusion Applications Release Notes will describe them.

You must examine the Oracle Fusion Applications Release Notes for Oracle Fusion Applications 11g Release 5 (11.1.5) to ensure no additional patches or steps are required when upgrading. If additional steps for upgrading to 11g Release 5 (11.1.5) are listed in the Release Notes, perform them now before proceeding to "Start the Servers and Processes."

5.4.3.12 Start the Servers and Processes

Start servers and processes in the following sequence:

Note:

Refer to the "Starting and Stopping Oracle Identity Management Components" section in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition) for specific commands for starting components.

You can access this document in the Oracle Fusion Applications Technology Library on the Oracle Technology Network (OTN): http://www.oracle.com/technetwork/index.html

Start Oracle Internet Directory.
Start Oracle Virtual Directory.
Start the Oracle WebLogic Administrative Server for the IDM node.
Start Oracle Directory Services Manager managed servers.
Start Oracle Access Manager managed servers.
Start Oracle Identity Federation managed servers.
Start Oracle SOA managed servers.
Start Oracle Identity Manager managed servers.
Start Oracle HTTP Server and Webgate.

5.4.3.13 Execute the patch_oim_wls Script

On the IAM node, where you applied Patch 14193741 for Oracle Identity Manager, you must execute the patch_oim_wls script as follows:

Change to the ORACLE_HOME/server/bin directory.
Edit the values in the patch_oim_wls.profile so they are specific to your environment. Use only forward slash characters (/) in the directory paths you set. Do not use back slash characters (\), including on Microsoft Windows platforms.
Set the following environment variables. Use only forward slash characters (/) in the directory paths you set. Do not use back slash characters (\), including on Microsoft Windows platforms.
```
ANT_HOME
                        JAVA_HOME
                        OIM_ORACLE_HOME
                        WL_HOME
```
Execute the patch_oim_wls script that is appropriate for your environment, patch_oim_wls.sh or patch_oim_wls.bat.
Examine the patch_oim_wls.log file for information about the script execution.
Restart all Oracle Identity Manager managed servers.

5.4.3.14 Verify the Oracle Identity Management Domain

To verify that the upgrades and patches to the Oracle Identity Management domain were applied correctly:

Confirm you can access and log in to the Oracle WebLogic Administrative Server console. For example:
```
http://HOST:ADMIN_SERVER_PORT/console
https://HOST:SECURE_ADMIN_SERVER_PORT/console
```
Confirm you can access and log in to Fusion Applications Control. For example:
```
http://HOST:ADMIN_SERVER_PORT/em
```

5.4.4 Apply Mandatory Prerequisite RDBMS Patches

Note:

Before you perform the steps in this section, you must remove any conflicting patches from the RDBMS host. Follow the steps in the README.txt file of patch 14543240 to run the script on the RDBMS host. You downloaded patch 14543240 in Section 5.3.5, "Find Conflicting Patches".

Ensure that you run this script only before upgrading. If you run this script at any time other than before upgrading, the system may be left in an unstable state.

When you run RUP Installer, the patches you downloaded in Step 3, Section 5.3.5, "Find Conflicting Patches", will automatically apply.

Run the RUP Lite for RDBMS utility to update your Oracle Fusion Applications database before you upgrade.

RUP Lite for RDBMS uses non-interactive OPatch calls to apply RDBMS patches. OPatch tries to install and configure Oracle Configuration Manager (OCM) if OCM has not already been installed and configured. This causes non-interactive OPatch calls to fail in some cases. To avoid this issue, Oracle recommends that you install OCM prior to running RUP Lite for RDBMS. If you plan to use OCM, you should configure it after you install it. If you do not plan to use OCM, you can either configure it in disconnected mode or let RUP Lite for RDBMS configure it. If you install OCM and do not configure it, RUP Lite for RDBMS will automatically configure it in disconnected mode. For more information, see "Installing Oracle Configuration Manager Using the Command Line Interface" in the Oracle Configuration Manager Installation and Administration Guide.

If you do not use Oracle Exadata Database Machine, run RUP Lite for RDBMS to automatically apply the mandatory Oracle Database patches mentioned in the "Oracle Database" section of Oracle Fusion Applications release notes. This step applies Oracle Database base patches that reside in both the REPOSITORY_LOCATION and the post_repo_patches directory, which you downloaded in Section 5.3.6, "Download Mandatory Post Release 5 Patches". Follow the steps in Section 5.4.4.1, "Run RUP Lite for RDBMS".

If you use Oracle Exadata Database Machine, manually apply the patches listed in Section 5.4.4.4, "Apply Exadata Patches" followed by any patches you downloaded in Section 5.3.6, "Download Mandatory Post Release 5 Patches". Do not run RUP Lite for RDBMS.

5.4.4.1 Run RUP Lite for RDBMS

If you are running Oracle Fusion Applications on a RAC database, follow the steps in Section 5.4.4.2, "Run RUP Lite for RDBMS in a RAC Database".

Perform the following steps to run RUP Lite for RDBMS:

Copy the TPBundler.zip file to any temporary directory, such as work_dir, in this example:
```
cp REPOSITORY_LOCATION/installers/pre_install/TPBundler.zip work_dir
```

Unzip TPBundler.zip in work_dir, which contains the following files after unzipping:

createTPBundle.jar
createTPBundle.cmd
createTPBundle.sh
ojdl.jar
tpBundleConfig_DB.xml
tpBundleConfig_IDM.xml
tpBundleConfig_OHS.xml
README.txt

The createTPBundler utility creates the RDBMS patch bundle and RUP Lite for RDBMS. This patch bundle contains the mandatory prerequisite patches that are delivered in REPOSITORY_LOCATION as well as any patches you may have downloaded.

Use the following command syntax to run createTPBundler, which creates DBPatches.zip in a temporary directory, referred to as work_dir in the example. Note that work_dir must have read/write permissions.
```
(Unix)
sh createTPBundle.sh -shiphomelocation REPOSITORY_LOCATION -tempdir work_dir -target DB [-patchdownloadloc location_of_downloaded_patches]

(Windows)
createTPBundle.cmd -shiphomelocation REPOSITORY_LOCATION -tempdir work_dir -target DB [-patchdownloadloc location_of_downloaded_patches]
```
The following options are available for createTPBundler:
- -shiphomelocation: Location of the ship home.
- -tempdir: Destination directory to which the generated zip file was copied.
- -target: Target against which the copy should be initiated. Valid values are IDM, DB, OH. Use the DB value.
- -patchdownloadloc: Location of the patch directory where you downloaded the patches in Section 5.3.6, "Download Mandatory Post Release 5 Patches". Use this option only if you downloaded patches into a directory other than the default patch download directory, which is post_repo_patches.
- -logfile: Full path of the createTPbundle log file. The default is createTPBundle.log in the current directory.
- -loglevel: Log level for the createTPbundler utility. Valid values are SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST. The default value is INFO.
Copy DBPatches.zip to any temporary directory on the database server host.
Log in to the database server host.

Unzip DBPatches.zip to any temporary directory on the database server host. The following subdirectories and files exist after unzipping.

|-- DB_TIME_STAMP
    -- db_server_bundle
        |-- README.txt
        |-- bin
        |   |-- ruplite.bat
        |   |-- ruplite.sh
        |-- metadata
        |   |-- env.properties
        |   |-- installer.properties
        |   |-- plugin-metadata.txt
        |-- custom_db_server
        |    -- database
        |        -- patch
        |            -- downloaded one-off patches
        |-- db_server
        |   |-- database
        |       |-- opatch
        |       |    -- OPatch zip file
        |       |-- patch
        |       |    -- One-off patches in repository
        |       |-- psu
        |       |    -- Patch Set Updates in repository
        |-- db
        |   |--RUP Lite related files 
        |-- lib
        |   |--RUP Lite related files
        |-- ruplite
        |   |--RUP Lite related files 
        |-- techpatch
        |   |--TPU related files

Perform this step only if you are running RUP Lite for RDBMS on an Oracle VM environment.

As the root user, change the permissions on the DB_timestamp subdirectory:
```
chmod -R 777 DB_timestamp
```
Exit out of root user to ensure that you do not perform the remaining steps as root.
Set executable permissions on ruplite.sh.
```
chmod -R 755 ruplite.sh
```
Set the following environment variables:
- ORACLE_SID=Use an instance name that belongs to the fusionapps database.
- ORACLE_HOME=Use an Oracle home directory, such as /u01/db/11.2.0.3.
- TNS_ADMIN=Use a valid tns_admin location, which is typically located under the grid infra and contains listener.ora and sqlnet.ora files.
- LISTENER_NAME=Use a listener name, such as db1234.
- JAVA_HOME=Use a Java home directory, such as /net/u02/APPTOP/fusionapps/jdk.
Verify that the java version is 1.6 or above by using the following command:
```
(Unix)
$JAVA_HOME/bin/java -version

(Windows)
%JAVA_HOME%\bin\java -version
```
If your version is lower, download 1.6 or a higher version from My Oracle Support.
Verify that your Opatch version is 11.2.0.3.0 or above by using the following command:
```
(Unix)
$ORACLE_HOME/OPatch/opatch version

(Windows)
%ORACLE_HOME%\OPatch\opatch version
```
If your version of OPatch is lower than 11.2.0.3.0, download the 11.2.0.3.0 or higher version from My Oracle Support.
Stop all user applications.
Change directory to the following location:

DB_timestamp/db_server_bundle/ruplite/bin
RUP Lite for RDBMS starts and stops only the Fusion Applications database listener and the database server. You must stop any other applications or processes that are running from the Oracle Fusion Applications home directory, except the OPSS Security Store, before you run RUP Lite for RDBMS. For more information, see "Starting and Stopping" in the Oracle Fusion Applications Administrator's Guide. Also confirm that the BI presentation servers are shut down.

You can optionally use the startstopdb false option if you want to manually shut down the database and stop the listener before patching, and then manually bring them up after applying the patches. If you use the startstopdb false option on Windows, follow the steps in Section 5.4.4.3, "Stop Services on Windows Before Running RUP Lite For RDBMS". If you use this option, the status of the database and listener is not checked.

Run RUP Lite for RDBMS.
```
(Unix)
ruplite.sh [-startstopdb false]

(Windows)
ruplite.bat [-startstopdb false]
```

Review the following log files located under the DB_timestamp directory if any errors occurred:

./db_server_bundle/techpatch/tp-property-editor.log
./db_server_bundle/techpatch/db_validate_repository_patches.log
./db_server_bundle/techpatch/db_apply_repository_patches.log
./db_server_bundle/techpatch/db_stop.log
./db_server_bundle/techpatch/db_start.log 
./db_server_bundle/apply_repo_dboutput.xml 
./db_server_bundle/post_apply_dboutput.xml 
./db_server_bundle/pre_apply_dboutput.xml

If RUP Lite for RDBMS fails, resolve the issue reported in the log files and restart your session. When you restart a failed session, RUP Lite for RDBMS ignores the successful actions, starts with the failed action, and proceeds from that point.

You must manually execute any manual steps that are documented in the README.txt file of the patches you applied with RUP Lite for RDBMS. RUP Lite for RDBMS does not execute manual steps from the README.txt of the patches.
For Windows, start the services that were stopped. From the Control Panel, select Administrative Tools, then Services. Right click on each service and choose the Start option.

5.4.4.2 Run RUP Lite for RDBMS in a RAC Database

Perform the following steps to run RUP Lite for RDBMS for a RAC database. You must run RUP Lite for RDBMS on all available file systems. This may involve multiple hosts and nodes. Note that a single Oracle home can be shared by multiple nodes, and in this case, running RUP Lite on a single node of such a group is sufficient.

Follow Steps 1 through 8 in Section 5.4.4.1, "Run RUP Lite for RDBMS".
Stop all user applications that use the Oracle home directory being patched.

Go to an Oracle home and set the following environment variables:

setenv ORACLE_SID instance_name
setenv ORACLE_HOME /server01/oracle/db/tech_st/11.2.0.3
setenv TNS_ADMIN /server01/oracle/db/tech_st/11.2.0.3/network/admin/db999
setenv LISTENER_NAME db999
setenv JAVA_HOME Location_of_java (must be jdk6)

Verify that the java version is 1.6 or above by using the following command:

(Unix)
$JAVA_HOME/bin/java -version

(Windows)
%JAVA_HOME%\bin\java -version

Verify that your Opatch version is 11.2.0.3.0 or above by using the following command:
```
(Unix)
$ORACLE_HOME/OPatch/opatch version

(Windows)
%ORACLE_HOME%\OPatch\opatch version
```
If your version of OPatch is lower than 11.2.0.3.0, download the 11.2.0.3.0 or higher version from My Oracle Support.
Shut down all Oracle RAC databases on all nodes in the cluster, even those that are sharing the same Oracle home. Database instances that are running could cause issues that prevent patches from applying successfully or you could receive errors because the patches update files that are in use.

To shut down an Oracle RAC database, enter the following command in a command window, where CRS_home is the location of the Grid home directory and sales is the name of the database:
```
(Unix)
CRS_home/bin/srvctl stop database -d sales

(Windows)
CRS_home\bin\srvctl stop database -d sales
```
Stop the listener that is running from all Oracle homes in the cluster, using the following command. Note that all services must be shut down if the OIM and OID databases are configured on same listener.
```
(Unix)
CRS_home/bin/srvctl stop listener [-l listener_name]

(Windows)
CRS_home\bin\srvctl stop listener [-l listener_name]
```
Change directory to the following location:

DB_timestamp/db_server_bundle/ruplite/bin

Run RUP Lite for RDBMS with the option -startstopdb false.

(Unix)
ruplite.sh -startstopdb false

(Windows)
ruplite.bat -startstopdb false

Review the following log files located under the DB_timestamp directory if any errors occurred:

./db_server_bundle/techpatch/tp-property-editor.log
./db_server_bundle/techpatch/db_validate_repository_patches.log
./db_server_bundle/techpatch/db_apply_repository_patches.log
./db_server_bundle/techpatch/db_stop.log
./db_server_bundle/techpatch/db_start.log 
./db_server_bundle/apply_repo_dboutput.xml 
./db_server_bundle/post_apply_dboutput.xml 
./db_server_bundle/pre_apply_dboutput.xml

You must manually execute manual steps that are documented in the README.txt file of the patches you applied with RUP Lite for RDBMS. RUP Lite for RDBMS does not execute manual steps from the README.txt of the patches. If there is more than one ORACLE_HOME in the RAC database, you do not need to run SQL scripts again when patching the second through the nth ORACLE_HOME, but you do need to perform any manual steps that update ORACLE_HOME.
RAC databases often share a single ORACLE_HOME for all RAC instances. If you have this configuration, continue to the next step.

If you do not have this configuration, you must update the files in the other ORACLE_HOMEs for your RAC database. To update the other ORACLE_HOMEs, repeat Steps 4 through 8 in Section 5.4.4.1, "Run RUP Lite for RDBMS" for RAC instances with non-shared ORACLE_HOMEs. Then repeat Steps 3 through 13 in this section for all RAC instances. Note that this may involve multiple hosts and nodes.
Start the database.
Start the listener from all Oracle homes in the cluster. For Windows, start the services you stopped in Section 5.4.4.3, "Stop Services on Windows Before Running RUP Lite For RDBMS".

5.4.4.3 Stop Services on Windows Before Running RUP Lite For RDBMS

For a Windows platform, the following services must be stopped:

OracleOraDb11g_home1TNSListenerLISTENER_<SID>
OracleOraDb11g_home1ClrAgent
OracleDBConsole<SID>
OracleJobScheduler<SID>
OracleService<SID>
OracleMTSRecoveryService
Windows Management Instrumentation
Distributed Transaction Coordinator
Oracle <SID> VSS Writer Service

From the Control Panel, select Administrative Tools, then Services. Right click on each service and choose the Stop option.

5.4.4.4 Apply Exadata Patches

If you are on the Linux64 operating system and use the Oracle Exadata Database Machine, download and apply patch p13734832_112030_Linux-x86-64.zip (Patch 13734832 - Database Patch for Exadata (APR 2012 - 11.2.0.3.5)) from My Oracle Support.

Then apply the Generic and Linux64 patches with the special considerations as described in Table 5-9.

Table 5-9 Mandatory Exadata Patches

Generic/Linux patch	Exadata equivalent
p13508115_112030_Generic.zip	Apply as is
p10263668_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 Exadata Database for the same Bug number
p12312133_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for the same Bug number
p12358083_112030_Linux-x86-64.zip	Apply as is
p12672969_112030_Linux-x86-64.zip	Ignore (included in p13734832_112030_Linux-x86-64.zip)
p12772404_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for the same Bug number
p12880299_112030_Linux-x86-64.zip	Apply as is
p12889054_112030_Linux-x86-64.zip	Ignore (included in p13734832_112030_Linux-x86-64.zip)
p12977501_112030_Linux-x86-64.zip	Apply as is
p12985184_112030_Linux-x86-64.zip	Apply as is
p13014128_112030_Linux-x86-64.zip	Apply as is
p13073340_112030_Linux-x86-64.zip	Apply as is
p13257247_112030_Linux-x86-64.zip	Ignore (included in p13734832_112030_Linux-x86-64.zip)
p13365700_112030_Linux-x86-64.zip	Apply as is
p13382280_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for the same Bug number
p13404129_112030_Linux-x86-64.zip	Apply as is
p13454210_112030_Linux-x86-64.zip	Ignore (included in p13734832_112030_Linux-x86-64.zip)
p13503598_112030_Linux-x86-64.zip	Ignore (included in p13734832_112030_Linux-x86-64.zip)
p13714926_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for the same Bug number
p13775960_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for the same Bug number
p13787482_112030_Linux-x86-64.zip	Apply as is
p13790109_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for the same Bug number
p13983131_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for Bug 13949189
p14019600_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for Bug 14192095
p14029429_112030_Linux-x86-64.zip	Apply as is
p14058884_112030_Linux-x86-64.zip	Apply as is
p14143796_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for Bug 14235967
p14237907_112030_Linux-x86-64.zip	Download and apply the overlay patch on 11.2.0.3.5 ExadataDatabase for Bug 14179751

5.4.5 Run "catmetx.sql"

To prevent issues during the Bootstrapping Patch Manager configuration task, run the following script as SYS user on all database instances before you start RUP Installer:

ORACLE_HOME/rdbms/admin/catmetx.sql

5.4.6 Perform Required Backups

The following backups must be performed:

Back Up Oracle Fusion Applications
Back Up the OPSS Security Store
Back Up Steps for Windows Platforms

5.4.6.1 Back Up Oracle Fusion Applications

Back up your entire Oracle Fusion Applications environment by following the steps in "Backing Up and Recovering Oracle Fusion Applications" in the Oracle Fusion Applications Administrator's Guide. You should also back up your central inventory.

For additional back up steps that are specific to Windows, refer to Section 5.4.6.3, "Back Up Steps for Windows Platforms".

5.4.6.2 Back Up the OPSS Security Store

RUP Installer upgrades all WLS domains to the 11gR1 PS5 MLR1 (11.1.1.6.1) level so you must perform the following backups. You can use any directory to back up the data, as long as you know where to restore the backup from.

OPSS Security Store

Back up all data under the root node of the OPSS Security Store. To identify the root node in the Oracle Internet Directory hosting the OPSS Security store, use Fusion Applications Control and look at the Root Node Details pane under the Security Provider information. For more information, see "Reassociating with Fusion Middleware Control" in the Oracle Fusion Middleware Application Security Guide.

In case of an upgrade failure, restore this node entirely. The ldifwrite and bulkload operations that follow must be performed on the system where the Oracle Internet Directory hosting the OPSS Security store resides.
- Set the following environment variables.
```
setenv ORACLE_HOME  OID_ORACLE_HOME
setenv ORACLE_INSTANCE  OID_INSTANCE_HOME
```
  Example:
```
setenv ORACLE_HOME /u01/oid/oid_home 
setenv ORACLE_INSTANCE /u01/oid/oid_inst 
```
- Follow this step to create the backup.
  
  In the system where the Oracle Internet Directory is located, produce an LDIF file by running ldifwrite as illustrated in the following line:
```
OID_HOME/ldap/bin/ldifwrite connect="srcOidDbConnectStr" basedn="cn=FAPolicies", c=us" ldiffile="srcOid.ldif"
```
  Example:
```
/u01/oid/oid_home/ldif/bin/ldifwrite connect="oidddb" basedn="cn=FAPolicies" ldiffile="srcOid.ldif"
```
  This command writes all entries under the node cn=FAPolicies to the file srcOid.ldif. Once generated, move this file to the directory that was identified earlier, to hold all backup data.
- Follow these steps to restore the backup.
  - In the Oracle Internet Directory system, verify that there are no schema errors or bad entries by running bulkload as illustrated in the following line:
```
OID_HOME/ldap/bin/bulkload connect="dstOidDbConnectStr" check=true generate=true restore=true file="fullPath2SrcOidLdif"
```
    If duplicate DNs (common entries between the source and destination directories) are detected, review them to prevent unexpected results.
  - Load data into the Oracle Internet Directory by running bulkload as illustrated in the following line:
```
OID_HOME/ldap/bin/bulkload connect="dstOidDbConnectStr" load=true file="fullPath2SrcOidLdif"
```
For more information about the bulkload command, see "Performing Bulk Operations" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

For more information about migrating Oracle Internet Directory, see "Migrating Large Volume Policy and Credential Stores" in the Oracle Fusion Middleware Application Security Guide.
Bootstrap Wallet

Back up the cwallet.sso file in the DOMAIN_HOME/config/fmwconfig/bootstrap directory for each WLS domain in an Oracle Fusion Applications installation. You must take backups of each cwallet.sso file for each domain and when you restore, you must be careful to restore the correct file. For example, if you back up cwallet.sso from the Common Domain, then you must restore it in the Common Domain upon failure. If you back up cwallet.sso from the BI domain, you must restore it to the BI Domain upon failure.

5.4.6.3 Back Up Steps for Windows Platforms

Back up the Oracle Fusion Applications environment, including APPLICATIONS_BASE, inventory, registry entries, Oracle Identity Management, the database and the System environment PATH variable of the Oracle Fusion Applications host machine.

APPLICATIONS_BASE has many files whose path is more than 256 characters. The Microsoft Windows Copy function is limited to copying only those files with a path of less than 256 characters. Therefore, many files fail to copy.

Use Robust File Copy (Robocopy), which is available as part of the Windows Resource Kit, to copy the APPLICATIONS_BASE. Use the following command:

robocopy <source> <destination> /MIR > <file>

Sample output from the robocopy command:

	Total	Copied	Skipped	Mismatch	FAILED	Extras
Dirs:	112640	112640	0	0	0
Files:	787114	787114	0	0	0
Bytes:	63.822 g	63.822 g	0	0	0
Times:	2:22:20	2:19:00			0:00:00	0:03:19

Back up the inventory.

Back up the inventory location referenced in the registry HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\inst_loc.
Back up the registry.

Use Regedit.exe to back up the following registries related to Oracle Fusion Applications.
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
  - Web Tier service
  - BI Service
  - Node Manager service
- HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Oblix

Ensure that the System PATH has the following values:

C:\<APPLICATIONS_BASE>\dbclient\bin
C:\<APPLICATIONS_BASE>\webtier_mwhome\webtier\bin
C:\<APPLICATIONS_BASE>\webtier_mwhome\webtier\\bin
C:\<APPLICATIONS_BASE>\webtier_mwhome\webtier\opmn\lib
C:\<APPLICATIONS_BASE>\webtier_mwhome\webtier\perl\bin
C:\<APPLICATIONS_BASE>\fusionapps\bi\products\Essbase\EssbaseServer\bin
C:\<APPLICATIONS_BASE>\fusionapps\bi\bin
C:\<APPLICATIONS_BASE>\fusionapps\bi\opmn\bin
C:\<APPLICATIONS_BASE>\fusionapps\bi\opmn\lib
C:\<APPLICATIONS_BASE>\fusionapps\bi\perl\bin

Add any of the previous values that are missing to the system PATH. Missing values cause failures in launching the OPMN services and BI Presentation Catalog deployment tasks in RUP Installer.

Save the system PATH variable.

5.4.7 Remove Conflicting Patches From the Primordial Host

Backup the existing ATG_HOME/atgpf/lib/oracle.apps.fnd.applxdf.jar file.
Follow the steps in the README.txt file of patch 14543240 to run the script to remove conflicting patches from the primordial host. You downloaded patch 14543240 in Section 5.3.5, "Find Conflicting Patches". You must run this script on the primordial host.

Note:

Ensure that you run this script only before upgrading. If you run this script at any time other than before upgrading, the system may be left in an unstable state.

When you run RUP Installer, the patches you downloaded in Step 3 in Section 5.3.5, "Find Conflicting Patches", will automatically apply.
Restore ATG_HOME/atgpf/lib/oracle.apps.fnd.applxdf.jar from the backup to its original location.

5.4.8 Enable Anonymous Binds in Oracle Internet Directory

To prevent an error during the upgrade, you must temporarily enable anonymous binds in Oracle Internet Directory. To enable all anonymous binds on the Oracle Internet Directory instance with componentName oid1 using ldapmodify, run the following command:

ldapmodify -D cn=orcladmin -Q -p portNum -h hostname -f ldifFile

with an LDIF file such as the following example:

dn: cn=oid1,cn=osdldapd,cn=subconfigsubentry
changetype: modify
replace: orclAnonymousBindsFlag
orclAnonymousBindsFlag: 1

You can also use Oracle Enterprise Manager Fusion Middleware Control to enable anonymous binds. For more information, see "Managing Anonymous Binds" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory. You will disable anonymous binds after the upgrade by setting the value of the orclAnonymousBindsFlag to 0.

5.4.9 Run the Inventory Cleanup Script

Run the wipeFAPatches.pl script to ensure that the patch information stored in the FA_ORACLE_HOME/inventory is accurate. Perform the following steps:

The script creates a backup directory named FA_ORACLE_HOME/inventory/backup/wipeFAPatchesBackup_timestamp where it copies the existing contents of the FA_ORACLE_HOME/.patch_storage and FA_ORACLE_HOME/inventory/oneoffs directories, and the FA_ORACLE_HOME/inventory/ContentsXML/comps.xml file. Verify that you have sufficient disk space for the back up to succeed.
Download and unzip patch 14565997 from My Oracle Support.

Use the following command syntax to run the patch inventory cleanup script:

(Unix)
setenv PERL5LIB APPLICATIONS_BASE/dbclient/perl/lib/5.8.3:APPLICATIONS_BASE/dbclient/perl/lib/site_perl/5.8.3/:APPLICATIONS_BASE/dbclient/perl/lib/site_perl

$APPLICATIONS_BASE/dbclient/perl/bin/perl PATCH_LOCATION/wipeFAPatches.pl FA_ORACLE_HOME

(Windows)
SET PERL5LIB=APPLICATIONS_BASE\dbclient\perl\5.8.3;APPLICATIONS_BASE\dbclient\perl\site\5.8.3\;APPLICATIONS_BASE\dbclient\perl\site

%APPLICATIONS_BASE%\dbclient\perl\5.8.3\bin\MSWin32-x64-multi-thread\perl PATCH_LOCATION\wipeFAPatches.pl FA_ORACLE_HOME

To verify that the inventory is correctly updated, run the OPatch inventory report that lists patches applied to FA_ORACLE_HOME. The inventory report should not show any patches as being applied after you run the cleanup script.
```
(Unix)
FA_ORACLE_HOME/OPatch/opatch lsinventory -oh FA_ORACLE_HOME -invPtrLoc FA_ORACLE_HOME/oraInst.loc -jre JVM_HOME

(Windows)
FA_ORACLE_HOME\OPatch\opatch lsinventory -oh FA_ORACLE_HOME -jre JVM_HOME
```

5.4.10 Upgrade JDK (Linux and Windows Platforms Only)

To upgrade your JDK version, or confirm that your version is compatible with RUP Installer, run the upgradeJDK utility. This utility is located in REPOSITORY_LOCATION/installers/farup/Disk1/upgrade/bin. Ensure that you set the environment variables described in Section 5.3.4, "Set Environment Variables".

Run the following command from the primordial host. Primordial host is define in Section 5.3.1, "Before You Begin".

(Unix) upgradeJDK.sh
(Windows) upgradeJDK.bat

The upgradeJDK utility moves the previous jdk6 to jdk6.28.2.0 and then moves the new version of jdk6 to the correct location, APPLICATIONS_BASE/fusionapps.

Logs for upgradeJDK are located in the following directory: FA_ORACLE_HOME/admin/FUSION/log/upgradeJDK.

5.4.11 Run RUP Lite for OVM - Offline (Oracle VM Hosts Only)

Perform the steps in this section only if you are running Oracle Fusion Applications in an Oracle VM environment that was created from the official releases of Oracle VM templates for Oracle Fusion Applications Release 2 (11.1.2) and higher. The content is not applicable for any Oracle VM environments that are created using other methods.

Note:

To ensure you are upgrading an OVM environment and before you run RUP Lite for OVM, confirm that the host related properties in APPLICATIONS_BASE/ovabext/deployfw/deployprops/ovm-ha-deploy.properties properly describe the physical machines in the environment. For IDM nodes, the location is /u01/ovmext/deployfw/deployprops/ovm-ha-deploy.properties.

RUP Lite for OVM is a utility that addresses the differences between a newly provisioned Oracle VM environment on the latest release and an Oracle VM environment provisioned in a previous release. You run RUP Lite for OVM in offline mode before RUP Installer runs. After RUP Installer completes, you run RUP Lite for OVM again, this time in online mode, as described in Section 5.6.2, "Run RUP Lite for OVM - Online (Oracle VM Hosts Only)".

Table 5-10 describes the plug-ins that are included in RUP Lite for OVM in offline mode.

Table 5-10 Offline Plug-ins for RUP Lite for OVM

Plugin Name	Mandatory	Description
ValidateEnvironment	Yes	Checks if the node is a valid Oracle VM node. This plugin always runs and does not have any properties.
SetupCredentials	Yes	Prompts for credentials and stores the results in a secure manner for other plugins to use. This plugin always runs and only prompts for secure properties that are needed by other plugins that will execute. If a plugin does not run on the current node or is disabled, then its properties are not requested.
InstallArtifacts	Yes	Installs new artifacts required by Release 5.
UpdateJPSRoot	Yes	Updates `jpsroot` to use `cn=FAPolicies` instead of `cn=jpsroot`. This plugin runs only on the `admin-apps` node. This change only applies to RUP1 Oracle VMs which have `cn=jpsroot`. Note that if an Oracle VM is from RUP1, then there is an IDM script that migrates policies from `cn=jpsroot` to `cn=FAPolicies` that is executed as part of the IDM upgrade.
UpdateResolvConf	No	Adds DNS servers, search domains, and other options by updating `/etc/resolv.conf`.
ApplyMemorySettings	No	This plugin runs only on the `admin-apps` node. It increases existing memory settings for WebLogic servers based on the latest Oracle recommendations. It updates settings to the higher of the current setting or the recommended setting. If memory settings increase to a level where the Oracle VM's memory settings need to be increased, then the update to the Oracle VM must be done prior to running RUP Lite for OVM. Note that values that are higher in the environment compared to the reference values are not changed. Only lower values are increased.
CreateFAAdminUser	No	Uploads a new Oracle Fusion Applications administrator user name and password to the ID store and runs only on the `admin-apps` node. Note that if the FAAdmin user or password was changed when OVM was first created, then you cannot enable this plugin.
UpdateBootstrapCredentials	Yes	Updates the bootstrap credentials across domains to use the policy store Read Write user, such as updating the user name from `orcladmin` to `cn=PolicyRWUser,cn=users,dc=us,dc=oracle,dc=com`. This plugin runs only on the `admin-apps` node.
SetExternalDNSNames	Yes	Updates the external DNS name in the `APPLICATIONS_CONFIG/domains/admin-apps.oracleoutsourcing.com/CommonDomain/config/config.xml` file. This plugin runs on the `admin-apps` and the `bi` nodes.
UploadOSNCredentials	Yes	Seeds OSN required artifacts to the LDAP store. This plugin runs only on the admin-apps node.
UpdateBIHostname	Yes	Updates the BI domain with the physical host name.
CreateUVScanSymlink	Yes	Creates a symbolic link to McAfee `uvscan`. This plugin only runs on CRM topology. McAfee `uvscan` should be enabled on all post-Release 2 CRM Oracle VMs.
UpdateESDProperties	Yes	Sets the Email Send Daemon information in `APPLICATIONS_BASE/instance/domains/admin-apps.oracleoutsourcing.com/CRMDomain/config/FusionEsd/esd.properties`.
FixUCMConfig	Yes	Updates the IP address filter whitelist for UCM to allow all machines access to UCM.
EnableSearchUI	Yes	Enables the global search UI for Oracle Fusion Applications.
GenerateOptimizedQueryPlans	Yes	Generates optimized query plans for Oracle MDS queries.

Perform the following steps to run RUP Lite for OVM on each node of your Oracle VM environment:

Download and Unzip RUP Lite for OVM
Update the Properties File
Run RUP Lite for OVM
Repeat Steps On All Nodes Of Your Oracle VM Environment
Troubleshoot RUP Lite for OVM

5.4.11.1 Download and Unzip RUP Lite for OVM

Perform the following steps to download and unzip RUP Lite for OVM.

From My Oracle Support, download patch 14324781 to the primordial host.
Unzip the opatch zip file to a directory, such as /u01/patches/14324781.
Go to this directory:
```
cd /u01/patches/14324781
```

Run OPatch to apply the patch on the primordial host.

FA_ORACLE_HOME/OPatch/opatch apply -oh FA_ORACLE_HOME -invPtrLoc FA_ORACLE_HOME/oraInst.loc 
-jre APPLICATIONS_BASE/fusionapps/jdk6

The ruplite-ovm.zip file will be placed in the FA_ORACLE_HOME/lcm directory.
Unzip ruplite-ovm.zip into a new directory under the primordial host's local storage.

5.4.11.2 Update the Properties File

Update the env.properties file under the ruplite-ovm/metadata directory with the required property values for the following plugins:

UpdateResolvConf

If you have additional DNS servers, search domains, or want to set options such as timeout and attempt, set the properties below and run this plugin.

If no additional DNS servers, search domains or options are needed, disable this plugin so it does not run.

ovm.plugin.UpdateResolvConf.enabled=true
 
# Optional additional dns name server IP addresses (comma delimited)
#example: ovm.plugin.UpdateResolvConf.dns_servers=138.2.202.15,130.35.249.41
ovm.plugin.UpdateResolvConf.dns_servers=ip_address_dns_server_01,ip_address_dns_server02
 
# Optional additional resolv.conf options (comma delimited)
#example: ovm.plugin.UpdateResolvConf.options=timeout:1,attempts:2
ovm.plugin.UpdateResolvConf.options=
 
# Optional additional resolv.conf search domains (comma delimited)
#example: ovm.plugin.UpdateResolvConf.search=example.com,x.example.com
ovm.plugin.UpdateResolvConf.search=

The dns_servers property is a comma separated list of IP addresses of the dns servers to add to the /etc/resolv.conf file.

ApplyMemorySettings

ovm.plugin.ApplyMemorySettings.enabled=true

CreateFAAdminUser

ovm.plugin.CreateFAAdminUser.enabled=true
ovm.plugin.CreateFAAdminUser.admin_username=fusion_apps_administrator
ovm.plugin.CreateFAAdminUser.idstore_user=cn=IDRWUser,cn=users,dc=us,dc=oracle,dc=com

UpdateBootstrapCredentials
```
ovm.plugin.UpdateBootstrapCredentials.enabled=true
ovm.plugin.UpdateBootstrapCredentials.policy_user=cn=PolicyRWUser,cn=users,dc=us,dc=oracle,dc=com
```
Note that the user name and password for bootstrap credentials should be that of the Policy Read Write User. You are prompted for the Policy Store Read Write User password when the SetupCredentials plugin runs.

UpdateJPSRoot

ovm.plugin.UpdateJPSRoot.enabled=true
ovm.plugin.UpdateJPSRoot.jpsroot_name=cn=FAPolicies
ovm.plugin.UpdateJPSRoot.original_jpsroot_name=cn=jpsroot

UploadOSNCredentials

ovm.plugin.UploadOSNCredentials.enabled=true
ovm.plugin.UploadOSNCredentials.idstore_user=cn=IDRWUser,cn=users,dc=us,dc=oracle,dc=com

UpdateBIHostname

ovm.plugin.UpdateBIHostname.enabled=true

CreateUVScanSymlink
```
ovm.plugin.CreateUVScanSymlink.enabled=true
```
Before running this plugin, ensure that McAfee uvscan is installed on this Oracle VM. If McAfee uvscan is installed, the location is reflected in the property, faovm.virusscan.mcafee.dir,located in ovm-ha-deploy.properties.

UpdateESDProperties

ovm.plugin.UpdateESDProperties.enabled=true

FixUCMConfig
```
ovm.plugin.FixUCMConfig.enabled=true
```
EnableSearchUI
```
ovm.plugin.EnableSearchUI.enabled=true
```

GenerateOptimizedQueryPlans

ovm.plugin.GenerateOptimizedQueryPlans.enabled=true

Confirm that the OVM_ROOT_DIR property is in the env.properties file, for example OVM_ROOT_DIR=/u01/APPLTOP.

5.4.11.3 Run RUP Lite for OVM

Run RUP Lite for OVM on all nodes of your Oracle VM environment. Note that you must run RUP Lite for OVM as the root user.

Set the JAVA_HOME directory, for example:
```
setenv JAVA_HOME /assemblybuild/jre
```
Examples of jre locations for other nodes follow:
- AuthOHS Node: /u01/ohsauth/oracle_common/jdk
- OIM Node: /u01/oim/jrockit_160_24_D1.1.2-4
- OID Node: /u01/oid/oracle_common/jdk
Run ruplite.sh from the ruplite-ovm directory.
```
cd /ruplite-ovm
bin/ruplite.sh
```

Respond to the following prompts, which will be stored in a wallet file in the ruplite-ovm/output/wallet directory.

RUP Lite Wallet Key: If a wallet already exists, enter the value for the existing key. If the wallet does not exist, a new one will be created using the key you provide.
The key must be at least 8 characters long and include at least one numeric character.

Policy Store RW User Password: The user name and password for bootstrap credentials should be that of the PolicyRWUser. Enter this password.
ID Store RW User Password:
FA Admin Password:

If no plugins run that require secure properties, the wallet creation and access is skipped and you are not prompted for the wallet key.

Refer to Section 5.4.11.5, "Troubleshoot RUP Lite for OVM" for information about verifying that RUP Lite for OVM was successful.

5.4.11.4 Repeat Steps On All Nodes Of Your Oracle VM Environment

The following steps must be performed on all nodes of your Oracle VM environment:

Create a top level directory, referred to as ruplite-ovm, into which you will copy and unzip the ruplite-ovm.zip file.
Copy and unzip FA_ORACLE_HOME/lcm/ruplite-ovm.zip to the ruplite-ovm directory in each node's local storage.
Update the env.properties file under the ruplite-ovm/metadata directory, as described in Section 5.4.11.2, "Update the Properties File".
Run RUP Lite for OVM, as described in Section 5.4.11.3, "Run RUP Lite for OVM".

5.4.11.5 Troubleshoot RUP Lite for OVM

Review the ruplite-ovm/output/logs/ruplite.log file to confirm there are no errors. You can also check rehydration framework logs under /assemblybuilder/logs or /var/log for any errors. Review the following troubleshooting information for specific plugins:

ValidateEnvironment: If this plugin fails, RUP Lite for OVM stops. You must resolve any errors reported in the log file and then run RUP Lite for OVM again.
SetupCredentials: If this plugin fails, RUP Lite for OVM stops. Typical causes of failure are an incorrect key for an existing wallet, or specifying a key for a new wallet that does not meet Oracle's minimum standards. You must resolve any errors reported in the log file and then run RUP Lite for OVM again.
UpdateResolvConf: This plugin is rerunnable. If a value already exists in the /etc/resolv.conf file, it will not be added a second time.
CreateFAAdminUser: This plugin is not rerunnable. It uses the OVM rehydration framework which calls LDAP operations defined in an .ldif file that are not rerunnable. If the plugin fails, review the log file which includes the output from the rehydration command. If the error is not clear in this log file, then review the rehydration log for more information. RUP Lite for OVM displays a message that specifies the location of the rehydration log in the case of failure.

If you see the following message in the rehydration log, the user or password has already been changed. To proceed with the upgrade, disable this plugin.
```
[LDAP: error code 68 - Object already exists]
```
UpdateBootstrapCredentials: This plugin is rerunnable. When the environment is online, you can verify this plugin was successful by confirming that all domains come up after this plugin runs.

If the environment is down, you can verify this plugin was successful by confirming that the timestamp on the cwallet.sso file under the config/fmwconfig/bootstrap directory of each domain coincides with the time of the update.

If the wallet password is forgotten, or you entered an incorrect password, you can remove the ruplite/output/wallet directory, so you are prompted for all of the credentials again.
ApplyMemorySettings: Check the fusionapps_start_params.properties files in the environment, which are located under the bin directory of each domain. Ensure that the minmaxmemory settings in the files are at least as high as the settings in the template under the ovm/metadata directory that corresponds to the environment's topology.
UpdateJPSRoot: This plugin is rerunnable. Verify that the following property is set to the new jps root name in the jps-config.xml and jps-config-jse.xml files on all domains of all the nodes of the OVM environment. If the jps root name is already set to cn=FAPolicies, this plugin does not update the file.
```
<property name="oracle.security.jps.ldap.root.name" value="cn=FAPolicies"/>
```
SetExternalDNSNames: Verify that the config.xml file for each domain, such as CommonDomain,CRMDomain, FinancialDomain, and HCMDomain, contains the external DNS name. For example, for the CommonDomain, review the file, APPLICATIONS_CONFIG/domains/admin-apps.oracleoutsourcing.com/CommonDomain/config/config.xml. The following property should contain the external DNS name:
```
<external-dns-name>dns_server.mycompany.com</external-dns-name>
```

SetSOAFTPAdapter: This plugin is rerunnable. Verify that the config.xml file for the FinancialDomain references the deployment plan XML file. In the following example file, APPLICATIONS_CONFIG/domains/admin-apps.oracleoutsourcing.com/FinancialDomain/config/config.xml, notice the row that references the deployment plan XML file:

<app-deployment>
    <name>FtpAdapter</name>
    <target>FIN_SOACluster</target>
    <module-type>rar</module-type>
<source-path>/u01/APPLTOP/fusionapps/soa/soa/connectors/FtpAdapter.rar</source-path>
    <deployment-order>325</deployment-order>
    <plan-dir xsi:nil="true"></plan-dir>
    <plan-path>/u1234/APPLTOP/instance/wlsdeploymentplans/SOAFtpAdapter_Plan.xml</plan-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
  </app-deployment>

Confirm that the deployment plan XML file contains the property values set by this plugin, as shown in the following example:

<variable>
      <name>ConfigProperty_host_Value_FtpAdapter</name>
      <value>sftp.cloud.mycompany.com</value>
    </variable>
    <variable>
      <name>ConfigProperty_port_Value_FtpAdapter</name>
      <value>4321</value>
    </variable>

InstallArtifacts: This plugin is rerunnable. Verify this plugin was successful by checking that the /u01/lcm directory exists, which is created by this plugin.
InstallStartStop: This plugin is rerunnable. It requires Administration Servers to be running in order to succeed. Verify this plugin was successful by ensuring that either /etc/init.d/fastartstop or /etc/init.d/idmstartstop exists.
UploadOSNCredentials: This plugin is not rerunnable. It calls LDAP operations defined in an .ldif file that are not rerunnable. If the plugin fails, review the displayed messages and the log file which include the details of the error.
UpdateBIHostname: This plugin is rerunnable and runs on the BI node. Verify this plugin was successful by confirming that /etc/sysconfig/network contains the line, HOSTNAME=physical_name_of_BI_node. Also confirm that /etc/hosts contains a line for the BI node.

After the BI host name update, you must restart BI opmn services by performing the following steps:
- Start the node manager. See "Task 3: Start Node Manager" in the Oracle Fusion Applications Administrator's Guide.
- Start the BI Administration Server and Managed Server (bi_server1). See "Starting Oracle Business Intelligence" in the Oracle Fusion Applications Administrator's Guide.
- Start BI opmn services. See "Starting Oracle Business Intelligence" in the Oracle Fusion Applications Administrator's Guide.
CreateUVScanSymlink: This plugin is rerunnable. You can confirm that the symbolic link was created by running the following command:
```
ls -l APPLICATIONS_BASE/third_party/mcafee/uvscan
```
The following result should be returned:
```
APPLICATIONS_BASE/third_party/mcafee/uvscan \-> /mcafee/virusscan/uvscan
```
The creation of the symbolic link to the virus scan directory is successful only if the virusscan directory exists on the Oracle VM. The directory location is stored in the property, faovm.virusscan.mcafee.dir in ovm-ha-deploy.properties. If this property is missing, the plugin fails.
UpdateESDProperties: This plugin is rerunnable. Verify this plugin was successful by confirming that the following property is set in APPLICATIONS_BASE/instance/domains/admin-apps.oracleoutsourcing.com/CRMDomain/config/FusionEsd/esd.properties and that the server:port values match those in ovm-ha-deploy.properties:
```
esd.mailServers=server:port
```
FixUCMConfig: This plugin is rerunnable. Verify this plugin was successful by confirming that the following property is set in APPLICATIONS_BASE/instance/domains/secondary.oracleoutsourcing.com/CommonDomain/ucm/cs/config/config.cfg and APPLICATIONS_BASE/instance/domains/secondary.oracleoutsourcing.com/CommonDomain/ucm /ibr/config/config.cfg, if it exists:
```
SocketHostAddressSecurityFilter=*.*.*.*
```
EnableSearchUI: This plugin is rerunnable. Verify this plugin was successful by connecting to the database as fusion and confirming that the following command returns 'Y':
```
select fnd_profile.value('FUSION_APPS_SEARCH_ENABLED') from DUAL;
```
GenerateOptimizedQueryPlans: This plugin is rerunnable. Verify this plugin was successful by connecting to the database as fusion_mds and running the following command:
```
SELECT TO_CHAR(last_analyzed, 'yyyy/mm/dd hh:mi:ss am') as last_analyzed FROM user_tables;
```
The results should show that the tables were just analyzed.

5.4.12 Confirm the OPSS Security Store is Running

Start the OPSS Security Store if it is not already running. The OPSS Security Store used here is an Oracle Internet Directory LDAP server instance. Before proceeding with the installation, the designated Oracle Internet Directory server instance must be up and running. If this server is not running prior to starting the installation, the related configuration tasks will fail.

For more information, see "Starting and Stopping Oracle Internet Directory" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition).

5.4.13 Start Servers That Were Added After Provisioning

If you added any servers, you must start the new servers at least once. This step is not required for a server that has already been started at least once since your provisioned your Oracle Fusion Applications environment.

5.5 Run RUP Installer

RUP Installer must run during downtime. Oracle recommends that you run RUP Installer from a machine that is co-located in the same subnetwork as the database server to maximize performance. You must run RUP Installer from the primordial host. Primordial host is defined in Section 5.3.1, "Before You Begin".

Ensure that all steps in Section 5.3, "Prepare to Upgrade - Before Down Time" and Section 5.4, "Prepare to Upgrade - During Down Time" are successfully completed before you start RUP Installer.

RUP Installer supports GUI mode and silent mode. In GUI mode, you navigate through screens that display the progress of the upgrade, including log file locations and status messages. In silent mode, RUP Installer reports the progress of the upgrade as console output.

Run RUP Installer in GUI Mode
Run RUP Installer in Silent Mode

5.5.1 Run RUP Installer in GUI Mode

Perform the following steps to start RUP Installer in GUI mode from the command line, using specific options to further define the necessary actions. You must run RUP Installer from the primordial host.

Note:

If RUP Installer encounter errors, refer to Section 5.7, "Troubleshoot RUP Installer Sessions" before clicking any buttons in the RUP Installer user interface.

Set the JAVA_HOME environment variable as follows:

(Unix) setenv JAVA_HOME APPLICATIONS_BASE/fusionapps/jdk6

(Windows) set JAVA_HOME=APPLICATIONS_BASE\fusionapps\jdk6

Confirm the registration of the network location of FA_ORACLE_HOME.

If the Oracle Fusion Applications Oracle home directory (FA_ORACLE_HOME), which is APPLICATIONS_BASE/fusionapps/applications, is registered in the central inventory with a /net path, then provide the oraInst.loc location including /net when starting RUP Installer. An example follows:
```
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc APPLICATIONS_BASE/fusionapps/jdk6/ 
-invPtrLoc /net/APPLICATIONS_BASE/fusionapps/applications/oraInst.loc
```
If not triggered with /net path, RUP Installer copies the -invPtrLoc file to FA_ORACLE_HOME. In the example, this results in a copy of the file to itself, which then becomes an empty or zero byte file. As a result, the copy phase will fail when oracle_common patches are applied. For more information, see Section 5.7.2.4, "Inventory Pointer File is Empty".

Run the following command to start the first installer in GUI mode:

(UNIX) $REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] 
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory][-logfile log_file_name][-debug]

(IBM AIX on POWER Systems (64-bit)
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] 
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory][-logfile log_file_name][-debug] 
JVM_OPTIONS="-Xms1024m -Xmx2048m"

(Solaris X64 and Solaris Sparc) 
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] 
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory][-logfile log_file_name][-debug] 
JVM_OPTIONS="-d64 -Xms512m -XX:MaxPermSize=1024m -Xmx2048m"

(Windows)%REPOSITORY_LOCATION%\installers\farup\Disk1\setup.exe -jreLoc
APPLICATIONS_BASE\fusionapps\jdk6 [-Dworkers=number_of_workers][-DlogLevel=level] 
[-DpatchDownloadLocation=patch_directory][-logfile log_file_name] 
[-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-debug]

Table 5-11 shows valid options that can be used when running RUP Installer in GUI mode.

Table 5-11 RUP Installer command options in GUI mode

Option Name	Description	Mandatory
`-jreLoc`	Path where the Java Runtime Environment is installed. This option does not support relative paths, so you must specify the absolute path.	Yes.
`-invPtrLoc`	The location of an overriding inventory pointer file. If Oracle Fusion Applications Oracle home directory (FA_ORACLE_HOME) is registered in inventory with a `/net` path, then provide the location of `oraInst.loc` including `/net` in the path.	Recommended, use to override the default location of the inventory pointer file, located in `/etc/oraInst.loc.` This option can be used only on Unix platforms.
`-J-Dworkers` (-`Dworkers` for Windows)	The number of workers to use for uploading database content. If you provide a value for the number of workers that is outside the calculated range, you are prompted to provide a value that is within the optimal range. If you do not use this option, a calculated optimal value is used.	No, overrides the default number of workers calculated by RUP Installer. See "Worker Calculation" in Section 3.1.2, "Patching Database Artifacts".
`-J-DlogLevel` (-`DlogLevel` for Windows)	Records messages in the log file at the level you specify. Enter a value to override the default log level of `INFO`. See Section 11.1, "Oracle Fusion Applications Patch Manager Logging".	No, default value is `INFO`.
`-J-DserverStartTimeout` (-DserverStartTimeout for Windows)	Configures the timeout value for server in seconds.	No, overrides the default value for server timeout.
`-J-DpatchDownloadLocation` (`-DpatchDownloadLocation` for Windows)	The directory path where you downloaded mandatory prerequisite patches to be applied by RUP Installer. See Section 5.3.6, "Download Mandatory Post Release 5 Patches".	No, the default is `post_repo_patches`.
`-debug`	Retrieves the debug information from RUP Installer.	No.

Table 5-12 illustrates the tasks that the first installer runs. Note that additional manual steps are required to start the second installer. For information about troubleshooting RUP Installer errors, see Section 5.7, "Troubleshoot RUP Installer Sessions". For information about log files, see Section 5.7.1, "RUP Installer Log File Directories".

Table 5-12 RUP Installer Screen Sequence for the First Installer

Screen	Description and Action Required
Welcome	Appears when you start RUP Installer. This screen does not appear if you restart RUP Installer after a failure. The standard Welcome screen is read-only. It contains a navigation pane on the left-hand side that summarizes the steps the installer will take. Each item in the pane represents an installer screen, which contains prompts for the necessary information. Click Next to continue.
Installation Location	Specify the location of the existing Oracle Fusion Applications home (`FA_ORACLE_HOME)`. Click Next to continue.
Installation Summary	Summarizes the selections you made during this installation session. It includes the Oracle home, required and available disk space, and the version of the release to be installed. Review the information displayed to ensure that the installation details are what you intend. To make changes before installing, click Back to return to previous screens in the interview. Click Install to accept this configuration and start the installation.
Installation Progress	Displays a progress indicator that shows the percentage of the installation phase that is complete and indicates the location of the installation log file. The installation phase consists of copying files to the appropriate Oracle homes that are related to configuration tasks run during the first installer. When the installation progress indicator shows 100 percent, click Next to continue.
Configuration Progress	Displays a progress indicator that shows the percentage of the configuration phase that is complete. It displays each task, including steps within tasks, in the message pane as they are performed. Tasks that could be included in the first installer's configuration phase are described in Table 5-1. No additional user action is required in the Configuration Progress screen unless a failure occurs. For more information, see Section 5.7.4, "General Troubleshooting During the Configuration Phase in GUI Mode".
Installation Complete	Summarizes the installation just completed. If you want to save this configuration to a response file, click Save. For more information, see "How Response Files Work" in the Oracle Database Installation Guide 11g Release 2 (11.2) for Linux. To complete a successful installation of the first installer, click Finish. The Finish button is activated only if all mandatory configuration tasks completed successfully. If you want to rerun this session to resolve failed configuration tasks, click Cancel.
Run RUP Lite for Domain Configuration	You must perform the following steps before proceeding to the next screen. The first installer must complete successfully before you proceed to the second installer. Do not click OK until you complete this step. Run RUP Lite for Domain Configuration on all servers that contain local domains. You can skip this step if the environment does not contain any local domains. Local domains are those that are hosted on the local storage of various hosts, rather than in shared storage. Note that this step is not required for Oracle VM environments, as Oracle VM environments do not use local domains. Log in to each remote machine. Set the JAVA_HOME environment variable: (Unix) setenv JAVA_HOME=APPLICATIONS_BASE/fusionapps/jdk6 (Windows) set JAVA_HOME=APPLICATIONS_BASE\fusionapps\jdk6 Go to the directory that contains RUP Lite for Domain Configuration: (Unix) cd APPLICATIONS_CONFIG/fapatch/admin/ruplitedomain/RUP_version/bin (Windows) cd APPLICATIONS_CONFIG\fapatch\admin\ruplitedomain\RUP_version\bin Run RUP Lite for Domain Configuration. Note that RUP Lite cannot be run in parallel on remote servers and it does not have to be run from the primordial host where you started RUP Installer. It must be run on one server at a time. (Unix) ./ruplite.sh (Windows) ruplite.bat Ensure that you run RUP Lite for Domain Configuration on each server that contains local domains. Click OK to proceed to the second installer.

Start the Node Manager and OPMN server when the Welcome screen of the second installer displays.
- Start the Node Manager on all hosts that are part of the Oracle Fusion Applications provisioned system. For more information, see "Task 3: Start Node Manager" in Oracle Fusion Applications Administrator's Guide.
- Start the OPMN server for BI, GOP (if GOP is installed), and Web Tier. If you run the Web Tier (OHS) installed with the Oracle Fusion Applications middle tier, you can start it using the following steps. If you run the Web Tier on a separate machine, you may be able to run the following steps on the other machine. In either case, ensure that Web Tier (OHS) is up at this point.
  
  Example for BI: (note the usage of start instead of startall)
```
(Unix)
cd APPLICATIONS_CONFIG/BIInstance/bin
./opmnctl start

(Windows)
cd APPLICATIONS_CONFIG\BIInstance\bin
opmnctl.bat start
```
  Example for GOP: (note the usage of start instead of startall) Note that the OPMN server for GOP should be started from the machine that runs the Advanced Planning Managed Server. Start the OPMN server for GOP only if you have GOP installed.
```
(Unix)
cd APPLICATIONS_CONFIG/gop_1/bin
./opmnctl start

(Windows)
cd APPLICATIONS_CONFIG\gop_1\bin
opmnctl.bat start
```
  Example for Web Tier: (note the usage of start instead of startall)
```
(Unix)
cd APPLICATIONS_CONFIG/CommonDomain_webtier/bin
./opmnctl start

(Windows)
cd APPLICATIONS_CONFIG\CommonDomain_webtier\bin
opmnctl.bat start
```
  For more information about the location of APPLICATIONS_CONFIG, see Section 5.3.1, "Before You Begin".
  
  The BI and Web Tier processes managed by OPMN are started by RUP Installer during the Starting All Servers configuration task. The GOP processes managed by OPMN must be started using Fusion Applications Control after RUP Installer completes, as described in Section 5.6.8, "Start the GOP Processes".

Click Cancel to exit out of the second installer. Then run the following command to start the second installer in GUI mode:

(Linux)
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] 
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory][-logfile log_file_name][-debug]
JVM_OPTIONS="-Xmx2048m -XX:MaxPermSize=1024m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=path_of_the_dump_file" 

(IBM AIX on POWER Systems (64-bit)
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] 
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory][-logfile log_file_name][-debug] 
JVM_OPTIONS="-Xms1024m -Xmx2048m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=path_of_the_dump_file"

(Solaris X64 and Solaris Sparc) 
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] 
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory][-logfile log_file_name][-debug] 
JVM_OPTIONS="-d64 -Xms512m -XX:MaxPermSize=1024m -Xmx2048m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=path_of_the_dump_file"

(Windows)%REPOSITORY_LOCATION%\installers\farup\Disk1\setup.exe -jreLoc
APPLICATIONS_BASE\fusionapps\jdk6 [-Dworkers=number_of_workers][-DlogLevel=level] 
[-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-DpatchDownloadLocation=patch_directory][-logfile log_file_name][-debug]
"-Xmx2048m -XX:MaxPermSize=1024m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=path_of_the_dump_file"

Table 5-13 RUP Installer Screen Sequence for the Second Installer

Screen	Description and Action Required
Welcome	Appears when the second installer starts. Click Next to continue.
Installation Location	Specify the location of the existing Oracle Fusion Applications home (`FA_ORACLE_HOME)`. Click Next to continue.
Installation Summary	Summarizes the selections you made during this installation session. It includes the Oracle home, required and available disk space, and the version of the release to be installed. Review the information displayed to ensure that the installation details are what you intend. To make changes before installing, click Back to return to previous screens in the interview. Click Install to accept this configuration and start the second installer.
Installation Progress	Displays a progress indicator that shows the percentage of the installation phase that is complete and indicates the location of the installation log file. The installation task consists of copying files to the appropriate Oracle homes that are related to configuration tasks run during the second installer. When the installation progress indicator shows 100 percent, click Next to continue.
Policy Store Analysis (Note that if you installed a Language Pack and chose to override the base English strings in the policy store, then this screen no longer displays.)	Analysis is available for the following policy store stripes: hcm, crm, fscm, and obi. Select the stripes to be analyzed and then click Run Analysis to identify any conflicts or deletions. Only the stripes that will be updated are enabled for analysis and the analysis could run for several minutes. After the analysis runs, review the results of the analysis to determine which deployment method RUP Installer will use for policy store changes to each stripe. Oracle recommends that you select Apply safe changes only. This is the safest method unless you have read and totally understood the consequences of the other three options. If you decide to resolve the conflicts or deletions before the actual JAZN upload from RUP Installer, you should run the Policy Store Analysis step again to get the most accurate analysis report. The choices for deployment method are: Apply safe changes only (choose this method if there are no conflicts) Apply all changes and overwrite customizations Append additive changes Manually resolve conflicts and upload changes using Authorization Policy Manager If you choose Apply safe changes only or Append additive changes, then you must review the results of the analysis to manually upload any changes not applied by RUP Installer with the choice you selected, after the upgrade is complete. If you choose Apply all changes and overwrite customizations, then you may need to reapply the customizations that are overwritten after the upgrade is complete. If you choose one of these options, click Next after you make your selection. If you choose Manually resolve conflicts and upload changes using Authorization Policy Manager (APM), you must pause the upgrade while you bring up the APM application and upload the changes. For more information, see the "Upgrading Oracle Fusion Applications Policies" chapter in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition). Note the location of the following files: Baseline file: `FA_ORACLE_HOME/admin/JAZN/stripe/baseline` Patch file for fscm, crm, and hcm stripes: `FA_ORACLE_HOME/stripe/deploy/system-jazn-data.xml` Patch file for the obi stripe: `FA_ORACLE_HOME/com/acr/security/jazn/bip_jazn-data.xml` When you complete this task in APM, shut down the APM application, return to RUP Installer, and click Next.
Configuration Progress	Displays a progress indicator that shows the percentage of the configuration phase that is complete. It displays each task, including steps within tasks, in the message pane as they are performed. Tasks that could be included in the second installer's configuration phase are described in Table 5-2. Before the Starting All Servers task, the Verifying Node Manager and OPMN Status configuration task checks for access to the Node Manager and the OPMN control process. This may fail if you did not start the Node Manager and OPMN processes after the completion of the first installer. Do not cancel and exit out of RUP Installer in response to this task. For more information, see Section 5.7.19, "Troubleshooting Failure During Verifying Node Manager and OPMN Status". No additional user action is required in the Configuration Progress screen unless a failure occurs. For more information, see Section 5.7.4, "General Troubleshooting During the Configuration Phase in GUI Mode". Links to specific configuration task failures are available in Table 5-2.
Installation Complete	Summarizes the installation just completed. If you want to save this configuration to a response file, click Save. For more information, see "How Response Files Work" in the Oracle Database Installation Guide 11g Release 2 (11.2) for Linux. To complete a successful installation, click Finish. The Finish button is activated only if all mandatory configuration tasks completed successfully. If you want to rerun this session to resolve failed configuration tasks, click Cancel.

Proceed to Section 5.6, "Complete the Post Upgrade Tasks".

5.5.2 Run RUP Installer in Silent Mode

Perform the following steps to start RUP Installer in silent mode from the command line, using specific options to further define the necessary actions. You must run RUP Installer from the primordial host.

Create a response file named silent.rsp to be used in silent mode. This file can be located in any directory that is accessible while launching RUP Installer. An example follows:
```
ORACLE_HOME=/u01/APPLTOP/fusionapps/applications
CRM_SELECTED_JAZN_MIGRATION_TYPE=PATCH_POLICY
FSCM_SELECTED_JAZN_MIGRATION_TYPE=PATCH_POLICY
HCM_SELECTED_JAZN_MIGRATION_TYPE=PATCH_POLICY  
OBI_SELECTED_JAZN_MIGRATION_TYPE=PATCH_POLICY
```
Note:

The stripe_SELECTED_JAZN_MIGRATION_TYPE properties allow you to choose which deployment method RUP Installer will use for policy store changes to each stripe. The following choices are available:
- PATCH_POLICY: Apply safe changes only. This is the recommended method. Choose this method if there are no conflicts.
- MIGRATE_POLICY_OVERRIDE: Apply all changes and overwrite customizations.
- MIGRATE_POLICY_NO_OVERRIDE: Append additive changes.
- MIGRATE_POLICY_APM: Manually resolve conflicts and upload changes using Authorization Policy Manager (APM)
If you choose PATCH_POLICY or MIGRATE_POLICY_NO_OVERRIDE, then you must review the results of the analysis to manually upload any changes not applied by RUP Installer, based on the choice you selected, after the upgrade is complete. If you choose MIGRATE_POLICY_OVERRIDE, then you may need to reapply the customizations that are overwritten after the upgrade is complete.

If you choose MIGRATE_POLICY_APM, you must pause the upgrade while you bring up the APM application and upload the changes. For more information, see the "Upgrading Oracle Fusion Applications Policies" chapter in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition). Note the location of the following files:
- Baseline file: FA_ORACLE_HOME/admin/JAZN/stripe/baseline
- Patch file for fscm, crm, and hcm stripes: FA_ORACLE_HOME/stripe/deploy/system-jazn-data.xml
- Patch file for the obi stripe: FA_ORACLE_HOME/com/acr/security/jazn/bip_jazn-data.xml

Set the JAVA_HOME environment variable as follows:

(Unix) setenv JAVA_HOME APPLICATIONS_BASE/fusionapps/jdk6

(Windows) set JAVA_HOME=APPLICATIONS_BASE\fusionapps\jdk6

Confirm the registration of the network location of FA_ORACLE_HOME.

If the Oracle Fusion Applications Oracle home directory (FA_ORACLE_HOME), which is APPLICATIONS_BASE/fusionapps/applications, is registered in the central inventory with a /net path, then provide the oraInst.loc location including /net when starting RUP Installer. An example follows:
```
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc APPLICATIONS_BASE/fusionapps/jdk6/ 
-invPtrLoc /net/APPLICATIONS_BASE/fusionapps/applications/oraInst.loc -silent -response location_of_response_file JAZN_EXIST=true
```
If not triggered with /net path, RUP Installer copies the -invPtrLoc file to FA_ORACLE_HOME. In the example, this results in a copy of the file to itself, which then becomes an empty or zero byte file. As a result, the copy phase will fail when oracle_common patches are applied. For more information, see Section 5.7.2.4, "Inventory Pointer File is Empty".

Run the following command to start the first installer in silent mode:

Note:

Refer to Section 5.7.5, "General Troubleshooting During the Configuration Phase in Silent Mode" if any failures occur.

(Linux)
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] -silent
-response location_of_silent.rsp_file JAZN_EXIST=true
JVM_OPTIONS="-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=path_of_the_dump_file
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory] [-waitForCompletion yes]
[-logfile log_file_name][-debug]

(IBM AIX on POWER Systems (64-bit))
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] -silent
-response location_of_silent.rsp_file JAZN_EXIST=true
JVM_OPTIONS="-Xmx2048m -XX:MaxPermSize=1024m -d64 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=path_of_the_dump_file"
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds] 
[-J-DpatchDownloadLocation=patch_directory] [-waitForCompletion yes]
[-logfile log_file_name][-debug] 

(Solaris X64 and Solaris Sparc) 
$REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] -silent
-response location_of_silent.rsp_file JAZN_EXIST=true
JVM_OPTIONS="-d64 -Xms512m -XX:MaxPermSize=1024m -Xmx2048m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=path_of_the_dump_file"
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory] [-waitForCompletion yes]
[-logfile log_file_name][-debug] 

(Windows)
%REPOSITORY_LOCATION%\installers\farup\Disk1\setup.exe -jreLoc
APPLICATIONS_BASE\fusionapps\jdk6 [-Dworkers=number_of_workers][-DlogLevel=level] -silent
-response location_of_silent.rsp_file JAZN_EXIST=true
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=path_of_the_dump_file
[-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-DpatchDownloadLocation=patch_directory] [-waitForCompletion yes]
[-logfile log_file_name][-debug]

Table 5-14 shows valid options that can be used when running RUP Installer in silent mode.

Table 5-14 RUP Installer command options in silent mode

Option Name	Description	Mandatory
`-jreLoc`	Path where the Java Runtime Environment is installed. This option does not support relative paths, so you must specify the absolute path.	Yes.
`-invPtrLoc`	The location of an overriding inventory pointer file. If Oracle Fusion Applications Oracle home directory (FA_ORACLE_HOME) is registered in inventory with a `/net` path, then provide the location of `oraInst.loc` including `/net` in the path.	Recommended, use to override the default location of the inventory pointer file, located in `/etc/oraInst.loc.` This option can be used only on Unix platforms.
`-silent`	Run RUP Installer in silent mode.	Yes.
`-response`	The location of the response file named `silent.rsp`.	Yes.
`JAZN_EXIST`	Required for the Deploying Applications Policies configuration task.	Yes, always set to true.
`JVM_OPTIONS`	Use " -Xmx2048m -XX:MaxPermSize=1024m"	Yes.
`-J-Dworkers` (-`Dworkers` for Windows)	The number of workers to use for uploading database content. If you provide a value for the number of workers that is outside the calculated range, you are prompted to provide a value that is within the optimal range. If you do not use this option, a calculated optimal value is used.	No, overrides the default number of workers calculated by RUP Installer. See "Worker Calculation" in Section 3.1.2, "Patching Database Artifacts".
`-J-DlogLevel` (-`DlogLevel` for Windows)	Records messages in the log file at the level you specify. Enter a value to override the default log level of `INFO`. See Section 11.1, "Oracle Fusion Applications Patch Manager Logging".	No, default value is `INFO`.
`-J-DserverStartTimeout` (`-DserverStartTimeout` for Windows)	Configures the timeout value for server in seconds.	No, overrides the default value for server timeout.
`-J-DpatchDownloadLocation` (`-DpatchDownloadLocation` for Windows)	The directory path where you downloaded mandatory prerequisite patches to be applied by RUP Installer. See Section 5.3.6, "Download Mandatory Post Release 5 Patches".	No, the default is `APPLICATIONS_BASE/../post_repo_patches`.
`-waitForCompletion`	Causes the installer to wait for the completion of all operations, including the configuration assistants, instead of spawning the Java engine and exiting.	No, default value is No.
`-debug`	Retrieves the debug information from RUP Installer.	No.

After the first installer completes successfully, run RUP Lite for Domain Configuration on all servers that contain local domains. You can skip this step if the environment does not contain any local domains. Local domains are those that are hosted on the local storage of various hosts, rather than in shared storages.

Note that this step is not required for Oracle VM environments, as Oracle VM environments do not use local domains.

Perform the following steps:
1. Log in to each remote machine.
  
  Set the JAVA_HOME environment variable:
```
(Unix) setenv JAVA_HOME=APPLICATIONS_BASE/fusionapps/jdk6
(Windows) set JAVA_HOME=APPLICATIONS_BASE\fusionapps\jdk6
```
2. Go to the directory that contains RUP Lite for Domain Configuration:
```
(Unix) cd APPLICATIONS_CONFIG/fapatch/admin/ruplitedomain/RUP_version/bin
(Windows) cd APPLICATIONS_CONFIG\fapatch\admin\ruplitedomain\RUP_version\bin
```
3. Run RUP Lite for Domain Configuration. Note that RUP Lite cannot be run in parallel on remote servers and it does not have to be run from the primordial host where you started RUP Installer. It must be run on one server at a time.
```
(Unix) ./ruplite.sh
(Windows) ruplite.bat
```
Perform the following steps to start the Node Manager and the OPMN server for BI, GOP, and Web Tier.
1. Start the Node Manager on all hosts that are part of the Oracle Fusion Applications provisioned system. For more information, see "Task 3: Start Node Manager" in Oracle Fusion Applications Administrator's Guide.
2. Start the OPMN server for BI, GOP (if GOP is installed), and Web Tier. If you run the Web Tier (OHS) installed with the Oracle Fusion Applications middle tier, you can start it using the following steps. If you run the Web Tier on a separate machine, you may be able to run the steps below on the other machine. In either case, ensure that Web Tier (OHS) is up at this point.
  
  Example for BI: (note the usage of start instead of startall)
```
(Unix)
cd APPLICATIONS_CONFIG/BIInstance/bin
./opmnctl start

(Windows)
cd APPLICATIONS_CONFIG\BIInstance\bin
opmnctl.bat start
```
  Example for GOP: (note the usage of start instead of startall) Note that the OPMN server for GOP should be started from the machine that runs the Advanced Planning Managed Server. Start the OPMN server for GOP only if you have GOP installed.
```
(Unix)
cd APPLICATIONS_CONFIG/gop_1/bin
./opmnctl start

(Windows)
cd APPLICATIONS_CONFIG\gop_1\bin
opmnctl.bat start
```
  Example for Web Tier: (note the usage of start instead of startall)
```
(Unix)
cd APPLICATIONS_CONFIG/CommonDomain_webtier/bin
./opmnctl start

(Windows)
cd APPLICATIONS_CONFIG\CommonDomain_webtier\bin
opmnctl.bat start
```
  For more information about the location of APPLICATIONS_CONFIG, see Section 5.3.1, "Before You Begin".
  
  The BI and Web Tier processes managed by OPMN are started by RUP Installer during the Starting All Servers configuration task. The GOP processes managed by OPMN must be started using Fusion Applications Control after RUP Installer completes, as described in Section 5.6.8, "Start the GOP Processes".

Run the following command to start the second installer in silent mode:

Note:

If RUP Installer encounter errors in silent mode, see Section 5.7.5, "General Troubleshooting During the Configuration Phase in Silent Mode".

(UNIX)
$REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] -silent
-response location_of_silent.rsp_file JAZN_EXIST=true
JVM_OPTIONS="-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=path_of_the_dump_file
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory] [-waitForCompletion yes]
[-logfile log_file_name][-debug]

(IBM AIX on POWER Systems (64-bit)
$REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] -silent
-response location_of_silent.rsp_file JAZN_EXIST=true
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory][-waitForCompletion yes]
[-logfile log_file_name][-debug] 
JVM_OPTIONS="-Xms1024m -Xmx2048m"

(Solaris X64 and Solaris Sparc) 
$REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -jreLoc
APPLICATIONS_BASE/fusionapps/jdk6/ [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] -silent
-response location_of_silent.rsp_file JAZN_EXIST=true
[-J-Dworkers=number_of_workers][-J-DlogLevel=level] 
[-J-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-J-DpatchDownloadLocation=patch_directory] [-waitForCompletion yes]
[-logfile log_file_name][-debug] 
JVM_OPTIONS="-d64 -Xms512m -XX:MaxPermSize=1024m -Xmx2048m"

(Windows)%REPOSITORY_LOCATION%\installers\fusionapps\Disk1\setup.exe -jreLoc
APPLICATIONS_BASE\fusionapps\jdk6 [-Dworkers=number_of_workers][-DlogLevel=level] -silent
-response location_of_silent.rsp_file JAZN_EXIST=true
[-DpatchDownloadLocation=patch_directory][-waitForCompletion yes]
[-logfile log_file_name] 
[-DserverStartTimeout=timeout_period_for_server_in_seconds]
[-debug]

The following configuration assistants are skipped when you run RUP Installer in silent mode:
- Generating OHS Reference Configuration File
- Importing Image Routing (IPM) Artifacts
- Deploying SPE Inline Service Artifacts
- Deploying Data Role (RGX) Templates
- Deploying B2B Metadata
- Deploying SOA Composites
To ensure that these configuration assistants run, you must restart RUP Installer. Before restarting RUP Installer, perform the following steps:
1. If the FA_ORACLE_HOME/patchsettop/mw_patchset_manifest.xml file exists, you can proceed with the restart.
2. If this file does not exist, restore it from FA_ORACLE_HOME/patchsettop/backup. The complete backup location is determined by the "Metadata Backup" property in oraInventory/checkpoint/11.1.5.0.0/farup/checkpoint.xml. The pattern for the location is FA_ORACLE_HOME/patchsettop/backup/11.1.1.5.0/timestamp.
  
  The following example shows the "Metadata Backup" property in the checkpoint file:
```
<aggregate name="Metadata Backup" status="fail">
      <property name="Patchsettop_Backup_Location"
value="/u01/APPLTOP/fusionapps/applications/patchsettop/backup/11.1.5.0.0/en_US/2012-11-26_11-12-07AM"/>
</aggregate>
```
3. The following example shows the command to restore the mw_patchset_manifest.xml file.
```
cp -r /u01/APPLTOP/fusionapps/applications/patchsettop/backup/11.1.5.0.0/2012-11-26_11-12-07AM 
/u01/APPLTOP/fusionapps/applications/patchsettop/
```
After you restart RUP Installer and the configuration assistants mentioned in Step 8 complete successfully, proceed to Section 5.6, "Complete the Post Upgrade Tasks".

5.6 Complete the Post Upgrade Tasks

Perform the following required manual steps after RUP Installer completes successfully.

Complete the Web Tier Upgrade Using RUP Lite for OHS
Run RUP Lite for OVM - Online (Oracle VM Hosts Only)
Run RUP Lite for BI
Invoke an Instance of SOA Composite
Confirm All Database Artifact Deployments Were Successful
Review Log Files for Errors or Exceptions
Verify the Status of Servers and Deployed Applications
Start the GOP Processes
Reload Custom Templates for BI Publisher Reports
Add Administration Servers to the Machine Created During Scaleout
Disable Anonymous Binds in Oracle Internet Directory (OID)
Review the Policy Store (JAZN) Analysis Reports
Perform Steps in Release Notes
Resolve Conflicts That Occurred During BI Metadata Updates
Perform Upgrade Steps for Oracle Business Intelligence Applications
Upgrade Installed Languages
Update CrashRecoveryEnabled Property to "true"

5.6.1 Complete the Web Tier Upgrade Using RUP Lite for OHS

RUP Lite for OHS manages the steps required to update WebGate, OHS, and ORACLE_COMMON. The following steps are performed by RUP Lite for OHS to accomplish this upgrade:

Stop Oracle Process Manager and Notification Server (OPMN) processes and start the OPMN server.
Apply OPatches from the repository to WebGate, OHS, and ORACLE_COMMON.
Apply downloaded OPatches to WebGate, OHS, and ORACLE_COMMON.
Update the OHS configuration files.
Apply OHS settings changes.
Start the OHS instance.

Perform the following steps to complete the Web Tier upgrade using RUP Lite for OHS. Note that you must run RUP Lite for OHS from the OHS host. If you are on Windows, perform the steps in Section 5.6.1.1, "Windows Steps Before Running RUP Lite for OHS" first.

Verify that the RUP Installer configuration task, Generating RUP Lite for OHS, configuration task was successful.
Copy webgate_installer_11.1.5.0.0.zip, which was generated by the RUP Installer configuration task, Generate RUP Lite for OHS, to /scratch/RUPLiteREPO, for example.
```
cp FA_ORACLE_HOME/admin/webgate_installer_11.1.5.0.0.zip /scratch/RUPLiteREPO 
```
Note that if the Web tier is on a separate host, then copying the zip file may not work. In this case, you may need to ftp the zip file to the OHS host instead.
Unzip webgate_installer_11.1.5.0.0.zip into the /scratch/RUPLiteREPO directory, which is referred to as the RUP Lite for OHS repository, or RUPLITE_REPO, in the remaining steps.

Set the JAVA_HOME environment variable to the java_home_location.

(Unix) setenv JAVA_HOME java_home_location
(Windows) set JAVA_HOME=java_home_location

Update the RUPLITE_REPO/metadata/env.properties file to set the environment variables required by RUP Lite for OHS. An example of env.properties follows:

# MIDDLEWARE_HOME - Points to the Middleware home location where the webtier,
# webgates and oracle_common are held
# Example: /oracle/work/MW_HOME
MIDDLEWARE_HOME=/APPTOP/webtier_mwhome
 
# OHS_ORACLE_HOME - Points to the webtier (OHS) home location (typically inside
# your MIDDLEWARE_HOME)
# Example: /oracle/work/MW_HOME/Oracle_WT1
OHS_ORACLE_HOME=/APPTOP/webtier_mwhome/webtier
 
# OHS_INSTANCE_HOME - Points to the specific webtier (OHS) instance on which the
# ruplite utility would be applied
# Example: /oracle/work/MW_HOME/Oracle_WT1/instances/instance1
OHS_INSTANCE_HOME=/APPTOP/instance/CommonDomain_webtier
 
# OHS_INSTANCE_ID - This value is the name of the webtier (OHS) instance that is
# going to be upgraded using the ruplite utility.
# Please note that variable is not a path, but simply a string name of the
# instance in question
# Example: ohs1
OHS_INSTANCE_ID=ohs1

You can update the RUPLITE_REPO/metadata/env.properties manually or you can use the ruplite.plugin.SetEnv plugin.

The command syntax for the ruplite.plugin.SetEnv follows:

RUPLITE_REPO/bin/ruplite.sh -m ruplite.plugin.SetEnv VARIABLE1 VALUE1 VARIABLE2 VALUE2 VARIABLE3 VALUE3

An example of ruplite.plugin.SetEnv usage follows. Note that this should be run as one line with no carriage returns after you set the JAVA_HOME environment variable.

RUPLITE_REPO/bin/ruplite.sh -m ruplite.plugin.SetEnv MIDDLEWARE_HOME /APPTOP/webtier_mwhome 
OHS_ORACLE_HOME /APPTOP/webtier_mwhome/webtier
OHS_INSTANCE_HOME /APPTOP/instance/CommonDomain_webtier
OHS_INSTANCE_ID ohs1

Follow the steps in the README.txt file of patch 14543240 to run the script to remove conflicting patches on the OHS host. You downloaded patch 14543240 in Section 5.3.5, "Find Conflicting Patches".

Ensure that you run this script only before upgrading. If you run this script at any time other than before upgrading, the system may be left in an unstable state.
Run RUP Lite for OHS from the OHS host:
```
cd RUPLITE_REPO
bin/ruplite.sh
```
If this utility completes with errors or warnings, you must resolve the issue, and then run the utility again. When you restart the ruplite utility, all failed steps run again.

To verify that RUP Lite for OHS was successful, review the results in the following files:

RUPLITE_REPO/ohs_bundle/techpatch/ohs/patch_validate_results.xml
RUPLITE_REPO/ohs_bundle/techpatch/ohs_manual_download/patch_validate_results.xml

Note:

If you have multiple instances of OHS, then you must repeat the steps in this section for each OHS instance. When you need to upgrade more than one Web tier instance, one of two scenarios applies to your environment, as follows:

If the same RUPLITE_REPO needs to be used for more than one Web tier instance, you must back up and remove the checkpoint file located in the RUPLITE_REPO/output/checkpoint directory before each upgrade.
If you copy and unzip the original RUPLITE_REPO to each Web tier instance, there is no requirement to remove the checkpoint file.

Ensure that you set the correct environment variable value for OHS_INSTANCE_ID before running the ruplite utility.

5.6.1.1 Windows Steps Before Running RUP Lite for OHS

Perform the following steps before running RUP Lite for OHS if you are on Windows:

Replace the Opatch under RUPLITE_ROOT\ohs_bundle with the 11.1.0.9.8 version of Opatch. The 11.1.0.9.8 version of Opatch can be copied from APPLICATIONS_BASE\fusionapps\applications.
Shutdown OPMN and OHS before starting Rup Lite for OHS:
```
opmnctl stopall 
```

In APPLICATIONS_BASE\ruplite_ga\metadata\plugin-metadata.txt, move the step ohs.plugin.StopAllOPMN to just before the ohs.plugin.StartOHS step. The recommended sequence is:

ohs.plugin.Initialize
ohs.plugin.ApplyOPatches
ohs.plugin.UpdateOHSConfFiles
ohs.plugin.ApplySettingsChanges
ohs.plugin.StopAllOPMN
ohs.plugin.StartOHS
ohs.plugin.Cleanup

5.6.2 Run RUP Lite for OVM - Online (Oracle VM Hosts Only)

Table 5-15 describes the plug-ins that are included in RUP Lite for OVM in online mode.

Table 5-15 Online Plug-ins for RUP Lite for OVM

Plugin Name	Mandatory	Description
ValidateEnvironment	Yes	Checks if the node is a valid Oracle VM node. This plugin always runs and does not have any properties.
SetupCredentials	Yes	Prompts for credentials and stores the results in a secure manner for other plugins to use. This plugin always runs and only prompts for secure properties that are needed by other plugins that will execute. If a plugin does not run on the current node or is disabled, then its properties are not requested.
InstallStartStop	Yes	Installs start and stop functionality that automatically restarts servers when a host is restarted.
SetSOAFTPAdapter	Yes	Configures the SOA FTP Adapter for the `FinancialDomain` in a two step process.From the `AdminServer` of the `CommonDomain`, it creates the SOA FTP adapter deployment plan, using the user, password, host, and port passed in by the plugin. Then from the `FinancialDomain`, it configures the `AdminServer` of the `FinancialDomain` to reference this deployment plan. This plugin runs only on the `admin-apps` node.

Perform the following steps to run RUP Lite for OVM in online mode.

Update Properties File
Run RUP Lite for OVM in Online Mode

5.6.2.1 Update Properties File

Update the env.properties file under the rupliteframework/metadata directory with the required property values for the following plugins:

InstallStartStop

ovm.plugin.InstallStartStop.enabled=true

SetSOAFTPAdapter

This property is applicable only for FSCM or FSCM-H Oracle VM topology environments where an FTP server has been set up. You must obtain FTP connectivity information and credentials from your administrators, enable the plugin, and respond to the prompts. If no FTP server is setup, you can disable this plugin by setting the ovm.plugin.SetSOAFTPAdapter property to false.
```
ovm.plugin.SetSOAFTPAdapter.enabled=true
ovm.plugin.SetSOAFTPAdapter.soa_ftp_username=USERNAME
ovm.plugin.SetSOAFTPAdapter.soa_ftp_host=sftp.cloud.mycompany.com
ovm.plugin.SetSOAFTPAdapter.soa_ftp_port=4321
```

5.6.2.2 Run RUP Lite for OVM in Online Mode

Run RUP Lite for OVM on each node of your Oracle VM environment, from the directory you created in Section 5.4.11.4, "Repeat Steps On All Nodes Of Your Oracle VM Environment". Note that you must run RUP Lite for OVM as the root user.

Set the JAVA_HOME directory, for example:
```
setenv JAVA_HOME /assemblybuild/jre
```
Examples of jre locations for other nodes follow:
- AuthOHS Node: /u01/ohsauth/oracle_common/jdk
- OIM Node: /u01/oim/jrockit_160_24_D1.1.2-4
- OID Node: /u01/oid/oracle_common/jdk
Run ruplite.sh from the ruplite-ovm directory.
```
cd /ruplite-ovm
bin/ruplite.sh online-plugin-metadata.txt
```
Note that online-plugin-metadata.txt should be specified without a path, as it is simply the name of the plug-in metadata file.

Respond to the following prompts, which will be stored in a wallet file in the ruplite-ovm/output/wallet directory.

RUP Lite Wallet Key: If a wallet already exists, enter the value for the existing key. If the wallet does not exist, 
a new one will be created using the key you provide.
The key must be at least 8 characters long and include at least one numeric character

SOA FTP Password: Secure File Transfer Protocol (FTP) for SOA server

For information about troubleshooting, see Section 5.4.11.5, "Troubleshoot RUP Lite for OVM".

5.6.3 Run RUP Lite for BI

The RUP Lite for BI utility automates changes to BIInstance configurations files required for Oracle Business Intelligence after upgrading.

RUP Lite for BI is located in BI_ORACLE_HOME/biapps/tools/lib/biruplite.jar. Before you run RUP Lite for BI, ensure that BI_ORACLE_HOME and BI_DOMAIN_HOME are configured properly with the correct permissions. For example, BI_INSTANCE_HOME must have read/write access for the user who runs RUP Lite for BI. BI_ORACLE_HOME is the Oracle home for BI, typically located at APPLICATIONS_BASE/fusionapps/bi. BI_DOMAIN_HOME is the home directory for the BI Domain, typically located at APPLICATIONS_CONFIG/domains/host/BIDomain, where host is the BI host.

Run RUP Lite for BI from the BI host, using the following command syntax:

(Unix)
java -jar BI_ORACLE_HOME/biapps/tools/lib/biruplite.jar BI_DOMAIN_HOME BI_ORACLE_HOME 

(Windows)
java -jar BI_ORACLE_HOME\biapps\tools\lib\biruplite.jar BI_DOMAIN_HOME BI_ORACLE_HOME

Example:

cd /APPTOP/fusionapps/bi/biapps/tools/lib 

java -jar biruplite.jar /APPTOP/instance/domains/server04.mycompany.com/BIDomain /APPTOP/fusionapps/bi

Note:

If you have multiple instances of BIInstance, then you must run RUP Lite for BI on each BI host.

If the utility encounters any errors, RuntimeException reports those errors. The output from the utility also contains information about any errors. After you resolve the cause of the errors, you can rerun biruplite.jar.

Perform the following steps to validate that the utility was successful:

Confirm that the BIInstance/Essbase/essbaseserver1/bin/esssql.cfg file contains the property ConvertUTF16toUTF8 1.
Confirm that the BIInstance/config/OracleBIPresentationServicesComponent/coreapplication_obips1/instanceconfig.xml file contains the property <UserprefCurrenciesConfigFile>/APPTOP/instance/BIInstance/config/OracleBIPresentationServicesComponent/coreapplication_obips1/userpref_currencies_OTBI.xml</UserprefCurrenciesConfigFile>.

5.6.4 Invoke an Instance of SOA Composite

You must run the UpdateSOAMDS SOA composite on every domain if you made any flexfield changes, by following the steps described in "Task: Synchronizing Customized Flexfields in the MDS Repository for SOA" in the Oracle Fusion Applications Extensibility Guide.

5.6.5 Confirm All Database Artifact Deployments Were Successful

Confirm that all database artifact deployments were successful by reviewing the Diagnostics report and log files. For more information, see Section 3.5.5, "Diagnostics Report".

5.6.6 Review Log Files for Errors or Exceptions

Confirm there are no unresolved errors or exceptions in the log files. For information about resolving errors, see Section 5.7, "Troubleshoot RUP Installer Sessions".

5.6.7 Verify the Status of Servers and Deployed Applications

Confirm that all relevant Managed Servers have a RUNNING status.
Verify that all deployed applications are up and running. You can check this from Fusion Applications Control, or by reviewing the server side log files. For more information, see "Starting Fusion Applications Control" in the Oracle Fusion Applications Administrator's Guide or Section 5.7.1, "RUP Installer Log File Directories".

5.6.8 Start the GOP Processes

Perform the following steps to start the GOP processes. Note that the opmnctl process for gop_1 should be started only on the host machine which contains the AdvancedPlanning Managed server. Do not start it on the primordial host.

Proceed to Step 2 if your GOP processes have been previously configured and have run before.

If you are starting GOP processes for the first time, confirm that a data source exists, in the form of XML files, under the APPLICATIONS_BASE/instance/gop_1/GOP/GlobalOrderPromisingServer1/datastore directory. Then run the RefreshOpDatastore ESS job by performing the following steps:
1. Ensure that the AdvancePlanning Managed Server is running in the SCM domain.
2. Invoke http://scm - AdvancePlanning managedserver:port/advancedPlanning/faces/MscCentralEssUi
3. In the bottom list applet click Actions, then Schedule New Process.
4. Select Search under Name, and query for %Order%.
5. Select Refresh Order Promising Data and click OK.
6. Select all of the check boxes in the Process Details popup.
7. You can customize some options in the Advanced pane, but this is not mandatory.
8. Click Submit and note the process ID.
9. After you confirm that the process is complete, you should see information from the log file that is similar to the following example:
```
Running RefreshOpDatastore Job...
Got service proxy successfully.
Got callback url successfully.
Getting the job-parameters in the Map.
Added job parameters in the map
Web service sucessfully invoked
***** callback received *****
Return Status of job is SUCCESS 
```
10. Proceed to Step 2.
Log in to Fusion Applications Control. For more information, see "Starting Fusion Applications Control" in the Oracle Fusion Applications Administrator's Guide.
Access GOP by navigating to Oracle Fusion Supply Chain Management, then Global Order Promising, then GlobalOrderPromisingServer1.
Click GlobalOrderPromisingServer1 to open the GlobalOrderPromisingServer1 page.
Select Control from the menu, then Start Up.

5.6.9 Reload Custom Templates for BI Publisher Reports

Follow this step if you have customized BI Publisher reports.

Reload custom templates for BI Publisher reports on Oracle-delivered BI Publisher reports by following the steps in "Task: Upload the Template File to the Report Definition" in the Oracle Fusion Applications Extensibility Guide.

5.6.10 Add Administration Servers to the Machine Created During Scaleout

Perform the steps in this section only if the steps in Section 5.3.15, "Validate Domain Directories" found domains that did not pass validation.

Log in to the WebLogic console for the domain.
Navigate to Environment, then Machines.
Find the machine that was created manually in or the purposes of AdminServer high availability scaleout.
Click on the machine and go to the Servers tab.
Click Lock & Edit to make changes.
Click Add.
Select the AdminServer and click Finish.
Click Activate Changes to apply the changes.

5.6.11 Disable Anonymous Binds in Oracle Internet Directory (OID)

Disable the anonymous binds that you enabled in Section 5.4.8, "Enable Anonymous Binds in Oracle Internet Directory".

Update the LDIF file so that the orclAnonymousBindsFlag has a value of 0.

Run the following command:

ldapmodify -D cn=orcladmin -Q -p portNum -h hostname -f ldifFile

For more information, see "Managing Anonymous Binds" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

5.6.12 Review the Policy Store (JAZN) Analysis Reports

Review the JAZN Analysis reports for potential conflicts and deletions that are not patched automatically by RUP Installer. The reports are located in this directory:

FA_ORACLE_HOME/admin/JAZN/stripe/delta/report.txt

The stripe is crm, fscm, hcm, or obi.

Review the Modification section of the report to see the roles that RUP Installer did not update. For each conflict that displays in this report, you must evaluate and manually patch the role by using APM. For more information, see "Upgrading Oracle Fusion Applications Policies" in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition).

The following example shows a typical Application Role conflict that has been modified by both the patch and production, therefore it is not applied by RUP Installer.

MODIFICATION CONFLICTS
Artifact type: Application Role 
Artifact Name: OBIA_PARTNER_CHANNEL_ADMINISTRATIVE_ANALYSIS_DUTY
Description: This artifact is modified at attribute level in patch version and also in production.

Note the location of the following files for reference when using APM:

Location of baseline files, where stripe is crm, fscm, hcm, or obi:
```
FA_ORACLE_HOME/admin/JAZN/stripe/baseline
```
Location of patch files for fscm, crm, and hcm stripes:
```
FA_ORACLE_HOME/stripe/deploy/system-jazn-data.xml
```

Location of patch files for the obi stripe:

FA_ORACLE_HOME/com/acr/security/jazn/bip_jazn-data.xml

5.6.13 Perform Steps in Release Notes

Follow any post upgrade steps mentioned in the Post Upgrade Known Issues section of Oracle Fusion Applications release notes.

5.6.14 Resolve Conflicts That Occurred During BI Metadata Updates

RUP Installer updates the applications policies for Oracle Business Intelligence during the Apply Offline BI Metadata and Configuration Updates configuration assistant. When RUP Installer runs the Apply Online BI Metadata and Configuration Updates configuration assistant, it updates the Oracle BI Applications metadata in the Oracle BI repository and the Oracle BI Presentation Catalog for Oracle Fusion Transactional Business Intelligence and Oracle Business Intelligence Applications.

Note:

This section refers to different Oracle BI directory paths. The BI Oracle home contains the binary and library files necessary for Oracle BI. BI_ORACLE_HOME represents the BI Oracle home in path names.

For more information about the Oracle BI directory structure, see "Oracle Business Intelligence Directory Structure" in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

Also, see "Understanding Oracle Fusion Middleware Concepts" in Oracle Fusion Middleware Administrator's Guide for information about the Fusion Middleware directory structure.

This section contains the following topics:

Resolving Conflicts in Oracle BI Presentation Catalog
Resolving Conflicts in Oracle Business Intelligence Policy Store

5.6.14.1 Resolving Conflicts in Oracle BI Presentation Catalog

When you run RUP Installer, the Oracle BI Metadata Update Tool overwrites all customizations to catalog objects in the Presentation Catalog with the new Oracle-supplied content and logs conflicts in a conflict report.

After RUP Installer completes, you must review the conflict report and decide whether you want to retain the new content or re-apply your customizations using a manual process.

Points to Consider

The folders /shared/backup/shared and /shared/backup/system are created in the updated Presentation Catalog during the RUP Installer and the Metadata Update Tool process. You access these folders through the Folders pane of the Catalog page in the Oracle BI Enterprise Edition user interface, as described in the procedure below.

Note: The /shared/backup folder should not exist before the RUP Installer is run, because the updated Presentation Catalog file will not be copied to this folder if it already exists.

As a precaution, to ensure the /shared/backup folder does not exist before the RUP Installer is run, you can optionally create an environment variable called webcat.force.restore, which will overwrite the contents of an existing /shared/backup folder.
Conflicts that arise during RUP Installer and the Metadata Update Tool process are stored in the folder /shared/backup/shared in the updated Presentation Catalog. Object references that have conflicts are also stored in /shared/backup/shared.

To resolve conflicts in the Presentation Catalog:

Locate the conflict report named update-conflict-report.txt, which is stored in the folder BI_ORACLE_HOME/.biapps_patch_storage/update/Run_ID.

A sample conflict report follows:
Sign in to Oracle Business Intelligence Enterprise Edition (Oracle BI EE).

See "Signing In to Oracle BI Enterprise Edition" and "Navigating Oracle BI Enterprise Edition" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition) for instructions on signing in and navigating the Oracle BI EE user interface.
Click Catalog in the global header.
In the Folders pane, navigate to the Shared Folders/backup/shared folder.
Open an object that has a conflict. This object depicts the state of the object before RUP Installer and the Metadata Update Tool were run.
Open a second instance of Oracle BI EE and the Presentation Catalog.
Navigate to the Shared Folders folder.
Open the same object you opened in step 5. This object depicts the state of the object after RUP Installer and the Metadata Update Tool were run (and after the metadata updates were applied).
Compare the two objects and decide whether you want to retain the Oracle-supplied update content or re-apply your customization from the previous version of the Presentation Catalog.
To re-apply your customization to an updated object, manually edit the object.
Repeat steps 5 through 10 for all objects that have conflicts.

5.6.14.2 Resolving Conflicts in Oracle Business Intelligence Policy Store

When you run RUP Installer, the Oracle BI Metadata Update Tool performs a safe upgrade on the Oracle Business Intelligence policy store, which means it updates only the metadata content that does not conflict with your customizations. Updated content that conflicts with your customizations is not applied. Conflicts are listed in the Oracle BI Metadata Tool update report, located at BI_ORACLE_HOME/.biapps_patch_storage/update/Timestamp/policystore_delta/report.txt.

This procedure provides instructions for overriding the customizations of the previous Oracle Business Intelligence policy store by applying the Oracle-supplied updated content. This procedure uses Oracle Authorization Policy Manager. For detailed information about upgrading Oracle Fusion Applications policies using Oracle Authorization Policy Manager, see "Upgrading Oracle Fusion Applications Policies" in Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition).

Note: You do not need to back up your existing policy store file, because the Metadata Update Tool process does not overwrite your customizations.

To resolve conflicts in the policy store:

Log into the Authorization Policy Manager Administration Console.

See "Getting Started With Oracle Authorization Policy Manager" in Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition) for instructions.
Navigate to the Home tab of the Policy Upgrade Management page.
Click Patch Application in the upper-left corner of the page to display the Patch Application dialog.
Select the appropriate application from the Application list.
In the Patch File field, specify the new patch file name and location, for example, BI_ORACLE_HOME/bifoundation/admin/provisioning/biapps-policystore.xml.
In the Baseline field, specify the previous policy store that was backed up by the Oracle BI Metadata Update Tool, for example, <BI_ORACLE_HOME>/.biapps_patch_storage_UPGRADE from VERSION/OH_BACKUP/bifoundation/admin/provisioning/biapps-policystore.xml.
Navigate to the Patch Details tab to view the policy store conflicts.

See the sections titled "Analyzing Patch Differences" and "Resolving Changes and Conflicts" in Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition) for instructions on taking the appropriate action regarding conflicts.

5.6.15 Perform Upgrade Steps for Oracle Business Intelligence Applications

If you are deploying Oracle Business Intelligence Applications, then you must perform the post-installation or upgrade steps specified in "Roadmap for Installing, Setting Up, and Upgrading Oracle BI Applications" in the Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.

5.6.16 Upgrade Installed Languages

If you have installed any languages in addition to US English, you must upgrade each installed language using Language Pack Installer. For more information, see Chapter 6, "Maintaining Oracle Fusion Applications Languages".

5.6.17 Update CrashRecoveryEnabled Property to "true"

You can skip this step unless you performed the step in Section 5.4.2.2, "Update "CrashRecoveryEnabled" Property to False". If you did perform this step, you must now set the CrashRecoveryEnabled property to "true" in the nodemanager.properties file for all domains in the following location:

APPLICATIONS_CONFIG/nodemanager/host

Note that the APPLICATIONS_CONFIG value can be obtained from the APPLICATIONS_BASE/fusionapps/faInst.loc file.

5.7 Troubleshoot RUP Installer Sessions

This section provides information to assist you in troubleshooting RUP Installer sessions. It contains the following topics:

RUP Installer Log File Directories
Troubleshooting Failures During the Installation Phase in GUI Mode
- CFGLOG-00056: Exception caught while getting node-manager homes
- Invalid Oracle Home
- Error in Writing to File, Text File Busy
- Inventory Pointer File is Empty
Failure During Analysis of Applications Policies
General Troubleshooting During the Configuration Phase in GUI Mode
General Troubleshooting During the Configuration Phase in Silent Mode
Recovering From a RUP Installer Session That Was Killed
The Next Button Is Not Enabled During Configuration Tasks
Troubleshooting Bootstrapping Patch Manager
Troubleshooting Applying Middleware Patches
Troubleshooting Upgrading Middleware Schema
Troubleshooting Failure During Propagating Domain Configuration
Troubleshooting Failure While Applying Downloaded Patches
Failure During Grant Privilege Scripts
Troubleshooting Loading Database Components
Troubleshooting Deployment of Applications Policies
Oracle BI Presentation Catalog Patch File Creation Failure
Updating BI Presentation Catalog to Resolve a Failure During Deploying BI Publisher Artifacts
Troubleshooting Failure During Verifying Node Manager and OPMN Status
Troubleshooting Server Start and Stop Failures
Failures During Online Preverification
Merging SOA Composite JDeveloper Customizations During RUP Installation
Location of GRC Policies in the OAM Applications Domain
Failure During IPM Import
Troubleshooting SOA Composite Deployment Failures
Troubleshooting Health Checker
AttachHome Script Hangs
The runInstaller.sh -updateHomeDeps Command Hangs
Perform Installation Verification Steps

5.7.1 RUP Installer Log File Directories

Table 5-16 contains a list of log directories for RUP Installer activities.

Table 5-16 Log Directories for RUP Installer Activities

Log directory name	Description
`oracle_inventory`/logs	Installation phase and Oracle Fusion Middleware patch set installation logs.
`FA_ORACLE_HOME`/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0	Top level directory for RUP Installer logs.
`FA_ORACLE_HOME`/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/ARCHIVE/`timestamp`	Top level log directory where log files are moved when you retry the installation session or you relaunch RUP Installer in silent mode.
`FA_ORACLE_HOME`/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/PatchManager_DBPatch	Database upload configuration task logs after failure or completion.
`FA_ORACLE_HOME`/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/StartStop	StartStop utility logs. Note that server logs are located under respective domains. For example, the AdminServer log for CommonDomain is under `APPLICATIONS_CONFIG/domains`/`hostname`/`CommonDomain/servers/AdminServer/logs`.
`FA_ORACLE_HOME`/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/soalogs	SOA artifacts configuration task logs. Note that SOA server logs are located under respective domains. For example, the SOA server logs for CommonDomain are under `APPLICATIONS_CONFIG/domains`/`hostname`/`CommonDomain/servers/soa_server1/logs.` For more information, see Section 5.7.25.1, "SOA Composite Log Files".
`FA_ORACLE_HOME`/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/PatchManager_DownloadedPatches	Applying Downloaded Patches configuration task logs.

During the execution of configuration tasks, log files are created under the FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_releasenumber directory. During the execution of the database upload configuration task, log files are created under the FA_ORACLE_HOME/admin/FUSION/log directory. Upon completion or failure of the database upload, the log files move to the FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_releasenumber/PatchManager_DBPatch directory. The current releasenumber is 11.1.5.0.0.

5.7.2 Troubleshooting Failures During the Installation Phase in GUI Mode

Follow these steps when an error occurs during the installation phase in GUI mode:

Click Cancel to exit RUP Installer.
Review the log files to determine the cause of the failure. The log files reside in oracle_inventory/logs/installtimestamp.log.
Resolve the cause of the failure.
Start RUP Installer using the same command syntax that you used for the previous incomplete installation. For more information, see Section 5.5.1, "Run RUP Installer in GUI Mode". After canceling the previous installation and starting again, you must choose to continue with the previously failed installation by clicking Yes on the Checkpoint Dialog. If the error is not recoverable, you can restore and restart from backup.
If you choose to continue with the failed installation, RUP Installer opens at the screen where it was canceled. When canceled during the copy action, it relaunches in the Installation Summary screen. Click Next to navigate through the Installation Summary screen. When the Installation Progress screen displays, click Install to start the installation again.

Troubleshooting steps are described for the following specific failures that may occur during the installation phase:

CFGLOG-00056: Exception caught while getting node-manager homes
Invalid Oracle Home
Error in Writing to File, Text File Busy
Inventory Pointer File is Empty

5.7.2.1 CFGLOG-00056: Exception caught while getting node-manager homes

Within a few seconds of starting the installer, you receive the following messages:

In the log file:

SEVERE: CFGLOG-00056 : Exception caught while getting node-manager homes

In the user interface:

CFGLOG-00052 : Error occurred while moving instance specific files

This failure is the result of having an incompatible version of OPatch in FA_ORACLE_HOME. To resolve the issue, download and apply patch 14044793, which contains the compatible version of OPatch.

5.7.2.2 Invalid Oracle Home

In the Installation Location page, you receive a message about entering an invalid Oracle home, even though the location displayed on the page is correct. RUP Installer reads /etc/oraInst.loc to determine the location of the central inventory. Review the following settings:

Ensure that the /etc/oraInst.loc file on the machine where you are running RUP Installer is pointing to the correct central inventory location.
Ensure that the FA_ORACLE_HOME matches the values provided during provisioning. If a /net/location was provided as the Oracle home location during provisioning, the same /net/location that corresponds to FA_ORACLE_HOME should be provided during the installation. You can find this location by following these steps:
- Open /etc/oraInst.loc and find the path to oraInventory, which is the central inventory, for example, server01/appmgr/APPTOP/oraInventory.
- Change directory to the ContentsXML directory under the central inventory, for example, server01/appmgr/APPTOP/oraInventory/ContentsXML.
- Open the inventory.xml file to find the correct directory path to FA_ORACLE_HOME.

5.7.2.3 Error in Writing to File, Text File Busy

During the installation phase of RUP Installer, you receive the following message on a Unix platform.

Error in writing to file'/server01/APPLICATIONS_BASE/fusionapps/applications/lcm/ad/bin/adctrl'
(Text file busy)

To resolve this issue, perform the following steps.

Run the lsof command using the full directory path of the file that is busy.
```
/usr/bin/lsof full_path_to_file
```
You should receive a list of process ids that are using the file. Kill each process using the appropriate command for your operating system.
After all processes are no longer running, click Continue in RUP Installer.

5.7.2.4 Inventory Pointer File is Empty

After running RUP Installer, the contents of oraInst.loc were removed.

RUP Installer always tries to copy the inventory pointer file specified by the -invPtrLoc option to the Oracle home on which the release is to be installed. If you specify an incorrect path for the -invPtrLoc file, the inventory pointer file could result in being an empty file. Review the following possible solutions for this issue:

For best results, if you are using the -invPtrLoc option, use it with this value: FA_ORACLE_HOME/oraInst.loc. This avoids a situation where you may inadvertently exclude part of the directory path to the file, as in the case of using a mapped drive. For example, if Oracle home is registered in inventory with a /net path, such as /net/home/oraInst.loc, and you provide /home/oraInst.loc to the invPtrLoc option, the installer interprets the two paths as different. The end result is an empty inventory pointer file.
If FA_ORACLE_HOME is registered in central inventory with a /net path, then you must include /net when specifying the location of the inventory pointer file with the -invPtrLoc option, for example, -invPtrLoc /net/directory_path/oraInst.loc.
Restore from a backup copy of your oraInst.loc file that was made in Section 5.4.6.1, "Back Up Oracle Fusion Applications", in case the original file is damaged.
You can recover from this error by creating a new oraInst.loc. See the "Creating the oraInst.loc File" section in the relevant Oracle Database installation guide, for example, Oracle Database Installation Guide, 11g Release 2 (11.2) for Linux.

Then click Retry in GUI mode or relaunch RUP Installer in silent mode.

5.7.3 Failure During Analysis of Applications Policies

If a failure occurs during applications policy analysis, review the log file that is generated by each stripe. These log files are located under the main log directory, FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/timestamp and are named as follows:

fapatch_CRMJaznAnalysis_timestamp.log
fapatch_FSCMJaznAnalysis_timestamp.log
fapatch_HCMJaznAnalysis_timestamp.log
fapatch_OBIJaznAnalysis_timestamp.log

After you resolve the JAZN analysis error, retry the analysis for the failed stripe to confirm the issue is resolved.

5.7.4 General Troubleshooting During the Configuration Phase in GUI Mode

RUP Installer can be restarted to rerun all failed configuration tasks as well as those tasks that were not started from the previous session. When a configuration task or step fails, the Configuration Progress screen displays the location of the log file and the exception that caused the failure. You can also view the contents of the log files that appear at the bottom of the screen to obtain detailed information to assist in diagnosing the cause of the failure.

If one or more failures occur during the configuration phase, after the final configuration task is complete, the following message displays:

Configuration is completed with errors, exit the installer by clicking the 'Cancel' button and retry the failed configurations.

Perform the following steps to rerun RUP Installer and retry the failed configuration tasks:

Click Cancel to exit RUP Installer.
Resolve the issues that caused the failure.
Start RUP Installer using the same command syntax that you used for the previous incomplete installation. For more information, see Section 5.5.1, "Run RUP Installer in GUI Mode".
A pop up dialog displays, asking if you want to continue the previous incomplete installation. Select Yes to continue running the previous session. If you select No, RUP Installer starts from the beginning and it will fail, indicating that a release cannot be installed again in the same environment. You would then need to restore from your backup and restart RUP Installer.
The Configuration Progress screen displays only the failed and remaining configuration tasks, and then runs these tasks.
Assuming all configuration tasks complete successfully, click Next to go to the Installation Complete screen and then click Finish to end the session. If a configuration task fails again and you want to attempt to run the session again, click Cancel to save the session. If all configuration tasks were successful, the second installer launches automatically. If all configuration tasks completed successfully, click Finish to end the session.

5.7.5 General Troubleshooting During the Configuration Phase in Silent Mode

RUP Installer can be restarted to rerun all failed configuration tasks as well as those tasks that were not started from the previous session. When a mandatory configuration task or step fails in silent mode, RUP Installer exits. After you resolve the issue that caused the failure, restart RUP Installer in GUI mode. When the installer restarts, it restarts from the first failed task.

When a non-mandatory task fails in silent mode, RUP Installer continues with the next configuration task and does not exit. You must review the logs to find any non-mandatory tasks that failed and then rerun RUP Installer in GUI mode until all tasks complete successfully.

To run RUP Installer in GUI mode, you must start it from the REPOSITORY_LOCATION/installers/farup/Disk1/ directory. For more information, see Section 5.5.1, "Run RUP Installer in GUI Mode".

5.7.6 Recovering From a RUP Installer Session That Was Killed

If RUP Installer is killed at any point during the upgrade, you must restore from the backup that you created in Section 5.4.6.1, "Back Up Oracle Fusion Applications", and restart from the beginning of the upgrade.

5.7.7 The Next Button Is Not Enabled During Configuration Tasks

On the Configuration Progress page of RUP Installer, the Next button is enabled only when all configuration tasks are successful.

If you see that all your configurations are complete, and the Next button is not enabled, you encountered a configuration failure and continued to the next configuration task. In this case, you must retry the failed configuration tasks by following these steps:

On the Configuration Progress page of RUP Installer, click Cancel.
Restart RUP Installer. All failed configuration tasks or steps rerun upon restart. For more information, see Section 5.7.4, "General Troubleshooting During the Configuration Phase in GUI Mode".

As long as a configuration task is not successful, the Next button remains disabled. It may be necessary to repeat the cancel and retry procedure until all configuration tasks are successful.

5.7.8 Troubleshooting Bootstrapping Patch Manager

An error during the Bootstrapping Patch Manager configuration task normally occurs only when the database is down. Ensure that the database is up and running. You can review the related log files in this location:

FA_ORACLE_HOME/admin/FUSION/log/FAPatchManager_bootstrap_timestamp.log

Another possible cause for the failure of the Bootstrapping Patch Manager configuration task could be that the UpdateBootstrapCredentials plugin for RUP Lite for OVM was run with an incorrect user name or password. If an incorrect user name or password was used, rerun the plugin with the correct user name and password. For more information, see Section 5.4.11, "Run RUP Lite for OVM - Offline (Oracle VM Hosts Only)".

5.7.9 Troubleshooting Applying Middleware Patches

If an error occurs during the Applying Pre-PSA Middleware Patches or Applying Post-PSA Middleware Patches configuration task, review the log file in the relevant location:

FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/ApplyPrePSAMiddlewarePatchestimestamp.log

FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/ApplyPostPSAMiddlewarePatchestimestamp.log

For specific OPatch failures, go to each of the individual Oracle home directories to find the details of the OPatch errors. For example, for a SOA failure, go to APPLICATIONS_BASE/fusionapps/soa/cfgtoollogs/opatch.

Note:

If you see the following error in FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/ApplyPrePSAMiddlewarePatchestimestamp.log, you can ignore it:

warning IOError: No such file or directory: ../../../applications/admin/FUSION_prov.properties

5.7.10 Troubleshooting Upgrading Middleware Schema

If an error occurs during the Upgrading Middleware Schema configuration task, review the log file in this location:

fusionapps/oracle_common/upgrade/logs/psatimestamp.log

5.7.11 Resolving Failure During Extending Certificate Validity

If an error occurs during the Extending Certificate Validity configuration assistant, cancel and restart RUP Installer to start running the remaining configuration assistants.

5.7.12 Troubleshooting Failure During Propagating Domain Configuration

This section contains information about troubleshooting issues that may occur during the Propagating Domain Configuration configuration task. The following topics are discussed:

Monitor the Propagating Domain Configuration Task
Confirm the Configuration Task Was Successful
Resolve Error Caused by WARs or EARs Not Accessible From The Primordial Host

5.7.12.1 Monitor the Propagating Domain Configuration Task

You can monitor the progress of this configuration task by reviewing log files in this location:

APPLICATIONS_CONFIG/fapatch/admin/ruplitedomain/version/output/logs

5.7.12.2 Confirm the Configuration Task Was Successful

To confirm this configuration task was successful, verify that the config/fusionapps_start_params.properties file exists under each local or non-admin split domain. Also ensure that the bin/setDomainEnv.sh file under each local or non-admin split domain contains the following row:

POST_CLASSPATH="${COMMON_COMPONENTS_HOME}/modules/oracle.appstrace_11.1.1/appstrace.jar${CLASSPATHSEP}${POST_CLASSPATH}"
export POST_CLASSPATH

5.7.12.3 Resolve Error Caused by WARs or EARs Not Accessible From The Primordial Host

The Propagating Domain Configuration configuration task fails if there are WARs or EARs installed or deployed that are not accessible from the primordial host where RUP Installer is running. An example of the error caused by this condition follows:

<< read domain from
APPTOP/instance/domains/server.company.com/SCMDomain
<< write template to
APPTOP/instance/fapatch/admin/ruplitedomain/11.1.5.0.0/output/templates/SCMDomain.jar
>>  fail: Unable to locate file:
/fusionapps/localdomain/domains/server.company.com/SCMDomain/datalens/datalens.war
>>  fail: write template to
"APPTOP/instance/fapatch/admin/ruplitedomain/11.1.5.0.0/output/templates/SCMDomain.jar"

CFGFWK-60550:  Script execution aborted. The script may contain an error.
Unable to locate file:
/fusionapps/localdomain/domains/server.company.com/SCMDomain/datalens/datalens.war

To resolve this issue, you must undeploy or uninstall the WAR or EAR, which is datalens.war in this example. Then restart RUP Installer. After the upgrade has completed successfully, you can install or deploy the WAR or EAR.

5.7.13 Troubleshooting Failure While Applying Downloaded Patches

If you do not download patches to the appropriate directory, the following type of error is reported:

Stack Description: java.lang.RuntimeException:
PatchObject constructor: Input file
"/net/server01/Downloaded_Patches/atgpf/patch/1234567/etc
/config/inventory" does not exist.

To resolve this issue, copy the patches to the correct directory and retry the failed configuration task.

5.7.14 Failure During Grant Privilege Scripts

If a failure occurs during either the Grant Privileges to Application Schemas or the Creating Grants/Synonyms on Application Database Objects configuration task, you can find the cause of the failure by running the script manually as the sysdba user, using SQL*Plus or SQL*Developer. After you resolve the issue, click Retry in RUP Installer.

5.7.15 Troubleshooting Loading Database Components

This section contains information about troubleshooting issues that may occur during the Loading Database Components configuration task. Depending on the type of failure, you may need to review one or more of the log files in the following locations:

FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/PatchManager_DBPatch/
- FAPatchManager_apply_timestamp.log
- adpatch_apply_timestamp.log
- adpatch_apply_timestamp_workernum.log
ATGPF_HOME/admin/FUSION/log

5.7.15.1 Error While Loading Database Components

When RUP Installer notifies you that one or more database workers failed during the Loading Database Components configuration task, you must start AD Controller to manage the failed workers. For more information, see Section 11.5, "Troubleshooting Patching Sessions for Database Content". After you resolve the issue that caused the workers to fail and you restart the failed worker, click OK in the dialog box and RUP Installer continues processing.

5.7.15.2 Database Failure While Loading Database Components

If your database goes down while RUP Installer is running the Loading Database Components configuration task, the options to Abort or Retry display. If you simply bring the database up and then click Retry, you may encounter the following error:

Failed to connect to the database as fusion with error: 
No more data to read from socket

Perform the following steps to recover from this error:

Force the database patching session to fail.

(Unix) FA_ORACLE_HOME/lcm/ad/bin/fapmgr.sh -forcefail 
(Windows) FA_ORACLE_HOME\lcm\ad\bin\fapmgr.cmd -forcefail

Start AD Controller.

(UNIX) FA_ORACLE_HOME/lcm/ad/bin/adctrl.sh
(Windows) FA_ORACLE_HOME\lcm\ad\bin\adctrl.cmd

For more information, see Section 11.5.1, "Starting AD Controller".

Perform the following sequence of steps in AD Controller to manage the workers:
1. Select Tell manager that a worker failed its job and enter All for all workers.
2. Select Tell worker to quit and enter All for all workers. Note that this does not kill the workers. It sends a command to the worker to shutdown after it completes the current task.
3. Wait for all workers to complete their tasks and shut down normally.
4. If there are still some worker processes that do not shut down, kill those processes manually by selecting Tell manager that a worker failed its job. Then select Tell manager that a worker acknowledges quit and enter All for all workers.
5. From your operating system, check for processes that are running fapmgr, javaworker, adpatch, adadmin, sqlplus, and adworker. If any exist, terminate them from your operating system.
6. Select Tell worker to restart a failed job and enter All for all workers.
Select Cancel to stop the session and then restart RUP Installer.

5.7.15.3 Failure During AutoPatch Validation

If AutoPatch validation fails, you receive this message:

An active adpatch or adadmin session was found. Complete or terminate the active session to allow fapmgr to proceed.

Follow these steps to resolve this error:

Run the fapmgr forcefail command to update the patching tables.

(UNIX) FA_ORACLE_HOME/lcm/ad/bin/fapmgr.sh forcefail [-logfile log file name] [-loglevel level]

(Windows) FA_ORACLE_HOME\lcm\ad\bin\fapmgr.cmd forcefail [-logfile log file name] [-loglevel level]

Run the fapmgr abort command from FA_ORACLE_HOME to find out if an Oracle Fusion Applications Patch Manager session must be cleaned up.

(UNIX) FA_ORACLE_HOME/lcm/ad/bin/fapmgr.sh abort [-logfile log file name] [-logLevel level]

(Windows) FA_ORACLE_HOME\lcm\ad\bin\fapmgr.cmd abort [-logfile log file name] [-logLevel level]

If this command finds no failed session, proceed to Step 3.

Run the following commands from ATGPF_ORACLE_HOME to abandon any Applications Core patching sessions or AD Administration sessions that may be running:

(Unix) ATGPF_ORACLE_HOME/lcm/ad/bin/adpatch.sh abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME/admin/TWO_TASK/defaults.txt

(Unix) ATGPF_ORACLE_HOME/lcm/ad/bin/adadmin.sh abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME/admin/TWO_TASK/defaults.txt

(Windows) ATGPF_ORACLE_HOME\lcm\ad\bin\adpatch.exe abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME\admin\TWO_TASK\defaults.txt

(Windows) ATGPF_ORACLE_HOME\lcm\ad\bin\adadmin.cmd abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME\admin\TWO_TASK\defaults.txt

5.7.15.4 Flexfield Seed Data Upload Fails

When multiple seed data files are uploaded for the same flexfield but for different flexfield contexts, the upload tasks can fail due to locking issues. The failed tasks appear in the log file as the following error:

Loading failed with a JboException: JBO-25014: Another user has changed the
row with primary keyoracle.jbo.Key ...

AutoPatch defers any failed tasks to the end of the phase and reattempts the failed tasks only after attempting all tasks in the phase at least once. Usually the flexfield seed data tasks that failed due to the locking issue succeed on subsequent attempts. You can ignore these errors if the flexfield seed data task succeeds on the retry. If the task remains in a failed state, you must use the AD Controller utility to retry the failed task.

For more information, see Section 11.5.4, "Restarting a Failed Worker".

5.7.16 Troubleshooting Deployment of Applications Policies

This section contains information about troubleshooting issues that may occur during the Deploying Application Policies configuration task. Log files for this task may be found in this location:

FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/fapatch_timestamp.log

5.7.16.1 Failure During Deploying Applications Policies

When a failure occurs during Deploying Application Policies, you must restore only the stripe or system policy that has failed, from your backup. Use the OPSS migrateSecurityStore command with the appropriate source and destination arguments to perform the restore. Do not restore a stripe that has not failed. Review the JAZN deployment log file, fapatch_Deploying_Applications_Policies_(jazn-data.xml)_timestamp.log, to determine the cause of the failure.

After you resolve the issue, restart RUP Installer by either selecting Retry in the same session or by exiting RUP Installer and restarting it.

For more information, see "Migrating with the Script migrateSecurityStore" in the Oracle Fusion Middleware Application Security Guide.

5.7.16.2 Warning During Deploying Applications Policies

If you see the following warning during Deploying Application Policies, you can safely ignore it as there is no functional impact of this warning and the deployment is successful.

WARNING: Failed to validate the xml content. cvc-complex-type.2.4.a: Invalid
content was found starting with element 'property'. One of
'{"http://xmlns.mycompany.com/oracleas/schema/11/jps-config-11_1.xsd":propertySetRef,
"http://xmlns.mycompany.com/oracleas/schema/11/jps-config-11_1.xsd":extendedProperty,
"http://xmlns.mycompany.com/oracleas/schema/11/jps-config-11_1.xsd":extendedPropertySetRef,
"http://xmlns.mycompany.com/oracleas/schema/11/jps-config-11_1.xsd":serviceInstanceRef}'
is expected. Location: line 165 column 96.
WLS ManagedService is not up running. Fall back to use system properties for
configuration.

5.7.16.3 Warning during Migrate Security Store

If you see the following warning during Deploying Application Policies, you can safely ignore it.

FINE: Application policies already exists for application: fscm
oracle.security.jps.service.policystore.PolicyObjectAlreadyExistsException:
Cannot create application policy context "fscm".
        at
oracle.security.jps.internal.policystore.ldap.LdapPolicyStore.unsync_createApp
licationPolicy(LdapPolicyStore.java:833)
        at
oracle.security.jps.internal.policystore.ldap.LdapPolicyStore.createApplicatio
nPolicy(LdapPolicyStore.java:753)
        at
oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstPolicy.c
lone(JpsDstPolicy.java:805)

5.7.16.4 IDM Server Failure During Deployment of Applications Policies

If the IDM Server goes down during Deploying Application Policies, the deployment fails. Even if the Retry button is enabled, RUP Installer does not allow a retry after this type of failure. You must instead click Cancel and restart RUP Installer.

5.7.17 Oracle BI Presentation Catalog Patch File Creation Failure

If you upgrade to a release that contains BI Publisher artifacts, the BI Presentation servers must not be running. The following error occurs if the BI Presentation servers are running during the deployment of BI Publisher artifacts:

java.lang.RuntimeException: Webcat patch file creation failed!

To resolve this issue, shut down the BI Presentation servers to release locks on the Oracle BI Presentation Catalog. For more information, see "fastartstop Syntax" in the Oracle Fusion Applications Administrator's Guide.

5.7.18 Updating BI Presentation Catalog to Resolve a Failure During Deploying BI Publisher Artifacts

Perform the steps in this section if you need to update the runtime instance BI Presentation Catalog to fix the cause of a failure during the Deploying BI Publisher Artifacts configuration task.

RUP Installer restores the backed up BI Presentation Catalog before you retry RUP Installer. The backup is stored in FA_ORACLE_HOME/admin/BIP/11.1.5.0.0/en_US/webcat.zip.

If you update the runtime instance BI Presentation Catalog only, this does not resolve the issue, because before you retry the failed step, RUP Installer will restore the previously backed up BI Presentation Catalog again. If you update the runtime BI Presentation Catalog directly, you must also update the backup BI Presentation Catalog. Perform the following steps if you plan to update the runtime BI Presentation Catalog:

Restore the runtime BI Presentation Catalog from the backed up version at FA_ORACLE_HOME/admin/BIP/11.1.5.0.0/en_US/webcat.zip.
Make your updates to the runtime BI Presentation Catalog.
Take a backup of FA_ORACLE_HOME/admin/BIP/11.1.5.0.0/en_US/webcat.zip.
Zip the runtime BI Presentation Catalog again, to FA_ORACLE_HOME/admin/BIP/11.1.5.0.0/en_US/webcat.zip
Click Retry to restart RUP Installer.

5.7.19 Troubleshooting Failure During Verifying Node Manager and OPMN Status

If the Verifying Node Manager and OPMN Status configuration task fails, do not cancel and exit out of RUP Installer in response to this task. Perform the following steps to recover:

Review the node manager log files to determine the cause of the failure:

APPLICATIONS_CONFIG/nodemanager/host_name/

Note that the APPLICATIONS_CONFIG value can be obtained from the APPLICATIONS_BASE/fusionapps/faInst.loc file.
After you resolve the issue that caused the failure, start the Node Manager on all hosts that are part of the Oracle Fusion Applications provisioned system. For more information, see "Task 3: Start Node Manager" in the Oracle Fusion Applications Administrator's Guide.
Restart the OPMN server for BI, GOP (if GOP is installed), and Web Tier. If you run the Web Tier (OHS) installed with the Oracle Fusion Applications middle tier, you can start it using the following steps. If you run the Web Tier on a separate machine, you may be able to run the steps below on the other machine. In either case, ensure that Web Tier (OHS) is up at this point.

Example for BI: (note the usage of start instead of startall)
```
(Unix)
cd APPLICATIONS_CONFIG/BIInstance/bin
./opmnctl start

(Windows)
cd APPLICATIONS_CONFIG\BIInstance\bin
opmnctl.bat start
```
Example for GOP: (note the usage of start instead of startall) Note that the OPMN server for GOP should be started from the machine that hosts the Supply Chain Management domain. Start the OPMN server for GOP only if you have GOP installed.
```
(Unix)
cd APPLICATIONS_CONFIG/gop_1/bin
./opmnctl start

(Windows)
cd APPLICATIONS_CONFIG\gop_1\bin
opmnctl.bat start
```
Example for Web Tier: (note the usage of start instead of startall)
```
(Unix)
cd APPLICATIONS_CONFIG/CommonDomain_webtier/bin
./opmnctl start

(Windows)
cd APPLICATIONS_CONFIG\CommonDomain_webtier\bin
opmnctl.bat start
```
For more information about the location of APPLICATIONS_BASE and APPLICATIONS_CONFIG, see Section 5.3.1, "Before You Begin".

The BI and Web Tier processes managed by OPMN are started by RUP Installer in the Starting All Servers configuration task. The GOP processes managed by OPMN must be started using Fusion Applications Control, as described in Section 5.6.8, "Start the GOP Processes", after RUP Installer completes.
Fix any other environment issues before retrying the session. If RUP Installer exits for any reason, make sure that all node managers and OPMN processes are running. Contact Oracle Support Services to proceed out of this step if you have unresolved environment issues.
After you start the services, click Retry to proceed to the Starting All Servers task. If the starting of servers times out, see Section 5.7.20, "Troubleshooting Server Start and Stop Failures".

Note:

If GOP is not installed, the user interface reports "Success" for GOP OPMN status, but the log file reports: GOP is not provisioned. Skipping check for OPMN status.

5.7.20 Troubleshooting Server Start and Stop Failures

This section includes the following troubleshooting topics:

General Server Failure Due to Time Out Errors
Failure to Start BIServer
Startup Failed for CommonDomain:OHSComponent (Oracle VM Only)

5.7.20.1 General Server Failure Due to Time Out Errors

Problem

A failure during the Starting All Servers configuration task typically happens when one of the servers times out and fails to start due to resource issues or application specific issues.

Solution

Various platforms and environment configurations can impact how long it will take all servers to actually start during the Starting All Servers configuration task. Although RUP Installer waits an average amount of time for this task to complete before it is marked as Failed, different platforms may require more time. It is not unusual to receive timeout errors in the log files if the starting of all servers for your environment requires more time than RUP Installer allows. If this task fails, follow these steps:

Monitor the status of the servers by reviewing the messages in the server log files or on the console. The log file, FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/StartStop/fastartstop_timestamp.log, indicates which server started and failed to start.

An example of messages for a server that timed out follows.

Time out while performing Start for domain SCMDomain. Waited for 2400 seconds
[2011-10-21T03:57:52.052--8:00] [fastartstop] [NOTIFICATION:1] [UTIL] [oracle.apps.startstop.util.MbeanUtil: runSSCommandOnDomain.868] [tid:37] Start operation is completed for domain SCMDomain. Please see SCMDomain.log for details.

[2011-10-21T03:57:52.052--8:00] [fastartstop] [NOTIFICATION:1] [UTIL] [oracle.apps.startstop.invoke.StartStopTask: call.221] [tid:37] StartStopTask over for domain SCMDomain

[2011-10-21T03:57:52.052--8:00] [fastartstop] [NOTIFICATION:1] [SST] [oracle.apps.startstop.invoke.StartStopTask: call.223] [tid:37] Finished the task for the Domain SCMDomain

Review the log files at the domain level to see a summary of the server status for that domain: FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/StartStop/domain name_timestamp.log.
Review the corresponding server logs for the failed servers under the following directory: APPLICATIONS_CONFIG/domains/hostname/domain name/servers/server name/logs.
After you determine and resolve the cause of the failure, return to RUP Installer and click Retry.
When all servers are up and running, including those that exceeded the timeout limit, click Abort in RUP Installer to move to the next configuration task.

5.7.20.2 Failure to Start BIServer

The following exception during the Starting all Servers configuration action indicates a failure in starting the BIServer:

Start all servers fails to start
Start operation on the component :coreapplication_obips1:, for the instance
:BIInstance: - FAILED

The coreapplication_obips1 server log file reports the following error:

ecid:]]
[2012-04-10T00:22:20.000-07:00] [OBIPS] [ERROR:16] []
[saw.security.odbcuserpopulationimpl.initialize] [ecid: ] [tid: ] Unable to
create a system user connection to BI Server during start up. Trying again.[[
File:odbcuserpoploaderimpl.cpp
Line:325
Location:
saw.security.odbcuserpopulationimpl.initialize
saw.catalog.local.loadCatalog
saw.subsystems.catalogbootstrapper.loadcatalog
saw.webextensionbase.init
saw.sawserver
ecid:]]
[2012-04-10T00:22:25.000-07:00] [OBIPS] [NOTIFICATION:1] [] [saw.sawserver]
[ecid: ] [tid: ] Oracle BI Presentation Services are shutting down.[[
File:sawserver.cpp
Line:706
Location:
saw.sawserver
ecid:

Perform the following steps to work around this issue:

Select Retry, which shuts down and starts bi_server1.
Monitor the fastartstop log files and the state of bi_server1(BIDomain).
As soon as bi_server1 restarts, as indicated by a RUNNING status, start the component coreapplication_obiccs1 or all the components of type OracleBIClusterControllerComponent using opmnctl.

Example syntax follows:
```
*/BIInstance/bin/opmnctl startproc ias-component=coreapplication_obiccs1
```

5.7.20.3 Startup Failed for CommonDomain:OHSComponent (Oracle VM Only)

Problem

The OHS diagnostic log contains the following error message:

No such file or directory:  Couldn't create accept lock

Solution

This issue could be the result of the hypervisors going down, resulting in bringing the Oracle VM servers down. Perform the following steps to resolve the error:

Find the entry for the lock file in httpd.config, for example:

LockFile "/u101/ohs_inst1/diagnostics/logs/OHS/ohs1/http_lock"

Confirm whether the directory that contains the lock file exists.
Assuming this directory does not exist, create the directory.

5.7.21 Failures During Online Preverification

This section provides information for troubleshooting the following errors during Online Preverification:

EditTimedOutException Error During Online Preverification
OAM Configuration Step Fails Due to Special Characters in Password

5.7.21.1 EditTimedOutException Error During Online Preverification

If you receive the following error during Online Preverification,

weblogic.management.mbeanservers.edit.EditTimedOutException

you may have to manually release the edit session. For more information, see Section 11.3.8, "Resolving an EditTimedOutException Error".

5.7.21.2 OAM Configuration Step Fails Due to Special Characters in Password

If the OAM administrator password contains special characters, such as '#' or '&', the OAM Configuration step will fail. To work around this issue, you can manually validate that the OAM Administration Server host/port and surname/password are correct. After you manually validate this information, you can proceed with the upgrade by clicking Continue.

Perform the following steps to validate.

Get the OAM administrator user name and password from the credential store.
Run APPLICATIONS_BASE/fusionapps/oracle_common/common/bin/wlst.sh.
Run the following commands to connect to the Common Domain Administration Server and get the OAM administrator surname and password:
```
connect()
listCred(map='oracle.patching', key='FUSION_APPS_PATCH_OAM_ADMIN-KEY')
```
Get the OAM Administration Server host and port from the following properties in APPLICATIONS_CONFIG/fapatch/FUSION_prov.properties:
- OAM_ADMIN_SERVER_HOST
- OAM_ADMIN_SERVER_PORT

Use oamcfgtool.jar to confirm whether the OAM server can be invoked using the values found in the previous steps.

cd APPLICATIONS_BASE/fusionapps/oracle_common/modules/oracle.oamprovider_11.1.1

java -jar oamcfgtool.jar app_domain=crm web_domain=OraFusionApp
uris_file=APPLICATIONS_BASE/fusionapps/applications/crm/security/oam.conf
oam_aaa_mode=open_or_simple app_agent_password=password_for_map="oracle.patching" 
key="FUSION_APPS_PATCH_OAM_RWG-KEY"_in_credential_store
primary_oam_servers=oam_server1 oam_admin_server=http://OAM_admin_server_host:port
oam_admin_username=username_for_FUSION_APPS_PATCH_OAM_ADMIN-KEY
oam_admin_password=password_for_FUSION_APPS_PATCH_OAM_ADMIN-KEY
oam_version=11 default_authn_scheme=FAAuthScheme

If the previous command is successful, the validation is successful. Click Continue.

5.7.22 Merging SOA Composite JDeveloper Customizations During RUP Installation

If you performed JDeveloper customizations to a SOA composite and you deployed the composite to the SOA runtime, RUP Installer reports an error during SOA Preverification, which instructs you to take the newer version of the composite that is in the release. You must then merge your customizations by performing the following steps.

If any customizations are detected, the SOA Preverification results display the SOA composite name, its location in the FA_ORACLE_HOME/stripe/deploy directory, and the requirement for you to merge JDeveloper customizations into the sca_*.jar file in FA_ORACLE_HOME before proceeding with RUP Installer. The stripe in the directory path refers to crm, hcm, fscm, and so on.
Open the custom SOA workspace and the customized version of the Fusion Applications SOA composite in JDeveloper using "Oracle Fusion Applications Developer". For more information, see "Customizing SOA Composite Applications with JDeveloper" in the Oracle Fusion Applications Extensibility Guide.
Import the composite sca_*.jar file from FA_ORACLE_HOME/stripe/deploy into the project, for example revision 11.1.5.0.0, in JDeveloper. Make note of this revision number in the deployment window because you will need it in Step 8.
Restart JDeveloper in the Oracle Fusion Applications Administrator Customization role.
Verify that there are no errors in JDeveloper.
Verify that the changes introduced in both the customized version and the patched version are present.
Right-click the composite project in the Application Navigator, select Deploy, select the composite, click Deploy to SAR, and click Next.
Manually change the value in New Revision ID to the revision from Step 3, for example, 11.1.5.0.0, and click Finish.
If the deployment folder is set to a location different from that of the FA_ORACLE_HOME/stripe/deploy directory, copy and replace the JAR in the location mentioned in the error message of this SOA Composite. If your file name is different, rename it to the original name. You must copy the jar in the correct format to FA_ORACLE_HOME/stripe/deploy. For example if you have sca_ContractsDeliverablePurchaseDocAttrReadComposite_rev11.1.5.0.0.jar in JDeveloper, then you must copy it back to the FA_ORACLE_HOME/stripe/deploy directory as sca_ContractsDeliverablePurchaseDocAttrReadComposite.jar.
To proceed with the installation, select Retry.

For more information about customizing SOA composites, see "Customizing and Extending SOA Components" in the Oracle Fusion Applications Extensibility Guide.

5.7.23 Location of GRC Policies in the OAM Applications Domain

The location of your Governance, Risk, and Compliance (GRC) policies varies, depending on your upgrade path to Release 5. GRC polices are located in the grc OAM application domain if your Oracle Fusion Applications environment was originally provisioned with either version 11.1.1.5 or 11.1.2, then upgraded to version 11.1.3, and then upgraded to version 11.1.4. If your environment was originally provisioned with version 11.1.3 and upgraded to version 11.1.4, your GRC policies are located in the fs OAM application domain.

5.7.24 Failure During IPM Import

If the configuration task for importing IPM artifacts fails with the following error, follow the instructions in Steps 1 through 7 in Section 4.12.1, "Prerequisites for the Deployment of IPM Artifacts".

importIPMApplication() & importIPMInput() WLST commands have not run successfully

Then return to RUP Installer and select Retry.

5.7.25 Troubleshooting SOA Composite Deployment Failures

This section describes how to recover from failures during the Deploying SOA Composites configuration task. The following topics are described:

SOA Composite Log Files
Composite Revision is Already Deployed
Cannot Set Default Composite
Manually Deploying SOA Composites

5.7.25.1 SOA Composite Log Files

The following log files are generated by the deployment of SOA composites:

Client side log files where individual domain logs reside: FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.5.0.0/soalogs
Log files for the failed domain:
- APPLICATIONS_CONFIG/domains/hostname/domain name/servers/server name/logs/soa_server1.log
- APPLICATIONS_CONFIG/domains/hostname/domain name/servers/server name/logs/soa_server1.out
- APPLICATIONS_CONFIG/domains/hostname/domain name/servers/server name/logs/soa_server1-diagnostic.log
- APPLICATIONS_CONFIG/domains/hostname/domain name/servers/server name/logs/AdminServer.log

5.7.25.2 Composite Revision is Already Deployed

Normally, a failed SOA composite is undeployed by RUP Installer. However, if the failure of the deployment is due to SOA servers running out of memory, then RUP Installer cannot recover. As a result, a failure message such as CFGEX-00062: Composite revision "default/composite name!11.1.5.0.0" is already deployed may occur.

An example of a complete error message follows:

[2011-12-30T04:24:38.613-08:00] [apps]
[ERROR] [] [oracle.apps.CRMDomain] [tid: 58]
[ecid: 0000JIEvTHGEGR9ZvdYBV11EzMvF00000c,0]
CFGEX-00073 : SOA composite "/u01/APP_TOP/fusionapps/applications/crm/deploy/sca_ContractsTermLibTemplatesComposite.jar"
deployment failed for Domain "CRMDomain".[[
Action : See logs for details. oracle.as.install.
fapatchconfig.exception.PatchsetConfigException:
CFGEX-00073 : SOA composite "/u01/APP_TOP/fusionapps/applications/
crm/deploy/sca_ContractsTermLibTemplatesComposite.jar" deployment failed for Domain "CRMDomain".
      ….
Caused by: oracle.as.install.fapatchconfig.exception.PatchsetConfigException: CFGEX-00062 : Composite revision "default/
ContractsTermLibTemplatesComposite!11.1.5.0.0" is already deployed.

To resolve this issue, you must manually undeploy the composite.

Note:

Ensure that you undeploy only the revision deployed by RUP Installer. Do not undeploy the previous version.

To undeploy, you can use WebLogic Server Tool (WLST) commands or Fusion Applications Control. For more information see Section 5.7.25.2.1, "Undeploy SOA Composites Using WLST Commands" and Section 5.7.25.2.2, "Undeploy SOA Composites Using Fusion Applications Control".

Then return to RUP Installer and select Retry.

5.7.25.2.1 Undeploy SOA Composites Using WLST Commands

Follow these steps to undeploy the composite using WLST commands:

Start WLST:

(Unix) APPLICATIONS_BASE/soa/common/bin/wlst.sh
(Windows) APPLICATIONS_BASE\soa\common\bin\wlst.cmd

Run the sca_undeployComposite command using the following syntax:
```
sca_undeployComposite(serverURL, compositeName,
revision, [user], [password], [partition])
```
The variables have the following values:
- serverURL contains the host and port of the SOA cluster Managed Server of the domain on which the SOA composite failed to deploy
- compositeName is the name of the composite to be undeployed
- revision, in the case of the Release 5, this should be 11.1.5.0.0 by default.
Example:
```
wls:/mydomain/ServerConfig>  sca_undeployComposite
("http://myhost10:7001",
" ContractsDeliverablePurchaseAgrmntFlowComposite ", "11.1.5.0.0")
```
You are prompted for the user name and password to execute the command.

For more information, see "Oracle SOA Suite Custom WLST Commands" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

5.7.25.2.2 Undeploy SOA Composites Using Fusion Applications Control

Follow these steps to undeploy the composite using Fusion Applications Control:

In Fusion Applications Control, connect to the domain where the SOA composite failed to deploy. For more information, see "Starting Fusion Applications Control" in the Oracle Fusion Applications Administrator's Guide.
Navigate to Farm_Domain->soa-infra->default.
Locate the composite and revision, such as 11.1.5.0.0, as shown in this example:
```
ContractsDeliverablePurchaseAgrmntFlowComposite [11.1.5.0.0]
```
Right click on the composite and select SOA deployment > Undeploy.

5.7.25.3 Cannot Set Default Composite

You may receive the following error during deployment of a SOA composite. For this example, the HcmEmploymentProcessesChngWkHrsComposite composite is shown:

Step FIND_BASE_COMPOSITE:Find the base composite for patch. It will be
current default composite of the series
  ==> failed: Error in getting default
composite:default/HcmEmploymentProcessesChngWkHrsComposite, The configuration
file, deployed-composites.xml, does not contain the
default/HcmEmploymentProcessesChngWkHrsComposite composite-series element.

To resolve this issue, manually deploy the missing composite by executing the following commands on a Windows platform:

SET JAVA_HOME=REPOSITORY_LOCATION\jdk6
REPOSITORY_LOCATION\provisioning\ant\bin\ant -f
APPLICATIONS_BASE/fusionapps/soa/bin/ant-sca-deploy.xml -DsarLocation
APPLICATIONS_BASE/fusionapps/applications\hcm/deploy\sca_HcmEmploymentProcessesChngWkHrsComposite.jar
-DserverURL http://my_host:9420 -Duser
FUSION_APPS_PROV_PATCH_APPID -Dstdinpassword true -Doverwrite true
-DfailOnError true deploy

5.7.25.4 Manually Deploying SOA Composites

If a customized SOA composite deployment fails during patching, you must manually deploy this composite using WLST commands. You must also manually deploy SOA composites if you apply a patch in offline mode that contains SOA composites.

To apply a SOA composite manually after a deployment failure or when patching in offline mode

In the following steps, the example composite, FinAp, is patched from revision 1.0 to revision 2.0 and the SAR file of revision 2.0 is in FA_ORACLE_HOME/crm/deploy/sca_FinAp_rev2.0.jar.

Note that the parameters are for illustration purposes only.

Refer to the Diagnostics report to find the name and location of the sca_*.jar file that was copied to FA_ORACLE_HOME by Oracle Fusion Applications Patch Manager. For more information, see Section 3.5.5, "Diagnostics Report".
If the previous revision contained JDeveloper customizations, ensure that you deploy the patched revision with the merged JDeveloper customizations. Using the sca_*.jar file from Step 1, follow the JDeveloper customization merge instructions that are described in Section 5.7.22, "Merging SOA Composite JDeveloper Customizations During RUP Installation". Then use the merged sca_*.jar for Step 3.

Deploy the patched composite using the single patch composite command.

sca_patchComposite('SOA-Infra URL', user, password, 
'/FA_ORACLE_HOME/crm/deploy//sca_FinAprev2.0.jar', mergeLogFile='/tmp/merge-log.txt')

5.7.26 Troubleshooting Health Checker

Health Checker generates a log file in FA_ORACLE_HOME/admin/FUSION/log/healthchecker/healthcheckplugin _timestamp.log. Log archives are stored in the FA_ORACLE_HOME/admin/FUSION/log/healthchecker/ARCHIVE directory.

After you resolve the issue that caused the failure, you can restart Health Checker by using the -recover command line option.

5.7.27 AttachHome Script Hangs

If the attachHome script hangs, when following the steps in Section 5.3.12, "Confirm All Oracle Homes Are Registered in the Central Inventory", run attachHome with the following additional arguments: -waitforcompletion -nowait.

5.7.28 The runInstaller.sh -updateHomeDeps Command Hangs

If the runInstaller -updateHomeDeps command hangs, when following the steps in Section 5.3.12, "Confirm All Oracle Homes Are Registered in the Central Inventory", run this command with the following additional arguments: -waitforcompletion -nowait.

5.7.29 Perform Installation Verification Steps

Perform the steps in "Verifying Installation" in the Oracle Fusion Applications Post-Installation Guide.