1.

)adpatch ,adctrl,admrgpch
2.)readme.txt
3.)patch zip (driver files)
4.)prereq, bpatchname.ldt,fpatchname.ldt
5.)worker concept,
6.)types of patches
7.)patch options
8.)ad_deferred_jobs/fnd_install_process table

Patching - To enhance or to fix particular bugs we called it as patching

Upgradation - patching(10g to 11g to 12c)

Bug fixes - patching

Types of patchings

1.)database patch - opatch - oracle patch

2.)application patch - adpatch - application database patching

Apps DBA - adpatch - there are totally 206 products

(po,ap,ar,gl,hr,bom,inv...........)
specifically product related patches what oracle will give are known mainly as one-
off patch

1.)one-off patch - bug_number - 1234567(bug/error/issue) - 1234567(patch no) - no

prereq will be ther - readme.txt file need to follow for patching
2.) mini pack - multiple bugs (1234567,234567,456789,1012345) - 234567(patch
resolves multiple bugs)
3.) Family pack - financial - (po,ap,ar,gl) - supply chain management -
(INV,BOM,WIP) , manufacturing modules - (ASCP,CSD)
4.) CPU - critical patch updates - this patches will be released in every quarter -
so totally 4 sets of patches in 4 quaters will be released.
maintenance patches or performance improvement or some
vulnerabilities...environment basis and if it suitable then only you have to apply
this type of patches

How do we know we need to apply specific patch and from where we will get this
patch request? -
Functional teams , oracle recommendation and oracle have to provide the patch

System admin -> sysdba privilege -> program name - you want to run once concurrent
program to identify any latest patches need to be applied
raise an SR - rup.sql - when you run this - it will the validation and current
version version of instance and products...
based on that oracle will suggest to apply patches or not...

Before applying the patch, what this patch will do, is this patch any problem or
harm to apply......
until and unless you apply a patch on test environment ...you can't say or confirm
what it is doing...so for that reason oracle recommends to apply patch always first
in test environemnt
to identify any issues with that patch, whether issue has been resolved with that
patch, there are some cases like to apply patch in test mode
adpatch test=y/n or adpatch apply=n

Readme.txt -
any prereq patches are there or not to apply and any post patch steps are there or
any other patch options patch maintenance are there or not this all information
will be provided in readme.txt

then we will go with patch procedure

prereq-patches
1.)follow readme.txt
2.) check whether any invalids there are not
3.) check whether that specific patch is applied or not
4.) put the env in maintenance mode by enabling

patching

5.) unzip the patch at temp or patch staging location

6.) cd patchno
7.) adpatch

post patch step

8.)whether the patch is applied successfully or not

9.)check any new invalids generated
10.)disable your maintenance mode
11.) do the sanity check by bringing up the applications and then release the
instance to users....

adpatch , adctrl , admrgpch