Adpatch Explained
Brief
As an application DBA we apply patches regularly on EBS environments and these patches might include one-off fixes,mini packs, family packs,etc., These patches might fix the exiting issue but it might be again vulnerable for new bug. So evry patch should be thoroughly tested and then should be moved to PROD.
But many of the DBA's are not aware of the structure of adpatch, its metadata and minimum requirements for the patch to be applied.
Below are the minimum files available in patch zip file and these are mandatory for applying any adpatch.
1) b<bug_number> .ldt - This file contains the bug metadata information and is used to upload the bug metadata to the database after applying the patch and is based on afumsaru.lct
2) f<bug_number> .ldt - This file is used to upload the details of file versions changed or new files plugged into ebs as part of patching
3) marker1.txt - Contains the name of patch zip file
4) patch_metadata.xml - This file contains information of patch contents and action steps to be performed. This is the master copy that will be used by adpatch to apply the patch
5) README.txt/README.html - These contain the instructions of applying adpatch to application
6) u<bug_number> .drv - This is the unified driver which contains various instructions of copy files,compiling objects,forms,etc.,
7) j<bug_number> _per.zip - This zip file may be included in Java patches. A Zipped Resource Unit or ZRU. jcopy command is used to unified driver to apply this j driver to ebs
8) ad_apply_patch.xml - This is invoked from patch_metadata.xml and contains details of driver to be applied
9) product top files - contains tops with various fixes like updated fmb,packages.ldt's,etc.,
Detailed explanation on unified driver and its contents will be posted soon
Inputs are most appreciated.. :)
Brief
As an application DBA we apply patches regularly on EBS environments and these patches might include one-off fixes,mini packs, family packs,etc., These patches might fix the exiting issue but it might be again vulnerable for new bug. So evry patch should be thoroughly tested and then should be moved to PROD.
But many of the DBA's are not aware of the structure of adpatch, its metadata and minimum requirements for the patch to be applied.
Below are the minimum files available in patch zip file and these are mandatory for applying any adpatch.
1) b<bug_number
2) f<bug_number
3) marker1.txt - Contains the name of patch zip file
4) patch_metadata.xml - This file contains information of patch contents and action steps to be performed. This is the master copy that will be used by adpatch to apply the patch
5) README.txt/README.html - These contain the instructions of applying adpatch to application
6) u<bug_number
7) j<bug_number
8) ad_apply_patch.xml - This is invoked from patch_metadata.xml and contains details of driver to be applied
9) product top files - contains tops with various fixes like updated fmb,packages.ldt's,etc.,
Detailed explanation on unified driver and its contents will be posted soon
Inputs are most appreciated.. :)
patch_metadata.xml file: Contains the metadata information about the patch to be applied. admsi.pl reads this file and populates its screens accordingly.
ReplyDeletepatch_metadata.xml file: Contains the metadata information about the patch to be applied. admsi.pl reads this file and populates its screens accordingly.
ReplyDelete