patching fusion applications through adpatch

adpatch In fusion applications

we can user fapmgr.sh or adpatch or opatch to patching the artifacts of the fusion applications

       Oracle Fusion Applications AutoPatch is used to apply patches that contain fixes or updates to applications database artifacts..

The database artifacts which supported by the ad patch are 

[1]Applications Seed Data (XML,XLF files)
[2]Applications Database schema changes (SXML files)
[3]PL/SQL objects (PDQ, PCB files)
[4]SQL scripts

In fusion applications adpatch is located in two locations 

[1]$ATGPF_HOME/lcm/ad/bin/adpatch.sh [Oracle Fusion Middleware Extensions for Applications (Applications Core)]

[2]$AD_TOP/bin/adpatch.sh [Oracle Fusion Applications Patch Manager]

[1]ATGPF_HOME  adpatch will be located  under your base directory /basedir/products/fusionapps/atgpf/lcm/ad/bin before applying the auto patch we need to conform what ad patch we need to user

[2]AD_TOP  adpatch will be located under the/basedir/products/fusionapps/applications/lcm/ad

Using ATGPF adpatch

Step 1 

adpatch cn be applied in interactive mode and non interactive mode .. to start the adpatch we need to navigate to the $ATGPF_HOME/lcm/ad/bin/ and run the adpatch.sh or you can apply in non- interactive  mode

 To apply adpatch in non interactive Mode

  $ATGPF_HOME/lcm/ad/bin/adpatch.sh \
  patchtop=<location of the patch directory where the patch is stored > \
  driver=<patch driver> \
  interactive=No \

  workers=<no of workers assigned for patching>
  defaultsfile=$ATGPF_HOME/admin/TWO_TASK/defaults.txt \
  logfile=adpatch_<patch_number>.log wait_on_failed_job=yes

Legends

defaultsfile=The file which will be created automatically during the provisioning of the fusion applications and have the information about the particular environment.The file will be located at

$ATGPF_HOME/admin/<database_sid>/defaults.txt

To apply adpatch in interactive mode

start the adpatch from the patch directory and 

[oracle@fah 14794856]$ /u01/oracle/fa/products/fusionapps/atgpf/lcm/ad/bin/adpatch.sh

Your default directory is '/u01/oracle/fa/products/fusionapps/atgpf'.

Is this the correct APPL_TOP [Yes] ? yes 

Provide the appl_top for the atgpf_home .. hit yes to go with the default

Filename [adpatch.log] : 14794856.log     

provide the log file for the adpatch the default location of the logfile will be $ATGPF_HOME/admin/FUSION/log/

*.log = It is the main log file which contains all the details of the particular patch

*.lgi  = This file contains informational messages from your AutoPatch session

Please enter the batchsize [1000] :              --[hit enter to go with default batch size]

In your ORACLE database '<oracle_sid>'
using ORACLE executables in '/u01/oracle/fa/products/dbclient'.
Is this the correct database [Yes] ? --Check the correct database and hit yes

The default directory is [/u01/oracle/fa/Patch/14794856] :

The default directory where the Patch had been unzipped we need to specify until the patch number

Please enter the name of your AutoPatch driver file :  

Enter the driver name starting with u<patch_number>.drv wirh will be located under the patch directory

Two table are created during the patch process 

[1]AD_UTIL_PARAMS 

[2]FND_INSTALL_PROCESS 

Fnd_install_process the table which holds the patch session details which is created during the patch process if  any failed session of the patching is pending then it asks about the dropping the  previous FND_INSTALL_PROCESSES Table.. The table is created during the patch process and then droped after completing the patching session successful

Creating FND_INSTALL_PROCESSES table...
The table FND_INSTALL_PROCESSES created by AD Administration already exists.If you are sure you do not want to keep theinformation from the failed
AD Administration session,you may drop FND_INSTALL_PROCESSES table and
continue with AutoPatch.If you choose not to drop FND_INSTALL_PROCESSES table, AutoPatch cannot continue successfully.
Drop FND_INSTALL_PROCESSES table [No] ? 

If you are continuing from the failed patch session then  drop the Previous Fnd_install_process table and create the new table

Creating the AD_UTIL_PARAMS table...
Table AD_UTIL_PARAMS already exists, so dropping the table and recreating it.

SQL> desc AD_UTIL_PARAMS;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 WORKER_ID                                 NOT NULL NUMBER
 UTILITY_NAME                              NOT NULL VARCHAR2(100)
 TASK                                      NOT NULL VARCHAR2(30)
 STATUS                                    NOT NULL VARCHAR2(100)
 ARGUMENTS                                 NOT NULL VARCHAR2(2000)
 UTILITY_STATUS                            NOT NULL NUMBER
 SYMBOLIC_ARGUMENTS                        NOT NULL VARCHAR2(2560)

Ad_util_params is used to store the worker status while patch is in progress and once the patch is completed it will be purged ..when patch start the Process  it will drop the previous Ad_util_params and the recreate the table...
At the end of the patch process it will purge the ad_util_param table..

Timing report 
Timing report is generate with the execution time for each worker and all the actions of the script the timing report will be  located at the $ATGPF_HOME/admin/FUSION/log
 Jobdependencies
This file lists the jobs to be run After each job,
 this file contains the list of jobs which should run before starting the job's the dependencies of the  job's is listed in this file ..
jobdependencies.txt will  be located at $ATGPF_HOME/admin/FUSION/log

Incompatible Patch
when we try to apply the patch in the wrong oracle home it gives the message in the log file and the ad patch will fail with the below error massage..

[2012-11-22T17:06:39.956+04:00] [apps] [ERROR] [] [AutoPatch] [[Error: Incompatible Patch.Cannot apply ATGPF patch on FA_ORACLE_HOME]]