Wednesday, June 11, 2008

How to Find Patching History (10.7, 11.0, 11i)

Starting with Oracle Applications 11.5.5 (or 11i.AD.E (Patch 1945611) and
higher) a new autopatch feature that causes all patch history information to be
stored in the database instead of the applptch.txt and applpsum.txt files was
introduced.

Two scripts, adphrept.sql (patch history) and adfhrept.sql (file history),
provide the patch and file history reports (see Note 162498.1). Both are
located in the $AD_TOP/patch/115/sql directory. When the scripts are ran under
the APPS schema from Sql*Plus, they create report files called adphrept.r and
adfhrept.r, respectively.

There are 16 parameters to pass through the adphrept.sql script. It takes some
time to understand how to use these parameters effectively. As an alternative,
the following SQL statements may be used to obtain basic patch history from the
database:

a. To find a list of all the patches that have been applied:
select DRIVER_FILE_NAME
from AD_PATCH_DRIVERS;

b. To find if a particular patch has been applied:
select DRIVER_FILE_NAME
from AD_PATCH_DRIVERS
where DRIVER_FILE_NAME like '%2408149%';

Note: the SQL statements will return a listing of the respective C, D, and G
drivers of each patch. Thus, for the SQL statement in (b) above if the patch
had been applied to this instance, the results would be:

DRIVER_FILE_NAME
------------------------------
g2408149.drv
c2408149.drv
d2408149.drv

(Also note that any patches, which were applied using admrgpch, will not be
listed in the results of the above SQL statements.)


3. Here is a useful option to find details of patchsets applied to any Oracle
Applications instance, whether 10.7, 11.0, or 11i. It is called the Patchset
Comparison Utility tool (see Note 139684.1).

A UNIX shell script is used to compare the Oracle Applications' applptch.txt
file (or AD_PATCH_DRIVERS table) with the currently available patchsets. In
order to keep this script up to date, it is put out on the Oracle ftp site on a
nightly basis. Therefore, the patchset analysis is only as up to date as of the
last time this script was downloaded.

There are four sections within a typical output of this report:

a. The top of the script tells the date when the patchsets were last,
the date when the report was ran, the current Release Version from
the applptch.txt file, and the URL of a new version of the
patchsets.sh script with the latest patchset data.
b. The second section is a complete list of the applied patchsets that
match ARU.
c. The third section states the most recent patchsets for each of the
products that have not yet been applied.
d. The final section provides the base patchset listing that came
bundled in that particular Oracle Applications version.


4. A GUI for querying Patch History and File History information is available
as part of the HTML-based version of Oracle Applications Manager (OAM 11i).


RELATED DOCUMENTS
-----------------
139684.1 (Oracle Applications Current Patchset Comparison Utility)
162498.1 (Storing Applied Patch Information In The Database For Applications 11i)
162524.1 (How To Identify What Patches and Patchsets Installed in Applications 11i)
140848.1 (Where to Find the Applications Patch History File (applptch.txt))
181665.1 (Release 11i Adpatch Basics)

No comments: