How to troubleshoot untranslated menus after implementing NLS

Troubleshoot untranslated menus after implementing NLS

++++++++++++++++++++++++++++++++++++++++

1). Check the database character set use:

SQL> select value "Character Set" from V$NLS_PARAMETERS where parameter='NLS_CHARACTERSET';

Character Set

----------------------

UTF8

2). you need to enable French & German from OAM

Enabling the Arabic from OAM, folllow the below steps

Login to OAM as a sysadmin -> sitemap -> License Manager -> License -> Languages And license the following language

3). Validate the language activated:

SQL> Select NLS_LANGUAGE from FND_LANGUAGES where INSTALLED_FLAG in ('B','I');

NLS_LANGUAGE

---------------------------------------

GERMAN

FRENCH

AMERICAN

SQL> col PARAMETER for a30;

SQL> col VALUE for a30;

SQL> select * from V$NLS_PARAMETERS;

4). Stop the application servers

cd $ADMIN_SCRIPTS_HOME

./adstpall.sh apps/pwd

5). Run Maintain Multi-lingual Tables: adadmin

AD Administration Main Menu à  Maintain Applications Database Entities menu (4) à Maintain multi-lingual tables (3).

Note: If any work failed please update with details to support

6). Run Update current view snapshot : adadmin

Maintain Applications Files menu -> Maintain snapshot information -> Update current view snapshot

7). Run the Translation Synchronization Patch utility (adgennls.pl)

Login to applmgr user in application tier, make sure enviorment is sourced properly and execute the following command

perl $AD_TOP/bin/adgennls.pl

Above command will genertate the manifest file which you need to upload to support. Menifist file will be on following location:

$APPL_TOP/admin/$TWO_TASK/out/adgennls.txt

8). Upload the manifest file to oracle support.

     contact Oracle Support for assistance , list of Translation Synchronization patches you requested

 https://updates.oracle.com/TransSync

9). Apply the Translation Synchronization patch: latest translations from Oracle

Follow the instructions in the README file to apply the patch     

10). grep "ias_version" $CONTEXT_FILE

                        <ias_version oa_var="s_ias_version">10.1.3.5.0</ias_version>

grep "JRE_TOP" $CONTEXT_FILE

                        <JRE_TOP oa_var="s_jretop">/d01/oracle/SUPT/apps/tech_st/10.1.3/appsutil/jdk/jre</JRE_TOP>

The German font files from  cd $FND_TOP/resource  need to been copied to

$JRE_TOP/jre/lib/fonts directory on all web and concurrent nodes.

Copy the fonts ALBAN*.ttf to $JRE_TOP/jre/lib/fonts. Steps:

• Copy the font files to the Java default font directory for the external JDK on the HTTP Server node.

$ cp /resource/ALBAN*.ttf /jre/lib/fonts

• Remove Image Files from Cache Directory

Remove all existing non-English language image files from the image cache directory.

$ cd $OA_HTML/cabo/images/cache

$ cd

$ rm *.gif *.imx

11). AD Administration utility to generate message files from the Generate Applications Files menu.

12). Compile the invalid objects using utlrp.

13). Compile Forms and Reports

14). Compile Apps schema and validate apps schema

15). Bring up the applications services,

16). do a complete sanity check and release the instance.

Note: 
Please verify JRE_TOP

dbldxml.pl is not finding the java executable in the expected directory that is pointing the env variable:

 JRE_TOP ==>  $ORACLE_HOME/jre/1.1.8

The 'jre' is not shipped in 11g Database :

To implement the solution, please execute the following steps:

1. JRE_TOP should be set to $ORACLE_HOME/jre/1.4.2 :

export JRE_TOP=$ORACLE_HOME/jre/1.4.2

2. Start the creation of the Contextfile (XML-file) again :

perl adbldxml.pl tier=db appsuser=apps appspasswd=xxxx

The utility can be run by issuing the following command on the database tier:

perl $ORACLE_HOME/appsutil/bin/adbldxml.pl tier=db appsuser=apps appspass=apps

Note: In R12, this utility is supported only on the database tier.

For the appTier Under $AD_TOP/bin/

1). cd $AD_TOP/bin/perl  adclonectx.pl   --> May not work

2). (Or)

$ cd $APPL_TOP/ad/12.0.0/bin

$ perl adconfig.pl contextfile= <INST_TOP>/appl/admin/<STNDBY CONTEXT>.xml run=INSTE8

++++++++++++++++++++++++++++++++++++++++

1478859.1, 1333985.1, 333785.1, 252422.1, 399789.11070033.1 &  788053.1.

++++++++++++++++++++++++++++++++++++++++

What to install? NLS media or TSP (Translation Synchronization Patch)?

TSP patch is basically a customized patch to pull together all the delta files between US (the source of truth) and any activated languages.

See the Adding and Maintaining NLS Languages section in Chapter 1.

Follow the instructions for the business requirement to add a language. 

The Post-installation Tasks section of this document.

Adding and Maintaining NLS Languages:

Perform the following steps:

1. From Oracle Applications Manager, go to License Manager and activate or change your base language to a new one.

2. From AD Administration, run Maintain Multi-lingual Tables (AD Administration Main Menu > Maintain Applications Database Entities Menu).

3. From AD Administration, run Maintain Snapshot Information

4. Run the Translation Synchronization Patch utility (adgennls.pl). .

    If you have already run the Translation Synchronization Patch utility by following the Oracle E-Business Suite NLS Release Notes as mentioned in Step 3,

    you can omit this step and step 5.

    Requesting Translation Synchronization Patches note 252422.1

5. When you are notified that it is available, apply your Translation Synchronization Patch (TSP) for all languages you requested.

6. Install the Release 12 NLS Help, if available (optional).

+++++++++++++Manjunatha++++++++++++++++++++