This document provides methods to check if a specific patch has been applied to an Oracle E-Business Suite instance (versions 11i or R12). It outlines several approaches including using Oracle Applications Manager, SQL queries, and specific commands for R12. Additionally, it includes references for further troubleshooting and patch management guidance.
This document provides methods to check if a specific patch has been applied to an Oracle E-Business Suite instance (versions 11i or R12). It outlines several approaches including using Oracle Applications Manager, SQL queries, and specific commands for R12. Additionally, it includes references for further troubleshooting and patch management guidance.
This document provides methods to check if a specific patch has been applied to an Oracle E-Business Suite instance (versions 11i or R12). It outlines several approaches including using Oracle Applications Manager, SQL queries, and specific commands for R12. Additionally, it includes references for further troubleshooting and patch management guidance.
This document provides methods to check if a specific patch has been applied to an Oracle E-Business Suite instance (versions 11i or R12). It outlines several approaches including using Oracle Applications Manager, SQL queries, and specific commands for R12. Additionally, it includes references for further troubleshooting and patch management guidance.
11)|| RPAD(e.patch_name, 11)|| RPAD(TRUNC(c.end_date), 12)|| RPAD(b.applied_flag, 4) BUG_APPLIED FROM ad_bugs a, ad_patch_run_bugs b, ad_patch_runs c, https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=w4wkeq5sx_399&id=443761.1 1/3 2/2/22, 3:21 PM Document 443761.1 ad_patch_drivers d , ad_applied_patches e WHERE a.bug_id = b.bug_id AND b.patch_run_id = c.patch_run_id AND c.patch_driver_id = d.patch_driver_id AND d.applied_patch_id = e.applied_patch_id AND a.bug_number in ('<XXXXXX>','<YYYYYY>') ORDER BY 1 DESC;
Note: Please enter Patch number in place of <XXXXXX> and <YYYYYY>, e.g '3453499'
Method 3
In multi-node environment you are advised to use Patch Query from section "Checking the Patch Requirements on each Appl_Top" of the Note 364439.1 Tips and Queries for Troubleshooting Advanced Topologies.
Method 4
In R12.2, To check which patches were applied in each ADOP_SESSION_ID (patching cycle)
select * from ad_adop_session_patches order by end_date desc;
or
set pagesize 200;
set linesize 160; column adop_session_id format 999999999999; column bug_number format a15; column status format a15; column applied_file_system_base format a23; column patch_file_system_base format a23; column adpatch_options format a15; column node_name format a15; column end_date format a15; column clone_status format a15;
ADPATCH_OPTIONS, NODE_NAME, END_DATE, CLONE_STATUS from ad_adop_session_patches order by end_date desc;
Note: STATUS
N - Not Applied In the current node but applied in other nodes
R - Patch Application is going on. H - Patch failed in the middle. (Hard Failure) F - Patch failed in the middle but user tried to skip some failures. S - Patch Application succeeded after skipping the failed jobs. Y - Patch Application succeeded.
C - Reserved for clone and config_clone. Indicates clone completed
