USAGE OF INDIA LOCALIZATION PATCH TOOL (INDPATCH)
Oracle Application - India Localization - Version: 11.5.5 to 11.5.10
Information in this document applies to any platform.
Purpose
This bulletin provides you the following details of India Localization Patch Tool - INDPATCH
a) Salient features
b) Technical aspects
Scope and Application
About the Tool
The India Localization Patch Tool is designed to apply India Localization patches. All India Localization patches which are patch tool compliant clearly mention in the readme as to how to apply them using the patch tool. There are several options which can be used during application of the patch using the Patch Tool which are clearly detailed in the Patch Tool User Manual.
USAGE OF INDIA LOCALIZATION PATCH TOOL (INDPATCH)
Listed below are the salient features of the Patch Application Tool :
1. Applies the India Localization patch-tool compliant patches.
( You would find many patches of India Localization which are not patch tool compliant. These patches need to be applied as per instructions in the readme only if you have not applied Cummulative Patchset IN60107)
2. Performs Version checking, so latest objects will never get overwritten by old ones.
3. Performs backup of the following objects :
a. All database objects - functions, triggers, package ( body and spec ), procedures and views.
b. Forms(.fmb), reports(.rdf), form libraries (.pll) and seeded data (.ldt).
4. Every aspect of patch application is clearly detailed in the logs generated.
These logs can be used to diagonize patch application failures easily and quickly.
The following are the types of logs generated :
a. Main log : This is by default $JA_TOP/$APPLLOG/
b. L*.log : Concurrent application logs upon application of ".ldt" files using FNDLOAD command.
c. *.err : Compilation details of forms to generate ".fmx" files.
d. odf.log : Application details of odf files.
5. Takes the following parameters :
* drvr_file - Name of the driver file, usually
* fnd_patchset - The patchset level of FND on the environment. This information is required for successful application of ldt files in the patchset. Values can be between the range [A-Z]. No default provided, Mandatory.
* appspwd - Password of APPS schema. Default value is "apps".
* japwd - Password of JA schema. Default value is "ja".
* mode - any combination of letters "F", "C" and "D". Give "F", if the node is Forms Server node, "C", if the node is concurrent processing node and "D", if Database node. Default is "FCD", meaning a single node instance. For multi-node, apply the patch with
appropriate mode specified.
* logfile - Name of the logfile to which the log messages will be written. Default is $JA_TOP/$APPLLOG/
* test - Y/N, "N" being the default. If test="Y", then the patch is not actually applied, but only the versions of objects are displayed on screen, listing what objects will be applied and what will not be.
* paramfile - Instead of the above, just one single parameter file can be given as an argument, in which all the above parameters can be stored.
* systempwd - Password of SYSTEM schema. Default value is "manager".
Technical aspects of the tool
The tool is a perl script which can be run from command line by providing appropriate parameters. It calls sql scripts for version checking and backup.
Process to start applying a patch-tool compliant patch ( say
1. The patch would be a zip file which needs to downloaded from metalink and unzipped.
2. On unzipping, a directory would be created with
3. The Readme_
Automated Patch Application Steps
=================================
If you have applied the patch Patch 5458248 from metalink (India Localization Patch Application Tool), you should be able to apply this patch using that tool.
4. If you have not installed patch application tool, then you need to download patch Patch 5458248
a. You need to copy the zip to JA_TOP and unzip it there.
b. Follow the "User Manual" to install the Patch Application Tool.
c. Using the patch application tool, go to the directory where you have downloaded the patch
d. Apply the patch using a command similar to the one given below :
perl $JA_TOP/inpatch/indpatch.pl drvr_file=
5. If you already have the patch application tool, then you can use this tool to apply the patch
Please note that if you are at using an older version of the patch tool, on patch application using the old tool you will be prompted to download the latest patch tool.
6. It clearly details all the status of the application of the patch tool.
The status would be similar to the one given below :
STATUS :
Patch application completed successfully.
Please check /slot05/appmgr/ILCERTappl/ja/11.5.0/log/ILCERT/5352145/5352145.log for patch application details.
Alternatively you can also check the patch application status using the following query as "APPS" user.
select * from jai_applied_patches where patch_number = '
7. If the patch had not got applied successfully, then please log a TAR with the following information.
a. Patch number
b. Command used to apply the patch
c. Zip the log file directory specified as an argument logfile to patch application tool or the default directory.
(
default path for log files : $JA_TOP/$APPLLOG/
or
perl $JA_TOP/inpatch/indpatch.pl logfile=/slot05/appmgr/ILCERTappl/5352145/5352145_applied.log
then log files would be present in /slot05/appmgr/ILCERTappl/5352145 directory
)
d. Output of the following query :
select * from jai_applied_patches where patch_number = '
8. Even if the patch application is successful, customers have customization which needs to be incorporated to the main files.
In this scenario, the old files which have got overwritten by files in the patch
You need to manually make the changes and apply the objects.
No comments:
Post a Comment