| Oracle® Fusion Applications Upgrade Guide 11g Release 6 (11.1.6) Part Number E35833-07 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Upgrade Guide 11g Release 6 (11.1.6) Part Number E35833-07 |
|
|
PDF · Mobi · ePub |
This chapter describes the steps required to upgrade Oracle Fusion Applications to Release 6 (11.1.6).
This chapter contains the following topics:
RUP Installer must run during down time. 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 2.1.1, "Before You Begin".
Ensure that the steps in Section 2.1, "Pre-Upgrade Steps - Before Down Time" and Section 2.2, "Pre-Upgrade Steps - During Down Time" are successfully completed.
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.
Perform the following steps to start RUP Installer 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 encounters errors, refer to Chapter 6, " Troubleshooting the Upgrade" 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:
(Unix only) $REPOSITORY_LOCATION/installers/farup/Disk1/runInstaller -jreLoc APPLICATIONS_BASE/fusionapps/jdk6/ -invPtrLoc /net/APPLICATIONS_BASE/fusionapps/applications/oraInst.loc
If not triggered with a /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 6.2.4, "Inventory Pointer File is Empty".
Start RUP Installer.
(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][-J-Dapplseed_validation=full][-debug] (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] [-Dapplseed_validation=full] [-debug]
Table 3-1 shows valid options that can be used when running RUP Installer.
Table 3-1 RUP Installer command options
| Option Name | Description | Mandatory |
|---|---|---|
|
|
Path where the Java Runtime Environment is installed. This option does not support relative paths, so you must specify the absolute path. |
Yes. |
|
|
The location of an overriding inventory pointer file. If Oracle Fusion Applications Oracle home directory ( |
Recommended, use to override the default location of the inventory pointer file, located in |
|
(- |
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. |
|
(- |
Records messages in the log file at the level you specify. Enter a value to override the default log level of |
No, default value is |
|
|
Configures the timeout value for server in seconds. |
No, overrides the default value for server timeout. |
|
( |
The directory path where you downloaded mandatory prerequisite patches to be applied by RUP Installer. See Section 2.1.4, "Download Mandatory Post-Release 6 Patches". |
Yes, if you downloaded mandatory patches. Provide the full directory path to the |
|
( |
Enables full validations, so that all validations are triggered during seed data upload. |
No, default value is partial. |
|
|
Retrieves the debug information from RUP Installer. |
No. |
Table 3-2 and Table 3-3 illustrate the tasks that RUP Installer runs. For information about the user interface, see Section 1.4, "Installer User Interface". For information about troubleshooting RUP Installer errors, see Chapter 6, " Troubleshooting the Upgrade". For information about log files, see Section 6.1, "RUP Installer Log File Directories".
Table 3-2 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 ( Click Next to continue. |
|
Installation Summary |
Summarizes the configuration that will be used 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 assistants that 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 configuration assistant, including steps within configuration assistants, in the message pane as they are performed. Configuration assistants that could be included in the first installer's configuration phase are described in Table 1-1, "Configuration Assistants Run by Oracle Fusion Applications 11g Release 6 (11.1.6) RUP Installer Part 1 of 2". No additional user action is required in the Configuration Progress screen unless a failure occurs. For more information, see Section 6.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 assistants completed successfully. If you want to rerun this session to resolve failed configuration assistants, click Cancel. |
|
Run RUP Lite for Domain Configuration |
You must run RUP Lite for Domain Configuration on all servers that contain local domains 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. 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.
Click OK to proceed to the second installer. |
Table 3-3 RUP Installer Screen Sequence for the Second Installer
| Screen | Description and Action Required |
|---|---|
|
Welcome |
Appears when the second installer starts. You must perform the following steps to start the Node Manager and OPMN server before proceeding to the next screen.
The BI and Web Tier processes managed by OPMN are started by RUP Installer during the Starting All Servers configuration assistant. The GOP processes managed by OPMN must be started using Fusion Applications Control after RUP Installer completes, as described in Section 4.8, "Start GOP Processes". Click Next to continue. |
|
Installation Location |
Specify the location of the existing Oracle Fusion Applications home ( Click Next to continue. |
|
Installation Summary |
Summarizes the configuration that will be used 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 phase consists of copying files that are related to configuration assistants run during the second installer to the appropriate Oracle homes. 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, this screen does not display.) |
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 by RUP Installer 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:
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 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:
When you complete this task in APM, shut down the APM application, return to RUP Installer, and click Next. |
|
Configuration Progress |
The second installer supports parallel processing of certain configuration assistants, which run in groups. For more information, see Section 1.4.7, "Parallel Configuration Assistants". This screen displays a progress indicator that shows the percentage of the configuration phase that is complete. It displays each configuration assistant, including steps within configuration assistants, in the message pane as they are performed. Configuration assistants that could be included in the second installer's configuration phase are described in Table 1-2, "Configuration Assistants Run by Oracle Fusion Applications 11g Release 6 (11.1.6) RUP Installer Part 2 of 2". Before the Starting All Servers configuration assistant, the Verifying Node Manager and OPMN Status configuration assistant 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 configuration assistant. For more information, see Section 6.17, "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 6.4, "General Troubleshooting During the Configuration Phase in GUI Mode". Links to specific configuration assistant failures are available in Table 1-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 assistants completed successfully. If you want to rerun this session to resolve failed configuration assistants, click Cancel. |
Proceed to Section 3.2, "Run the Post RUP Installer Report".
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 6.2.4, "Inventory Pointer File is Empty".
Run the following command to start the first installer in silent mode:
Note:
If RUP Installer encounter errors in silent mode during the first installer, it terminates the session. You must resolve the issue that caused the failure and then restart RUP Installer, using the same command you used previously. RUP Installer then restarts from the first failed task. For more information, see Section 6.5, "General Troubleshooting During the Configuration Phase in Silent Mode".
(UNIX) $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 [-J-Dworkers=number_of_workers][-J-DlogLevel=level] [-J-DserverStartTimeout=timeout_period_for_server_in_seconds] [-J-DpatchDownloadLocation=patch_directory][-waitForCompletion yes] [-J-Dapplseed_validation=full][-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 [-DserverStartTimeout=timeout_period_for_server_in_seconds] [-DpatchDownloadLocation=patch_directory [-waitForCompletion yes] [-Dapplseed_validation=full] [-debug]
Table 3-2 shows valid options that can be used when running RUP Installer in silent mode.
Table 3-4 RUP Installer command options in silent mode
| Option Name | Description | Mandatory |
|---|---|---|
|
|
Path where the Java Runtime Environment is installed. This option does not support relative paths, so you must specify the absolute path. |
Yes. |
|
|
The location of an overriding inventory pointer file. If Oracle Fusion Applications Oracle home directory ( |
Recommended, use to override the default location of the inventory pointer file, located in |
|
|
Run RUP Installer in silent mode. |
Yes. |
|
|
The location of the response file, |
Yes. |
|
|
Required for the Deploying Applications Policies configuration task. |
Yes, always set to true for silent mode. |
|
(- |
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. |
|
(- |
Records messages in the log file at the level you specify. Enter a value to override the default log level of |
No, default value is |
|
|
Configures the timeout value for server in seconds. |
No, overrides the default value for server timeout. |
|
|
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. |
|
( |
The directory path where you downloaded mandatory prerequisite patches to be applied by RUP Installer. See Section 2.1.4, "Download Mandatory Post-Release 6 Patches". |
Yes, if you downloaded mandatory patches. Provide the full directory path to the |
|
( |
Enables full validations, so that all validations are triggered during seed data upload. |
No, default value is partial. |
|
|
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:
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.
Perform the following steps to start the Node Manager and the OPMN server for BI, GOP, and Web Tier.
To ensure that Node Manager does not automatically start servers, even if crashRecovery is enabled, remove all files that end with .pid, .state, and .lck from domain_home/servers/server_name.
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 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)
cd APPLICATIONS_CONFIG/BIInstance/bin
./opmnctl 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 Advanced Planning Managed server. Start the OPMN server for GOP only if you have GOP installed.
cd APPLICATIONS_CONFIG/gop_1/bin
./opmnctl start
Example for Web Tier: (note the usage of start instead of startall)
cd APPLICATIONS_CONFIG/CommonDomain_webtier/bin
./opmnctl start
For more information about the location of APPLICATIONS_CONFIG, see Section 2.1.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 4.8, "Start GOP Processes".
Run the following command to start the second installer in silent mode:
Note:
If RUP Installer encounter errors in silent mode during the second installer, it cancels the session. You must resolve the issue that caused the failure and then restart RUP Installer, using the same command you used to start the second installer. RUP Installer then restarts from the first failed task. For more information, see Section 6.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 [-J-Dworkers=number_of_workers][-J-DlogLevel=level] [-J-DserverStartTimeout=timeout_period_for_server_in_seconds] [-J-DpatchDownloadLocation=patch_directory][-waitForCompletion yes] [-J-Dapplseed_validation=full][-debug] (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 [-DserverStartTimeout=timeout_period_for_server_in_seconds] [-DpatchDownloadLocation=patch_directory][-waitForCompletion yes] [-Dapplseed_validation=full] [-debug]
Proceed to Section 3.2, "Run the Post RUP Installer Report".
Run the Post RUP Installer report to check for any errors or warnings that require attention and to confirm whether RUP Installer completed successfully. The Post RUP Installer report provides an overview of the configuration assistants that RUP Installer ran during the upgrade. It is generated in HTML and XML format and includes links to log files. The names of the report files are PostRUPInstallerReport.html and PostRUPInstallerReport.xml. The log file generated by this report is PostRUPInstallerReport.log. The report output and log files are located in the directory that you provide when you run the report.
The Post RUP Installer report displays the following information:
Configuration Assistant: The name of the configuration assistant.
Attempts: The number of times the configuration assistant ran.
Time Taken: The duration of the configuration assistant in minutes and seconds.
Result: The result of the configuration assistant, such as PASSED or FAILED.
Errors: Any errors that were reported during the configuration assistant.
Log Files: Link to log files for the configuration assistant.
Run the following command to generate the Post RUP Installer report:
(Unix) FA_ORACLE_HOME/lcm/ad/bin/generatepostrupinstallationreport.sh -loglocation log_location [-reportlocation report_location -outputloglocation outputlog_location] (Windows) FA_ORACLE_HOME\lcm\ad\bin\generatepostrupinstallationreport.cmd -loglocation log_location [ -reportlocation report_location -outputloglocation outputlog_location]
Table 3-5 describes the command line options for the Post RUP Installer report.
Table 3-5 Command Line Options for the Post RUP Installer Report
| Option Name | Mandatory | Description |
|---|---|---|
|
-loglocation |
Yes |
The location of the RUP Installer log files, for example, |
|
-reportlocation |
No |
The location of the Post RUP Installer report in HTML and XML format. The file names are |
|
-outputloglocation |
No |
The location of the Post RUP Installer report log file, named |
The directory paths you provide for the -loglocation, -reportlocation, and -outputloglocation options must be existing directories.
To complete the upgrade, proceed to Chapter 4, "Completing Post-Upgrade Tasks".
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|