| Oracle® Fusion Applications Patching Guide 11g Release 1 (11.1.4) Part Number E16602-15 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Patching Guide 11g Release 1 (11.1.4) Part Number E16602-15 |
|
|
PDF · Mobi · ePub |
This chapter describes how to install and maintain a set of languages in Oracle Fusion Applications.
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 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, and Applications Policies. You install language packs with Language Pack Installer.
Language Pack Installer enables you to add a language to your Oracle Fusion Applications environment and delivers translated artifacts for that language. You run Language Pack Installer in interactive mode and proceed through the installation by providing information in the user interface when prompted. For more information, see Section 5.1.3, "RUP Installer User Interface", which is the same as the Language Pack Installer user interface.
Language Pack Installer performs the following tasks:
Copies language artifacts to the appropriate directory in FA_ORACLE_HOME. For more information see Section 2.1.2, "Oracle Fusion Applications Oracle Home".
Enables the new language in the FND_LANGUAGES table.
Runs the AD Administration process to maintain multi-lingual tables, which prepares the tables for the data to be copied from the source language to the new language.
Updates the language content using the database artifacts for the new language that are included in the language pack.
Applies the updated translated middleware database content.
Deploys Service-Oriented Architecture (SOA) resource bundles.
Uploads LDAP Data Interchange Format (LDIF) translation XLF files to Oracle Internet Directory (OID).
Enables the language.
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.
Language Pack Installer supports the installation and automated deployment of middleware and database artifacts used by Oracle Fusion Applications and related to languages. Table 6-1 provides a quick reference that depicts how Language Pack Installer supports the Oracle Fusion Applications artifacts that could be included in a language pack. Language Pack Installer always copies the artifacts from the language pack to the appropriate location on your system. The table describes additional actions that are performed automatically for each artifact.
Table 6-1 Artifacts Supported by Language Pack Installer
| Artifact Type | Automated Actions Performed By Language Pack Installer |
|---|---|
|
Translated ADF resource bundles |
Deploy resource bundles. |
|
Applications Policies ( |
Deploy changes to the policy store. Also updates the policy store if you chose to override the base English strings in the policy store. |
|
Oracle Business Intelligence Publisher (Reports and Captions) |
Deploy to the Business Intelligence repository using Catalog Manager, and start the BI Presentation server after patching |
|
Common Resource (Activity Strings) |
None |
|
Flexfields |
Deploy flexfields |
|
LDAP Data (LDIF) |
Upload translated LDIF content to the identity store |
|
Translated content for seed data (XLF) |
Upload translated seed data |
|
SOA Resource Bundle |
Deploy SOA resource bundle and restart dependent composites |
During the installation phase, Language Pack Installer copies all of the files from the language pack to the 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. 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 configuration phase, you can abort or retry the task. The options available for managing failed tasks and steps depends on whether the task is a mandatory task. For more information, see Section 5.6.3, "General Troubleshooting During the Configuration Phase".
Table 6-2 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 select the Retry button. If available, links are provided to relevant troubleshooting sections.
Table 6-2 Configuration Tasks Run by Language Pack Installer
| Name | Mandatory | Description | Retry Behavior |
|---|---|---|---|
|
Activate Language |
Yes |
Activates the language in the database and runs the Maintain Multilingual Tables utility to maintain the tables related to the newly activated language. For more information, see Section 10.3.4, "Maintaining Multi-lingual Tables". |
Runs Activate Language again. |
|
Offline Preverification |
Yes |
Performs the following validation checks while all servers are shutdown:
|
Runs failed steps. |
|
Synchronize Multilingual Tables |
Yes |
Prepares tables for the data to be copied from the source language to the new language. |
Restart from failure. |
|
Apply Middleware Language Patches |
Yes |
Applies both the patches in the Language Pack repository and the downloaded patches from My Oracle Support in the |
Applies the failed patches. See Section 5.6.6, "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.6.9, "Troubleshooting Loading Database Components". |
|
Deploy Applications Policies (jazn-data.xml) |
Yes |
Oracle Fusion Applications allows one policy store per language. The |
Deploys the failed stripes. See Section 5.6.11, "Troubleshooting Deployment of Applications Policies". |
|
Deploy BI Publisher Artifacts |
Yes |
Copies captions and deploys BI Presentation Catalog to the Oracle Business Intelligence repository using Catalog Manager. |
Starts from the beginning of the task. See Section 5.6.14, "Webcat Patch File Creation Failure During Deployment of BI Publisher Artifacts". |
|
Verify Node Manager and OPMN Status |
Yes |
Checks for access to the Node Manager and the Oracle Process Manager and Notification Server (OPMN) control process. You must not exit out of Language Pack Installer during this task. |
This step will only fail if the node manager and OPMN control processes are already running. In case it fails, restart the Node Manager and OPMN and click Retry. |
|
Start All Servers |
No |
Starts servers that must be running for the deployment of the remaining artifacts in the language pack. |
Restarts failed servers. See Section 5.6.18, "Troubleshooting Server Start and Stop Failures". |
|
Online Preverification |
Yes |
Performs validation checks that require all servers to be running. The following validation steps are performed during this task:
|
Runs failed steps. See Section 5.6.19, "EditTimedOutException Error During Online Preverification". |
|
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 identity store. |
Retries only failed XLIFF files. |
|
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. |
|
Post Configuration |
No |
Reactivates the ESS Server from inactive mode. |
Retries failed domains. |
This section describes the following preparation steps for installing a language pack, all of which can be performed before your scheduled down time.
The language pack repository contains the language pack installer, translated Oracle Fusion Middleware patches, and the Oracle Fusion Applications language pack 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-3 list the installers in the language pack repository.
Table 6-3 Language Pack Installers
| Media Label Name | Staging Destination |
|---|---|
|
Language Pack Installer |
(Unix) (Windows) or |
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 a upgraded environment, ensure that you have followed all tasks described in Section 5.5, "Complete the Post Installation Tasks".
In either case, you must also perform the steps in the "Post-Installation" section of Oracle Fusion Applications release notes.
Follow this step only if you have updated OPatch in the 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.
If the file, FA_ORACLE_HOME/OPatch/ocm/lib/emocmclnt.jar 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.
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.
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 in Unix platforms 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.)
Check the local port range value in /proc/sys/net/ipv4/ip_local_port_range before starting the Language Pack installation. The recommended value is 32768 61000. If the range is set to any value below 32768, a system process could potentially use a port that was assigned to one of the Managed Servers.
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
Review the following steps to confirm that your database settings are optimized for the language pack installation.
Refer to Oracle Fusion Applications release notes for information about database tuning parameters, to avoid time out conditions 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.
Note:
If you are upgrading from a previous release, Oracle homes are likely to be already registered properly, so you can skip this step now.
Oracle Provisioning records information about the following Oracle homes separately from information about other products: Oracle Business Intelligence (Oracle BI), Oracle Global Order Promising (GOP), Web tier, and Web tier Common Oracle home installation information. Patching expects information about all products to be recorded in the same place. To transfer information about the 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 Language Pack 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
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
Register the dependency between the BI Oracle home and Oracle Common Oracle home.
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
Register the dependency between Web tier Oracle home and Web tier Common Oracle home.
(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 ATTACH_HOME command does not cause any issues.
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.
The section describes the following mandatory preparation steps for installing a language pack, all of which must be performed during your system down time.
This section contains steps to follow for all platforms. For Windows platforms, also follow the steps in Section 6.3.1.8, "Steps For Windows Platforms"
Stop only Fusion Applications middle tier servers and processes including BI servers and WLS administration and managed servers.
Confirm that the OPMN control process and Node Manager are running. If they are not running, follow the steps in Table 5-8 under "Welcome" to start them.
Start the OPSS Security Store if it is not already running. 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). If this server is not running prior to starting the installation, the related configuration tasks will fail. For more information, see Section 5.6.8, "LdapServerCheck Failure During Offline Preverification".
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 Oracle Fusion Applications 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.
Follow these steps before you install a RUP on Windows platforms.
Change the service type from Automatic to Manual for the following services: Node Manager, webtier, GOP, and BI. Restore the service type back to Automatic after RUP installation completes.
Stop the following services: Node Manager, webtier, 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 the Language Pack Installer. Before starting the Language Pack 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.
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.3.8.3, "Back Up Steps for Windows Platforms".
Apply any prerequisite patches listed in the Pre-Installation section of NLS release notes and Oracle Fusion Applications release notes prior to starting Language Pack Installer.
Language packs must be installed during downtime. 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.
This section contains the steps to install a language pack with Language Pack Installer. It contains the following topics:
Ensure that the steps in Section 6.2, "Prepare to Install a Language Pack Pre-Down Time" and Section 6.3, "Prepare to Install a Language Pack - During Down Time" are successfully completed. Then follow the steps in this section.
Note:
If Language Pack Installer encounter errors, refer to Section 6.5, "Troubleshooting Language Pack Installer Sessions" before clicking any buttons in the Language Pack Installer user interface.
Start Language Pack Installer from the command line, using specific options to further define the necessary actions. Table 6-4 shows valid options that can be used when running Language Pack Installer.
Set the PATH environment variable to include APPLICATIONS_BASE\fusionapps\jdk6 as follows.
(Unix) export JAVA_HOME=APPLICATIONS_BASE/fusionapps/jdk6 export $PATH=$JAVA_HOME/bin:$PATH (Windows) set JAVA_HOME=APPLICATIONS_BASE\fusionapps\jdk6 set PATH=%JAVA_HOME%\bin;%PATH%
Confirm registration of the network location of FA_ORACLE_HOME.
If Oracle Fusion Applications Oracle home directory (FA_ORACLE_HOME), which is located under the APPLICATIONS_BASE/fusionapps directory, is registered in inventory with a /net path then provide the oraInst.loc location including /net while starting the Language Pack Installer. An example follows:
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. In the example, this results in a copy of the file to itself, which causes a zero byte file. This causes failure during the copy phase when oracle_common patches are applied. For more information, see Section 5.6.2.3, "Inventory Pointer File is Empty".
Start Language Pack Installer
(UNIX) REPOSITORY_LOCATION/installers/fusionapps/Disk1/runInstaller -addLangs -jreLoc JAVA_HOME_LOCATION [-invPtrLoc FA_ORACLE_HOME/oraInst.loc] [-J-DupdateJAZNPolicyStore=true] [-J-Dworkers=number_of_workers][-J-DlogLevel=level] (Windows) REPOSITORY_LOCATION\installers/fusionapps\Disk1\setup.exe -addLangs -jreLoc JAVA_HOME_LOCATION [-DupdateJAZNPolicyStore=true] [-Dworkers=number_of_workers][-DlogLevel=level]
Table 6-4 Language Pack Installer Command Line Options
| 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 need to specify the absolute path. |
Yes. |
|
|
The location of an overriding inventory pointer file. If Oracle Fusion Applications Oracle home directory ( |
No, use only 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". |
|
|
Retrieve debug information from Oracle Universal Installer. |
No. |
|
( |
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 |
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 -jreLoc APPLICATIONS_BASE\fusionapps\jdk6 -addLangs -DupdateJAZNPolicyStore=true
Table 6-5 illustrates the tasks that Language Pack Installer runs. For information about log files generated during language pack installation, see Section 6.5.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 that is complete and indicates the location of the installation log file. The installation step consists of copying files from the Language Pack to the appropriate Oracle homes. The configuration process starts 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 enabled for the following 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 and decide 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 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 Section 6.1.5, "Language Pack Installer Configuration Tasks". 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. Do not cancel and exit out of Language Pack Installer in response to this task. If starting of servers times out, see Section 5.6.18, "Troubleshooting Server Start and Stop Failures". No additional user action is required in the Configuration Progress screen unless a failure occurs. |
|
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. |
Perform the following required manual steps after Language Pack Installer completes successfully:
Confirm that all 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.5, "Troubleshooting Language Pack Installer Sessions".
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 6.5.1, "Language Pack Installer Log File Directories".
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 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.6, "Troubleshoot RUP Installer Sessions".
This section contains the following topics:
Table 6-6 contains a list of log directories for Language Pack Installer activities.
Table 6-6 Log Directories for Language Pack Installer Activities
| Log directory name | Generated from... |
|---|---|
|
|
Installation phase |
|
|
Top level directory for Language Pack Installer logs |
|
|
Configuration phase when database actions run |
|
|
Configuration phase when language is activated |
|
|
StartStop utility Note that server logs are located under respective domains. For example, the AdminServer log for CommonDomain is under |
|
|
SOA Composite activities Note that SOA server logs are located under respective domains. For example, the SOA server logs for CommonDomain are under |
Follow these 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 oracle_inventory/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.4.1, "Perform the Installation". After canceling the previous installation and starting again, you must choose to continue with the previous 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.
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 choose to 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, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|