Maintaining System

Adding and Maintaining NLS Languages

Requirement : I want to add an additional language to my existing system.

Discussion : You can add a new language to your Release 12 system at any time after your

Actions

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. For the language (or languages) you are adding, refer to the Oracle Applications NLS Release Notes for your current release level to determine if you need to apply any specific NLS patches. If no patches are applicable, skip this step. If you are adding more than one language, and a patch is required for each, you should use AD Merge Patch to create a merged patch.

Note: For more information, see Oracle Applications Patching Procedures for information about merging NLS patches.

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

If you have already run the Translation Synchronization Patch utility by following the Oracle Applications NLS Release Notes as mentioned in Step 3, you can omit this step and step 5.

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).

Adding New Off-Cycle Products: using adsplice

Products that are released in between maintenance releases are sometimes referred to as off-cycle products. Since these new products do not appear in the OAM License Manager, you must add them to your product list by using AD Splicer. This utility splices the product into the list of existing products that are known to your system. This process makes the product available, so that you can register it as active, and thus,Maintaining Your System make it available to the AD maintenance utilities, such as AutoPatch.Once you splice the product, you use AutoPatch to install all product-related files.

###Actions###

Perform the following steps:

1. Download the initial product patch from My Oracle Support. This patch contains information about the new product, AD Splicer control files required to add the product, and the associated product files.

2. Review the readme file. Unzip the patch in the patch top directory. The patch readme file contains information on how to install the product. It may include manual steps to perform as part of this process.

3. Copy AD Splicer control files and product configuration file.

Copy <prod>prod.txt, <prod>terr.txt, and newprods.txt to APPL_TOP/admin.

Caution: If a newprods.txt already exists from a previous AD Splicer session, rename the existing file before copying the new newprods.txt file.

Note: If you want to change the default tablespace, you need to edit file $APPL_TOP/admin/newprods.txt, and change parameters main_tspace ,index_tspace and default_tspace.

# Table spaces may need to be editted to fit database setup

main_tspace=APPS_TS_TX_DATA

index_tspace=APPS_TS_TX_IDX

temp_tspace=TEMP

default_tspace=APPS_TS_TX_DATA

WARNING: Others information included in newprods.txt, cllterr.txt and cllprod.txt files cannot be changed.

cd $PATCH_TOP

cd 6436521/cll/admin

cp *.txt $APPL_TOP/admin/.

4. Add the off-cycle product to the list of products. Log on as applmgr, set the environment, and run AD Splicer. It modifies the APPL_TOP and database, then performs the same registration function as OAM License Manager.

UNIX:

$ cd $APPL_TOP/admin

$ adsplice

5. Run the AD Configuration report (adutconf.sql). Review the list of registered products to verify that the product was spliced properly into the database.

6. Re-set the instance environment

7. Verify that <PROD>_TOP registry and environment variables are set correctly for the newly spliced off-cycle products.

8. Download and apply the patch that introduces the product functionality. Once you splice the product, you use AutoPatch to install all product-related files.

9. Check if the installation was successfully applied by running the queries below with APPS user.

QUERY 1:

select application_id, application_short_name, basepath from applsys.FND_APPLICATION

QUERY 2:

select application_id, product_version, tablespace, index_tablespace from applsys.FND_PRODUCT_INSTALLATIONS

where application_id = <value from Query 1>;

10. Fix the $XXX_TOp on $CONTEXT_FILE

11. Run AUTOCONFIG