Here are some of the important tables used by and updated by ADPATCH utility.
AD_APPL_TOPS
This table holds the various APPLTOP’s in the Oracle Applications installation that have ever been patched.
AD_APPLIED_PATCHES
AD_APPLIED_PATCHES holds information about the “distinct” Oracle Applications patches that have been applied. If 2 patches happen to have the same name but are different in content (eg. “merged” patches), then they are considered distinct and this table will therefore hold 2 records.
AD_BUGS
AD_BUGS holds information about the various Oracle Applications bugs whose fixes have been applied (ie. patched) in the Oracle Applications installation.
AD_PATCH_DRIVERS
This table holds information about the patch drivers that comprise a patch.
AD_FILE_VERSIONS
This table holds the various versions of Oracle Applications files (real files, not “pseudofiles”),
that have ever been patched or executed in the Oracle Applications installation.
AD_FILES
AD_FILES is the “files repository”. It contains information about the various files that have been patched in the Oracle Applications installation. Some entries are “pseudofiles” and not real files, (eg. directories) in which case some of the columns are not applicable and would then hold the value “DUMMY”
AD_PATCH_DRIVER_LANGS
NLS patches (or more specifically, NLS patch drivers) pertain to a language or multiple languages. This table holds that language (or multiple languages).
AD_PATCH_DRIVER_MINIPKS
This table holds information about the various Mini Packs contained in a patch (driver) AD_PATCH_RUN_BUG_ACTIONS holds the various actions present in “applied” bug (fix). If Autopatch determined not to apply a bug (fix), then this table will not hold any records for that “unapplied” bug fix.
AD_PATCH_RUN_BUG_ACTIONS
Even though a patch may have been applied on an Oracle Applications installation, some actions in some of its included bugs (fixes) may not have got executed if the “Autopatch” utility determined that it was not necessary to execute those actions. In such cases, EXECUTED_FLAG is set to N.
AD_PATCH_RUN_BUGS
This table holds information about the bugs fixed in a specific run of Autopatch. AD_PATCH_RUN_BUGS holds information about the various bugs fixed in a specific run of Autopatch. Even though a patch may have been applied on an Oracle Applications installation, some bugs (fixes) contained in it may not get applied due to some reason. In such cases, the REASON_NOT_APPLIED column holds the reason.
AD_PATCH_RUNS
AD_PATCH_RUNS holds information about the various invocations of Autopatch for applying Oracle Applications patches to a specific release of an Oracle Applications installation. If multiple drivers are run in one invocation of Autopatch, they result in multiple records in this table. These multiple records will all have the same SESSION_ID (because they arose from one Autopatch invocation), but different TASK_NUMBER’s. The TASK_NUMBER’s in this case will be numbered sequentially as 1, 2, 3, etc. Note that when the database driver of a Maintenance Pack is applied, it bumps up the release version by creating a new record in AD_RELEASES, which is then pointed to by the UPDATED_TO_RELEASE_ID column of the old record.
AD_RELEASES
AD_RELEASES holds the various Oracle Applications releases that an installation of Oracle Applications has gone through in its entire life cycle. It should be noted that START_DATE_ACTIVE, END_DATE_ACTIVE and BASE_RELEASE_FLAG are loosely maintained informational columns and are not accurately maintained, and therefore should not be relied upon heavily.
AD_PATCH_COMMON_ACTIONS
This table holds distinct information about the various actions that are (often repeatedly) performed by Autopatch as part of applying patches
adfhrept.sql ? ? ?Patching History ???
Oracle Apps 11i and Ebusiness Suite R12 provides a wonderful utility to get the history of any file applied through patches. When a patch it applied higher version file get implemented in application. This utility will give complete history about a file starting from the initial release till now and which patch has introduced which release at what date.
The file name is adfhrept.sql and is present under
$AD_TOP/patch/115/sql
Following is the usage of file.
adfhrept.sql (filename)
(latest file version only? (Y/N)
(start date(mm/dd/rr or ALL)
(end date (mm/dd/rr or ALL) (patchtype/ALL) (language/ALL) (appltop/ALL)
limit to forms server? (Y/N)
limit to web server?(Y/N)
limit to node server? (Y/N)
limit to admin server?(Y/N)
only patches that change DB? (Y/N)
For example:
$ sqlplus apps/apps @adfhrept.sql adphst.odf N 12/01/00 12/31/08 ALL ALL ALL N N N N N
SQL*Plus: Release 8.0.6.0.0 Production
on Mon Jun 30 12:56:21 2008
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Connected to:
Oracle8i Enterprise Edition Release 8.1.7.4.0 Production
With the Partitioning option
JServer Release 8.1.7.4.0 Production
Writing data to report file adfilerep.xml…
Done writing data to report file adfilerep.xml
Note:
To view the XML report from browser Copy file adfilerep.xml to OA_HTML top directory
Disconnected from Oracle8i Enterprise Edition Release 8.1.7.4.0 Production
With the Partitioning option
JServer Release 8.1.7.4.0 Production
This sql will create an XML file at the same location from where you are running this
utility. You need to mode the XML file to OA_HTML where its corresponding XSLT
file is present. You can then access this XML file using the URL:
http://(hostname):(Apache port)/OA_HTML/adfilerep.xml
Output will be like this....
Search Details
File history for: adphst.odf Latest Vers only?: N
Date Range 12/01/00to12/31/08
Patch Type ALL Language: ALL ApplTop: ALL
Limit to Forms?: N Limit to Web?: N Limit to Conc.? N
Limit toAdmin Servers? N
Limit to patches that contain DB drivers?N
File Details Product Subdir ApplTopName Version Translation Level Patch Id End date
AD patch/115/odf MARMSTQA 115.18 0 2793083 02/22/03 04:11
AD patch/115/odf TEMPLT4 115.21 0 2673262 08/01/03 13:43
AD patch/115/odf rws60068rems 115.26 0 6372396 06/24/08 18:25
Cheers!!!!
No comments:
Post a Comment