Saturday, January 6, 2007

Implementing a new language.

Earlier to install a new language we had to use the corresponding NLS software Media for that language. Once the new langauage is installed, we need to apply all NLS patches of that language corresponding to all the US patches which has been applied on the instance. Needless to say, it requires a lot of time and effort.

Now, we have something called as "Translation Synchronization Patch" via which we can implement a new language by the application of one single patch, for each new language you want to install.

Prerequisites:--
----------------
11i.AD.I.2 or later.


Prepare the instance for the generation of the Manifest file:--
--------------------------------------------------------------

1. Apply Patch 5668199.

This patch delivers the tool required to the generation of the manifest file. You can apply the patch using the adpatch option hotpatch (You don't need to bring the instance down).

Refer Oracle Applications Maintenance Utilities for more details.

2. License the new languaage.

If you have not yet licensed the new language, then you will have to do it now. You can do this via Oracle Applications Manager (OAM) License Manager.

Refer Oracle Applications Maintenance Procedures document.

3. Using adadmin, run maintain multilingual tables from the Maintain Application database objects menu.

4. Run Maintain Snapshot Information.

Run Maintain Snapshot Information on all the nodes. If you have done this already done this, then you don't need to repeat it.

Refer Oracle Applications Maintenance Utilities for more details.

To perform these 4 steps you don't need any downtime.


Generate the Manifest file:--
--------------------------------------------------

1. Log on to your Applications' administration node as the APPLMGR user and source the APPL_TOP environment file.

2. Run the following command to generate the manifest file.

perl $AD_TOP/bin/adgennls.pl

Snapshot of the output-

Please enter the APPS User [APPS]:
Please enter the APPS password: tr5Ue5yV
Manifest file generation is in progress...
Manifest generated in: /visappl/applmgr/11510/admin/VISAPPL/out/adgennls.txt

As seen the manifest file will be generated in the format $APPL_TOP/admin/$TWO_TASK/out/adgennls.txt.

The manifest contains all of your active languages. You do not need to run the tool for each individual languages.

The contents of the manifest file, will be as follows--


# Release: 11i
# Active languages: E, PT, US
# Manifest generated by adgennls.pl 115.6

abm admin/import/US abmactwk.dis 115.1 E:115.1:0 PT:MISS
abm admin/import/US abmcowk.dis 115.1 E:115.1:0 PT:MISS
........................
........................

As you see above, the active languages are US, E (Spanish) and PT (Portuguese). PT was the language which was getting added in this case. The manifest file lists out the missing files for the new language (with the keyword "MISS") in your file system and also lists out any missing files for other active languages, along with version information.


Request the Translation Synchronization Patch:--
--------------------------------------------------

Once the manifest file (adgennls.txt) is generated, login to the following using your metalink username and password, http://updates.oracle.com/TransSync.

Follow the instructions in front of you and upload the file. A Translation Synchronization Patch will be generated for each of your active language, wrt to the manifest file uploaded. The Translation Synchronization Patch will be specific to your instance. This patch will bring the files of all your languages in sync with your corresponding American English language files.

Note, if you select the option to get latest translations, the patch will also bring your translations to the latest levels.

Once the Translation Synchronization Patch is generated you will receive a email indicating how you can down the patch. The release of the patch would take approximately 7-8 hours.

Apply Translation Synchronization Patch:--
--------------------------------------------

1. Take a cold backup of the instance.

2. Enable Maintainance Mode and put the database in No Archive log mode to avoid generation of unnecessary archives.

3. Download the Translation Synchronization Patch and apply it using adpatch. Do follow the readme. Once the patch is applied, do check the patch log file to confirm whether it was applied successfully. Application of the patch might take around 8 hours, depending upon your hardware configuration for each language.

Refer Oracle Applications Patching Procedures guide.

4. Translation Synchronization Patch doesn't deliver iHelp files. We need to download and apply the iHelp patches depending upon the apps version of the instancefor NLS version of the language that is being installed.

For 11.5.10 and later, apply patch 3275245.
For 11.5.9, apply patch 2662802.
For 11.5.8, apply patch 2400604.

5. Once the iHelp patch is applied, put the database in Archive log mode and disable Maintainance mode.

6. Bring the instance up and login as sysadmin user.

7. Submit the concurrent request ‘Rebuild Help Search Index’.

8. Once the ‘Rebuild Help Search Index’ request is completed, submit the request ‘Gather Schema statistics for APPS schema’.

9. Login as the sysadmin user by selecting the language which you have just installed and validate the forms and menus are getting displayed in the new installed language.

The new language is successfully installed!!

You may refer to metalink note 252422.1. Write to us if you have any further queries.

No comments: