We can use below query to identify Oracle Application Version.


SQL> select release_name from apps.fnd_product_groups;

RELEASE_NAME
--------------------------------------------------
12.2.6

Below are few important commands to apply weblogic patches using BSU.

Steps:

• Download the required patch from Oracle Support.
• Copy the patch to $MW_HOME/utils/bsu/cache_dir or $FMW_HOME/utils/bsu/cache_dir 
• In case cache_dir is not present, please create this directory.
• Unzip the patch in cache_dir. This will create a jar file.
• Set the environment  using below command.

    

     . ./setWLSEnv.sh



Installing  a  patch

cd $FMW_HOME/utils/bsu

./bsu.sh -install -patch_download_dir=$FMW_HOME/utils/bsu/cache_dir -patchlist=<patch_name without jar extension> -prod_dir=$FMW_HOME/wlserver_10.3 -log=patch_apply.log

Removing a patch

cd $FMW_HOME/utils/bsu

./bsu.sh -remove -patchlist=<patch_name without jar extension> -prod_dir=$FMW_HOME/wlserver_10.3


List the patches applied

cd $FMW_HOME/utils/bsu
./bsu.sh -report -bea_home=$FMW_HOME -output_file=bsu_patch_report.log

Apart from the regular patching ADOP also provides a phase known as FS Clone. 

FS clone mode can be only executed when there is no active patching cycle going on in the system.

When a fs_clone is triggered the Patch file system is incrementally synchronized with the run edition file system.

FS Clone might be needed to be executed some of the below scenarios.

• The previous Online Patching cycle was aborted.
• If we make any manual changes to the run edition file system
• FMW or  Middle-tier technology components are patched.
• After applying a big application RUP patch.
• Loss of patch edition file system or corruption.

Syntax:
adop phase=fs_clone

We can use the below tables to validate if the patch has been applied to the patch edition.


select ADOP_SESSION_ID,NODE_NAME,APPLTOP_ID,BUG_NUMBER,PATCH_TOP,DRIVER_FILE_NAME 
from AD_ADOP_SESSION_PATCHES 
where
BUG_NUMBER='&patch_number' 
and APPLIED_FILE_SYSTEM_BASE like '%fs%';

In the previous post, we have seen an overview about ADOP. Now we will try to understand Various phases of ADOP in detail.

Prepare Phase:

• Prepares the system for patching cycle.
• Creates the Database Patch Edition
• Validates system configuration
• Check & Submit Concurrent Request 'Online Patching In Progress'(ADZDPATCH)
• Prepare is run on all nodes in a mute-node configuration
• Synchronizes the Run and Patch File System
• If cleanup was not executed in previous adop cycle it will also run Cleanup.

adop phase=prepare

Apply Phase:

• Patches are applied in this phase.
• Adop internally calls adpatch to apply the patches, but we cannot run adpatch utility as standalone in R12.2 .
• Patches are applied in the Patch Edition.
• Application user are connected to RUN edition and they are not impacted by patching cycle.
• We can apply multiple patches in a patching cycle.

Syntax:
adop phase=apply

Finalize Phase:

• Ready the system for Cutover.
• Compile Invalid objects.
• If we don't run finalize, then the cutover phase will call finalize automatically before doing the actual cutover. But that will increase the downtime window for the cutover.
• Computes any DDL to be executed before the cutover.

Synatx:
adop phase=finalize

Cutover Phase:

• Switches to the patch edition of database and file system.
• In the phase, the system actually goes down.
• All application tier services are stopped and starts after the cutover.

Syntax:
adop phase=cutover

Cleanup Phase:

• Cleans up old edition and objects.
• Recovers space.

Syntax:
adop phase=cleanup








Note: ADOP utility should be executed on the primary application server. In case of the multinode environment, passwordless ssh should be enabled between the application nodes.

With R12.2 EBS, Oracle has launched online application patching feature which helps to reduce the downtime to minimal.
We will look into  ADOP features and its phases.

Key Features:
1. Online Patching utility for EBS R12.2 to apply application patches.
2. The application will be up and running during the patching cycle.
3. It can be executed in both Interactive and Non-Interactive mode.
4. Can apply multiple patches during a single patching cycle.
5. Option to abort the patch is also available.


Phases of ADOP cycle.

1. Prepare
2. Apply
3. Finalize
4. Cutover
5. Cleanup


Other Phases:
1. Abort
2. FS Clone



In Coming posts, we will discuss more on ADOP and some useful queries.

We can find the weblogic URL and port from the CONTEXT_FILE by using the below variable.

Steps:

1. Go to Application Tier
2. Set the RUN file system environment.
3. Execute

grep -i "wls_admin" $CONTEXT_FILE

<wls_admin_host oa_var="s_wls_admin_host">funoracleapps</wls_admin_host>

<wls_admin_domain oa_var="s_wls_admin_domain">com</wls_admin_domain>

<wls_admin_user oa_var="s_wls_admin_user">weblogic</wls_admin_user>

<wls_adminport oa_var="s_wls_adminport" oa_type="PORT" base="7001" step="1" range="-1" label="WLS Admin Server Port">7001</wls_adminport>


With these variable values we can create the weblogic URL for our EBS environment.

In our example the URL will be:

http://funoracleapps.com:7001/console

Login User: weblogic
Password: As per environment

We can use below query to find the OPP log for a request ID and its path.

SELECT fcpa.concurrent_request_id request_id, fcp.node_name node_name, fcp.logfile_name logfile_path
  FROM fnd_conc_pp_actions fcpa, fnd_concurrent_processes fcp
 WHERE fcpa.processor_id = fcp.concurrent_process_id
   AND fcpa.action_type = 6
   AND fcpa.concurrent_request_id = &REQUEST_ID;