Monday, July 13, 2009

Installing Dutch NLS

- Make sure to have a valid backup of the applications system
- Make sure the latest AD.I has been applied
- Make sure all the terminologies has been understood from Note # 399789.1
- Apply the database patch # 5005469 else multi-lingual update will fail on ICXNLINS.sql, CSNLINS.sql
- Apply patch # 6908630 else the PNXVAREN.fmx will fail
- Check the v$nls_parameters
select value "Character Set" from V$NLS_PARAMETERS where parameters='NLS_CHARACTERSET'; NOTE: The output should be UTF-8, or else the existing character set should be converted to UTF-8
- Change language configuration:
Use the Oracle Applications Manager (OAM) License Manager tool to change the language configuration or activate a new language in an existing system.
Navigation: From OAM, navigate to Sitemap -> License manager -> Languages
Select the “Dutch” language and install it,
- Update multilingual tables:
Update all multilingual tables using ADADMIN. Run adadmin and navigate to:
Maintain Applications Database Entities menu -> Maintain multi-lingual tables
- Log on to Applications' administration node as the APPLMGR user and source the APPL_TOP environment file. Use the manifest generation tool to generate a manifest file by executing the following command:
perl $AD_TOP/bin/adgennls.pl
The manifest generated from the tool is located at
$APPL_TOP/admin/$TWO_TASK/out/adgennls.txt
Generate the manifest from
http://updates.oracle.com/TransSync (use your My Oracle Support username and password).
- Download and Apply Translation Synchronization Patch # 8670288 using adpatch with reference to the readme.txt file
- Apply the online help patch # 3275245 for Dutch (NL), the American Language version already included with 11.5.10.2
- Run the AD Administration utility to generate message files from the Generate Applications Files menu.
- Start up the applications

1 comment:

Unknown said...

looks great. The parsing of corrupted documents can be also performed by the recovery for sql server utility, it is the fastest way to open affected files