AD Utilities(adrelink ,adident,ADMRGPCH)

Last updated on August 27th, 2016 at 05:40 am

We will be discussing three main ad Utlities in this section ADRELINK,ADIDENT,ADMRGPCH


• Adrelink utility relinks Oracle Applications executable programs with the Oracle server product libraries.
• For most products, you run this utility in AD Administration by choosing the Relink Applications Programs task from the Maintain ApplicationsFiles menu.
Note :- you cannot use AD Administration to relink AD executables, you must run AD Relink manually to link these programs.
• adrelink errors are recorded in AD Relink log file (adrelink.log) under $APPL_TOP/admin/$TWO_TASK/log

AD Relink requires several parameters, including the “force” parameter and optional arguments. There is no default value for the “force” parameter: setting it to “n” means relink the executable program only if the dependent libraries or object files are more recent than the current executable program, and setting it to “y” means relink regardless of the status of the libraries or object files.

Command line Generations

Relinking AD Executables force=y ranlib=y ‘AD adpatch’


• adident can be used to identify the version and translation level of Oracle Applications files.
• It is useful when you are troubleshooting Applications related issues.

On Solaris boxes the usage is
adident Header File_Name_1




  • AD Merge Patch (admrgpch) is a utility that is designed to merge multiple AutoPatch compatible patches into a single integrated patch.
  • It is an executable located in the bin directory of AD_TOP. To merge two or more patches into a single integrated patch,
  • run admrgpch with the following arguments:

admrgpch -s <source directory>  -d <destination directory> -merge_name  <mergename>

  • The <source directory> is the directory in which the patches to merge have been unloaded.
  • The <destination directory> is the directory in which admrgpch will create the merged patch.


How ADMRGPCH Works ?

  • This utility reads the u.drv for each patch in the source directory and merges them to create u<merge_name>.drv in the destination folder
  • It also merges the set of files contained in the individual patches under the source directory according to file revision and copies them to the destination directory. If a file is contained in more than one source patch, only the highest revision of the file is copied to the destination directory.
  • Actions in the merged patches are grouped by product then by patch number.
  • Comments in the merged readme.txt are also ordered by product then by patch number.
  • After admrgpch runs, you should check the admrgpch.log file for errors.
  • The admrgpch.log will be located from the location where you run the admrgpch command
  • You should be able to merge the prereq  patch with the main patch


Executing the merge of the patch drivers
— Processing patch: source/5875588
— Done processing patch: /source/5875588
— Processing patch: /source/9468060
— Done processing patch: /source/9468060
— Processing patch: /source/9464060
— Done processing patch: /source/9464060
Copying files…
5% complete. Copied 269 files of 5000…
10% complete. Copied 538 files of 5000…
15% complete. Copied 806 files of 5000…
20% complete. Copied 1075 files of 5000…
25% complete. Copied 1344 files of 5000…
30% complete. Copied 1612 files of 5000…
35% complete. Copied 1881 files of 5000…
40% complete. Copied 2150 files of 5000…
45% complete. Copied 2418 files of 5000…
50% complete. Copied 2687 files of 5000…
55% complete. Copied 2956 files of 5000…
60% complete. Copied 3224 files of 5000…
65% complete. Copied 3493 files of 5000…
70% complete. Copied 3762 files of 5000…
75% complete. Copied 4030 files of 5000…
80% complete. Copied 4299 files of 5000…
85% complete. Copied 4568 files of 5000…
90% complete. Copied 4836 files of 5000…
95% complete. Copied 5105 files of 5000…
100% complete. Copied 5000 files of 5000…
Character-set converting files…
3 unified drivers merged.
Patch merge completed successfully

Please read followings link for more information
Autopatch part -2

AD utilities-3

Autopatch -4

Autopatch -3

Troubleshooting Autopatch failures

How to reduce the Patching downtime

What is Adop in R12.2

R12.2 adop explained in detail

Distributed AD

Autopatch Part 1

Leave a Reply