| Oracle® Fusion Applications Patching Guide 11g Release 5 (11.1.5) Part Number E16602-21 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Patching Guide 11g Release 5 (11.1.5) Part Number E16602-21 |
|
|
PDF · Mobi · ePub |
This chapter describes how to install and maintain a set of languages in Oracle Fusion Applications 11g Release 5.
This chapter contains the following topics:
Oracle Provisioning and RUP Installer install and upgrade only the English language. To add a language or upgrade an existing language, use Language Pack Installer. If patches containing translatable artifacts were previously applied to this environment, you may apply the translated versions of each of those patches after you install the new language.
This section provides an introduction to the following concepts related to language packs:
A language pack for a given language and release contains artifacts at the specific release level that are translated to the specific language. Translated artifacts include Oracle Fusion Applications seed data that is uploaded into Oracle Fusion Applications database, SOA resource bundles, JEE resource bundles, LDAP data, Diagnostics Test Framework, and BI Presentation Catalog data. You install language packs with Language Pack Installer.
Language Pack Installer enables you to add or upgrade a language in your Oracle Fusion Applications environment and delivers translated artifacts for that language. You can run Language Pack Installer in GUI mode, and proceed through the installation by providing information in the user interface when prompted. For more information, see Section 5.1.2, "RUP Installer User Interface", which is the same as the Language Pack Installer interface. You can also run Language Pack Installer in silent mode, in which progress is reported to the console.
The policy store can maintain attributes in only one language. If you want to override the base English strings in the policy store, you set the -J-DupdateJAZNPolicyStore option (-DupdateJAZNPolicyStore for Windows) to true when you install the Language Pack. The Description and Displayname are the two attributes which are translatable and are loaded in JAZN files in the Language Pack.
During the installation phase, Language Pack Installer copies all of the files from the language pack to the appropriate locations, such as Oracle Fusion Middleware home and Oracle Fusion Applications Oracle home. After the file copy is completed, Language Pack Installer starts the Policy Store Analysis, as described in Table 6-5, "Language Pack Installation Screen Sequence". Then Language Pack Installer calls Configuration Assistants to perform the remaining tasks required to update and deploy the artifacts included in the language pack.
If any tasks fail during the installation phase, refer to Section 6.7.2, "Troubleshooting Failures During the Installation Phase" for more information.
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".
Table 6-1 provides a list of possible configuration tasks, including steps within the tasks. The Retry Behavior column describes what Language Pack Installer does after a configuration task fails and you restart Language Pack Installer after you resolve the cause of the failure. If available, links are provided to relevant troubleshooting sections.
Table 6-1 Configuration Tasks Run by Language Pack Installer
| Name | Mandatory | Description | Retry Behavior |
|---|---|---|---|
|
Activate Language |
Yes |
Activates the language in the database. |
Runs Activate Language again. |
|
Preverification |
Yes |
Performs the following validation checks:
|
Runs failed steps. |
|
Synchronize Multilingual Tables |
Yes |
Runs the Maintain Multilingual Tables utility to maintain the tables related to the language being installed. For more information, see Section 10.3.4, "Maintaining Multi-lingual Tables". |
Restart from failure. |
|
Apply Middleware Language Patches |
Yes |
|
Applies the failed patches. See Section 5.7.9, "Troubleshooting Applying Middleware Patches". |
|
Load Database Components |
Yes |
Uploads the database content packaged in the language pack to the database. |
Runs failed database commands. See Section 5.7.15, "Troubleshooting Loading Database Components". |
|
Deploy Applications Policies (jazn-data.xml) |
Yes |
Performs the deployment of the updated applications policies, based on your selections during the Policy Store Analysis task. This task runs only if you installed a Language Pack and chose to override the base English strings in the policy store by using the |
Deploys the failed stripes. See Section 5.7.16, "Troubleshooting Deployment of Applications Policies". |
|
Stop BI Presentation Server |
Yes |
Stops the BI Presentation server. |
Retries stopping the BI Presentation server. |
|
Deploy BI Publisher Artifacts |
Yes |
Using Catalog Manager:
|
Starts from the beginning of the task. See Section 5.7.17, "Oracle BI Presentation Catalog Patch File Creation Failure". |
|
Deploy Flexfields |
No |
Deploys flexfields to the domain that hosts the |
Starts from the beginning of the task. |
|
Deploy LDAP Data (LDIF) |
No |
Uploads LDIF XLIFF translations to the identity store. |
Retries failed XLIFF files. |
|
Deploy SOA Resource Bundles |
Yes |
Deploys SOA Resource Bundles to the corresponding SOA servers. |
Deploys failed SOA resource bundles. |
|
Apply Downloaded Language Patches |
Yes |
Applies post installation patches that you downloaded in the |
Applies failed patches. |
This section describes changes that were made to manual steps in Release 5.
Section 6.3.1, "Before You Begin" was added.
Post repository NLS patches can be applied by Language Pack Installer as long as you download and stage patches prior to the upgrade as described in Section 6.3.3, "Download Mandatory Post-Installation NLS Patches".
Section 6.3.4, "Confirm Oracle Fusion Applications Installation is Complete" was added.
The manual step titled "Confirm All Oracle Homes Are Registered in the Central Inventory" is no longer required.
Language Pack Installer no longer requires a server shutdown prior to starting the installation. Although servers are up, Language Pack Installer expects users to be offline and no transactions can be performed, as mentioned in Section 6.4, "Prepare to Install a Language Pack - During Down Time".
Section 6.6.3, "Bounce All Servers and Verify the Status of Deployed Applications" was added.
Section 6.6.4, "Reload Custom Templates for BI Publisher Reports" was added.
This section describes the following preparation steps for installing a language pack, all of which can be performed before your scheduled down time.
Before you begin the language pack installation, you should have access to the following documentation:
Oracle Fusion Applications release notes from the current release.
Oracle Fusion Applications NLS release notes from the current release.
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
For more information, see Figure 5-1 which shows the relationship of the home directories using the Oracle Fusion Financials product family on a UNIX environment as an example.
The language pack repository contains the language pack installer, translated Oracle Fusion Middleware patches, and the Oracle Fusion Applications language pack contents that are required to install a language pack for a specific language 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.
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 language pack repository.
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 language pack 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.
Table 6-2 list the installers in the language pack repository.
Table 6-2 Language Pack Installers
| Media Label Name | Staging Destination |
|---|---|
|
Language Pack Installer |
or |
Note:
If there are no post-installation patches in Oracle Fusion Applications NLS release notes when you run Language Pack Installer, no action is required for this step.
Language Pack 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 NLS release notes and that are specifically required for the language pack that you are installing.
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.
If you are installing a language pack after an upgrade, you already downloaded this patch and created the directories described in Steps 2 and 3, while following the steps in Section 5.3.6, "Download Mandatory Post Release 5 Patches".
Review the postRepoPatchDirsREADME.txt file to confirm the location for the post_repo_patches directory. If this directory does not exist, create it 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. If you are installing a language pack after an upgrade, you created this directory structure in Section 5.3.6, "Download Mandatory Post Release 5 Patches". Oracle recommends you use this exact directory name and location.
Note:
If you choose to download the patches to a different directory, you must use the -J-DpatchDownloadLocation option when you start Language Pack Installer. See Section 6.5.1, "Run Language Pack Installer in GUI 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 Oracle Fusion Applications NLS release notes to find the patches to be downloaded from My Oracle Support.
Table 6-3 describes the types of patches that you download and which configuration task applies the patches.
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 2. 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 5.
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 4, 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
If you are installing a language pack on a freshly installed Oracle Fusion Applications environment, ensure that you have performed all tasks described in "Postinstallation Tasks" in the Oracle Fusion Applications Installation Guide.
If you are installing a language pack on an upgraded environment, ensure that you have followed all tasks described in Section 5.6, "Complete the Post Upgrade Tasks".
In either case, you must also perform the steps in the "Post-Installation" section of Oracle Fusion Applications release notes.
Confirm that memory requirements are met on the primordial host that the Language Pack installer is launched from. The primordial host is where the Administration Server for the Common Domain runs.
Running Language Pack installer is an administrative activity that requires all of the Administration Servers for the provisioned Oracle Fusion Applications domains to be up during the Language Pack installation. Language Pack Installer requires at least 6GB of free RAM on the 64-bit domains to be up during the installation. Language Pack Installer also requires at least 6GB of free RAM on the 64-bit primordial host that the installer is launched from, for the duration of the Language Pack installation. This 6GB of free memory requirement 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 Language Pack installation as a safety net.
For example, if the BI domain is provisioned on the primordial host, then Language Pack 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 Language Pack Installer, which requires a connection to the Administration Server that is running. If you run Language Pack Installer and the Administration Server on the same primordial host with insufficient memory, then the Administration Server and Managed Servers may fail.
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 platform, 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.
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. The steps to check and modify local port range settings vary by platform. Follow the steps for your platform:
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
Follow these 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.
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
Review the following steps to confirm that your database settings are optimized for the language pack installation.
Refer to Oracle Fusion Applications release notes to verify that your database and Sql*Net tuning parameters are set properly to avoid timeout errors during the installation.
Confirm that the open file limit is set properly.
Language Pack 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 the Language Pack Installer. To understand how the number of the workers are calculated and the open file limit setting that is required 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.
Ensure that you have your own versions of any customized BI Publisher reports. If a language pack includes an update to a catalog object that was delivered with an Oracle Fusion application, the patch 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.
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/LP_Repo/ (Windows) SET APPLICATIONS_BASE=\server01\APPTOP\ SET REPOSITORY_LOCATION=\server01\LP_Repo\
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.
Health Checker for DBMS Stats confirms that 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.
For more information, see "Collecting Optimizer Statistics" in the Oracle Fusion Applications Administrator's Guide. This step optimizes the performance of starting servers.
Then follow the steps in "Configuring Oracle Metadata Services" in the "Common" chapter of the Oracle Fusion Applications Post-Installation Guide.
Note:
For 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.
This section describes the following mandatory preparation steps for installing a language pack, all of which must be performed during your system down time. As of Release 5, Language Pack Installer does not require any servers to be shut down. However, no users should be online, so it is still considered to be down time.
This section contains steps to follow for all platforms.
Confirm that all servers are up and running before installing the language pack.
Confirm that the OPMN control process and Node Manager are running. If they are not running, follow Step 4 in Section 5.5.1, "Run RUP Installer in GUI Mode" to start them.
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 about starting, see "Starting and Stopping Oracle Internet Directory" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition).
Confirm that there are no active jobs or processes running against the database. If there are, stop all background jobs, including jobs in the database and active processes. 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;
From your operating system, check for processes that are running fapmgr, javaworker, adpatch, adadmin, and adworker. If a 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]
If the forcefail command returns "There are no active Oracle Fusion Applications Patch Manager sessions which can be forcibly failed", then skip the next step.
Use the fapmgr abort command to abandon the session, only if a session is active.
(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 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=log_file_name (Windows) lcm\ad\bin\adpatch.exe abandon=y interactive=n defaultsfile=ATGPF_ORACLE_HOME\admin\LOCAL\defaults.txt logfile=log_file_name
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.
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.
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".
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.
Download and apply any prerequisite patches listed in the Post-Installation and Post-Upgrade sections of Oracle Fusion Applications release notes prior to starting Language Pack Installer. Note that the only patches that need to be applied are those that have been added to Oracle Fusion Applications release notes since the last time you applied patches from this list.
As of Release 5, Language Pack Installer does not require any servers to be shut down. However, no users should be online, so it is still considered to be down time. Oracle recommends that language packs be installed from a machine that is co-located in the same subnetwork as the database server to maximize performance. You must run Language Pack Installer on the primordial host.
Ensure that the steps in Section 6.3, "Prepare to Install a Language Pack - Before Down Time" and Section 6.4, "Prepare to Install a Language Pack - During Down Time" are successfully completed before you start Language Pack Installer.
Language Pack 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, Language Pack Installer reports the progress of the upgrade as console output.
Perform the following steps to run Language Pack Installer in GUI mode from the command line, using specific options to further define the necessary actions. You must run Language Pack Installer from the primordial host. Table 6-4 shows valid options that can be used when running Language Pack Installer.
Note:
If Language Pack Installer encounter errors, refer to Section 6.7, "Troubleshoot Language Pack Installer Sessions" before clicking any buttons in the Language Pack 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 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 Language Pack Installer. An example follows:
(Unix only) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -jreLoc APPLICATIONS_BASE/fusionapps/jdk6/ -invPtrLoc /net/APPLICATIONS_BASE/fusionapps/applications/oraInst.loc
If not triggered with /net path, Language Pack Installer copies the -invPtrLoc file to FA_ORACLE_HOME. 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.7.2.3, "Inventory Pointer File is Empty".
Run the following command to start Language Pack Installer in GUI mode.
(UNIX) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6 [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] [-J-DupdateJAZNPolicyStore=true] [-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] (Windows) %REPOSITORY_LOCATION%\installers\fusionapps\Disk1\setup.exe -addLangs -jreLoc APPLICATIONS_BASE\fusionapps\jdk6 [-DupdateJAZNPolicyStore=true] [-Dworkers=number_of_workers][-DlogLevel=level] [-DserverStartTimeout=timeout_period_for_server_in_seconds] [-DpatchDownloadLocation=patch_directory][-logfile log_file_name][-debug]
Table 6-4 shows valid options that can be used when running Language Pack Installer in GUI mode.
Table 6-4 Language Pack Installer Command Line Options in GUI Mode
| Option Name | Description | Mandatory |
|---|---|---|
|
|
Runs Language Pack Installer to install one language. |
Yes |
|
|
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 |
|
( |
Updates the policy store with translated attributes so field descriptions, display names, and other attributes display their translated values. |
No, use only when you do not want to use base English. |
|
( |
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 Language Pack Installer. See "Worker Calculation" in Section 3.1.2, "Patching Database Artifacts". |
|
|
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 Language Pack Installer. See Section 6.3.3, "Download Mandatory Post-Installation NLS Patches". |
No, the default is |
|
( |
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 |
|
|
Retrieve debug information from Language Pack Installer. |
No |
Example 6-1 Language Pack Installation with no policy store translation
(Unix) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6 -invPtrLoc FA_ORACLE_HOME/oraInst.loc (Windows) %REPOSITORY_LOCATION%\installers\fusionapps\Disk1\setup.exe -addLangs -jreLoc APPLICATIONS_BASE\fusionapps\jdk6
Example 6-2 Language Pack installation with policy store translation
(Unix) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6 -invPtrLoc FA_ORACLE_HOME/oraInst.loc -J-DupdateJAZNPolicyStore=true (Windows) %REPOSITORY_LOCATION%\installers\fusionapps\Disk1\setup.exe -addLangs -jreLoc APPLICATIONS_BASE\fusionapps\jdk6 -DupdateJAZNPolicyStore=true
Example 6-3 Language Pack installation when FA_ORACLE_HOME is registered with a /net path
(Unix) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc APPLICATIONS_BASE/fusionapps/jdk6 -invPtrLoc /net/APPLICATIONS_BASE/fusionapps/applications/oraInst.loc
Table 6-5 illustrates the tasks that Language Pack Installer runs. For information about troubleshooting Language Pack Installer errors, see Section 6.7, "Troubleshoot Language Pack Installer Sessions". For information about log files generated during language pack installation, see Section 6.7.1, "Language Pack Installer Log File Directories".
Table 6-5 Language Pack Installation Screen Sequence
| Screen | Description and Action Required |
|---|---|
|
Welcome |
Appears when you start Language Pack Installer. This screen does not appear if you restart Language Pack Installer after a failure. The standard Welcome screen is read-only. It contains a navigation pane on the left-hand side that summarizes the tasks 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 selections you made during this installation session. It includes the Oracle home, required and available disk space, and the language 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 start installing this language. |
|
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 from the language pack to the appropriate Oracle homes. When the installation progress indicator shows 100 percent, click Next to continue. |
|
Policy Store Analysis (Note that this screen displays only when the |
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 are included in the language pack 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 you want Language Pack Installer to 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 Language Pack 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 Language Pack Installer with the choice you selected, after the installation is complete. If you choose Apply all changes and overwrite customizations, then you may need to reapply the customizations that are overwritten after the installation 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 installation 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 Language Pack 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 in the message pane as it is performed. Tasks that could be included in the configuration phase are described in Table 6-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". Links to troubleshooting specific failures are available in Table 6-1. |
|
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 after you resolve failed configuration tasks, click Cancel. |
Proceed to Section 6.6, "Complete the Post Installation Tasks".
Perform the following steps to start Language Pack Installer in silent mode from the command line, using specific options to further define the necessary actions. You must run Language Pack 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 Language Pack 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 Language Pack Installer will use for policy store changes to each stripe. Note that these properties are required only if the J-DupdateJAZNPolicyStore option is set to true with the runInstaller command.
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 Language Pack 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 Language Pack Installer. An example follows:
$REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -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, Language Pack 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.7.2.3, "Inventory Pointer File is Empty".
Run the following command to start Language Pack Installer in silent mode:
Note:
Refer to Section 5.7.5, "General Troubleshooting During the Configuration Phase in Silent Mode" if any failures occur.
(Unix) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -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][-logfile log_file_name][-debug] (IBM AIX on POWER Systems (64-bit) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -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][-logfile log_file_name][-debug] (Solaris X64 and Solaris Sparc) $REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -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][-logfile log_file_name][-debug] (Windows) %REPOSITORY_LOCATION%\installers\fusionapps\Disk1\setup.exe -addLangs -jreLoc APPLICATIONS_BASE\fusionapps\jdk6 [-Dworkers=number_of_workers][-DlogLevel=level] -silent -response location_of_silent.rsp_file [JAZN_EXIST=true] [-DpatchDownloadLocation=patch_directory][-logfile log_file_name] [-DserverStartTimeout=timeout_period_for_server_in_seconds] [-debug]
Table 6-6 shows valid options that can be used when running Language Pack Installer in silent mode.
Table 6-6 Language Pack Installer Command Options in Silent Mode
| Option Name | Description | Mandatory |
|---|---|---|
|
|
Runs Language Pack Installer to install one language. |
Yes |
|
|
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 Language Pack Installer in silent mode. |
Yes. |
|
|
The location of the response file, silent.rsp. |
Yes. |
|
|
Required for the Deploying Applications Policies configuration task. |
No, use only when |
|
( |
Updates the policy store with translated attributes so field descriptions, display names, and other attributes display their translated values. |
No, use only when you do not want to use base English. |
|
( |
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 Language Pack Installer. See "Worker Calculation" in Section 3.1.2, "Patching Database Artifacts". |
|
|
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 Language Pack Installer. See Section 6.3.3, "Download Mandatory Post-Installation NLS Patches". |
No, the default is |
|
( |
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 |
|
|
Retrieve debug information from Language Pack Installer. |
No |
Proceed to Section 6.6, "Complete the Post Installation Tasks".
Perform the following required manual steps after Language Pack Installer completes successfully:
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".
Confirm there are no unresolved errors or exceptions in the log files. For information about resolving errors, see Section 6.7, "Troubleshoot Language Pack Installer Sessions".
Bounce all servers using the fastarstop script "bounce" option. For more information, see "fastartstop Syntax" and "Starting Examples with fastartstop" in the Oracle Fusion Applications Administrator's Guide.
Note:
If you are installing more than one language in an environment, you need to bounce servers only once, at the end of installing all languages in that environment to minimize time spent bouncing servers.
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 6.7.1, "Language Pack Installer Log File Directories".
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.
Disable the anonymous binds that you enabled in Section 6.4.3, "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.
Review the JAZN Analysis reports for potential conflicts and deletions that are not patched automatically by Language Pack 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 Language Pack 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 Applications Role conflict that has been modified by both the patch and production, therefore it will not be applied by Language Pack 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
Perform any steps listed in the Post-Installation Tasks section of Oracle Fusion Applications NLS Release Notes.
This section provides information to assist you in troubleshooting Language Pack Installer sessions specifically. For troubleshooting issues that are generic to both RUP Installer and Language Pack Installer, see Section 5.7, "Troubleshoot RUP Installer Sessions".
This section contains the following topics:
Table 6-7 contains a list of log directories for Language Pack Installer activities.
Table 6-7 Log Directories for Language Pack Installer Activities
| Log directory name | Description |
|---|---|
|
|
Installation phase logs |
|
|
Top level directory for Language Pack Installer logs |
|
|
Loading Database configuration task logs |
|
|
Activate language configuration task logs |
|
|
StartStop utility logs |
|
|
Log files from SOA Composite activities Note that SOA server logs are located under respective domains. For example, the SOA server logs for CommonDomain are under |
Perform the following steps when an error occurs during the installation phase:
Click Cancel to exit Language Pack Installer.
Review the log files to determine the cause of the failure. The log files reside in APPLICATIONS_BASE/logs/installtimestamp.log.
Resolve the cause of the failure.
Start Language Pack Installer using the same command syntax that you used for the previous incomplete installation. For more information, see Section 6.5.1, "Run Language Pack 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, Language Pack 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:
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. Language Pack 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 Language Pack 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.
During the installation phase of Language Pack 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 Language Pack Installer.
After running Language Pack Installer, the contents of oraInst.loc were removed.
Language Pack 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 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.
Oracle Fusion Applications content is translated to different languages and fixes are made available as individual patches. If your environment uses multiple languages, whenever you apply a patch with translatable content, you may also apply the associated translated patch for each of your installed languages. If a patch does not contain any translated content, such as a PL/SQL package, only the English patch is available.
If an Oracle Fusion Applications environment contains languages other than English, the recommended method for applying patches is to apply the English patch first and then apply the translation patch for each installed language.For example, after you apply a language pack for another language, such as Korean, whenever you apply a patch that involves translatable content, you must apply the base English patch and also the Korean patch for that fix.
For detailed information about how to apply a patch, see Section 3.4, "Applying Patches".
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|