Вы находитесь на странице: 1из 2

Merging Patches Using ADmrgpch

------------------------------
You can merge multiple patches into a single patch by using AD Merge Patch.
This AD utility is an executable located in AD_TOP/bin that merges multiple
AutoPatch compatible patches into a single, integrated patch. Once the merge is
complete, you use AutoPatch to apply the resulting patch in a single operation.
Using a merged patch reduces the time it takes to complete the patching process.
The command for merging patches is admrgpch.

AD Merge Patch reads the c<patchnum>.drv, d<patchnum>.drv, and g<patchnum>.drv


for each patch in the source directory and merges them to create a single set
of driver files (for example, cmerge99.drv, dmerge99.drv, and gmerge99.drv) in
the destination directory. 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 exists in more than one
source patch, only the highest revision of the file is copied to the
destination directory.

Complete these steps:


1. Review the readme files carefully.
Some patch readme files contain special instructions for applying merged
patches. The patch may also require manual steps.
2. Create directories.
In the patch top area, create a source directory and a destination directory.
Choose any name for these directories.
3. Unzip patches.
Copy all the patches to be merged into the source directory and unzip them.
4. Run AD Merge Patch.
Run AD Merge Patch and supply the arguments for the destination directory
name and the source directory name. You also need to specify the merged patch
name, or accept the default.
5. Check AD Merge Patch log files.
After AD Merge Patch runs, check the admrgpch.log file for errors. The file
is located in the current working directory (where AD Merge Patch was run).
6. Run the merged patch.
Once a merged patch is created, apply it just like a single patch.

AD Merge Patch cannot merge patches of different releases, different parallel


modes, or different platforms. However, it can merge patches for a specific
platform with a generic patch, or patches with different source character sets.
AD Merge Patch notifies you if you try to merge incompatible patches.

This utility is availabble under under AD_TOP/bin

There are 2 ways to you can use this utility. Just copy all the patches that you
need to merge
as single patch. Make sure that they all belong to the same version. Open the
driver file and
check the version in the header.

compatible release 11.5.0


compatible platform GENERIC
characterset us7ascii
extension recordpatch 4219646 US
extension patch_type software base
compatible feature checkfile

NLS lang and release should be the same for all the patches which will be merged as
one. Place
all the zip files under one directory and unzip all the patches in the same
directory. This
becomes your source and create a directory at the same level where you have the
source
directory. Following are the usage details

usage: admrgpch -help


admrgpch
admrgpch -s -d [-verbose ] [-merge_name ] [-manifest ] [-logfile ]where * -help
Print help message. * -verbose Can be one of: { 0(SILENT), 1(QUIET), 2(VERBOSE) or
3(LOUD) } Default - 1(QUIET). * -merge_name The name of the merged patch (max 24
characters). Default - "merged". * -s Path of source directory where all patches to
be merged have been unzipped. * -d Path of destination directory where the merged
patch will be created. * -manifest Full pathname of a file containing the list of
patch zip files to be merged. * -logfile Admrgpch log file name.
Default:"/admrgpch.log".

If an Oracle Applications system contains multiple languages other than American


English (US) and you are applying multiple patches for each language, the
recommended method is to merge all US patches into a single patch and all patches
for every non-US language into a single patch. Then, apply the merged US patch
followed by the merged language patch.

You can also merge US patches with the additional language patches or merge each
language in separate language-specific patches. Depending on your downtime window
and your system topology, it may be necessary to keep the US and non-US patches
separate. This procedure assumes that you will apply US and language patches
separately.

Вам также может понравиться