In Oracle EBS environment, patching play very important roles. Patch Analysis knowledge is key for any New or Experienced Oracle Apps DBA.
I am writing this post based on my experience and knowledge. Please post your comments to correct me if any thing you feel is not correct or you didn't understood.
The order to start with Patch Analysis (Sequence to apply the patch in Oracle E-Business Suites enviornment)
The best approach to start with any patch or CPU patches take the backup of your DB and file system so that you can revert back to same state in the event of any issue with patches. Normally every setup/Organization have daily backup schedule and you can fall back to last backup.
Take at least minimum backup of you configuration files in you application user home directory for important files like context .xml file, tns files,formservlet.ini,adalctl.sh,env files,Jserv config files etc
1 - RDBMS
2 - HTTP
3 - Developer 6i - Patch set (for e.g patchset 18)
3a - Bug Fixes - if any
3b - Developer (Forms , Reports and 126.96.36.199 Home or now 10g Home)
4a - IO (Interoperability)
1st Checkpoint to perform Application healthcheck to rule out any issue at this stage (by my experience recommanded way)
5 - Oracle Jinitiator
6 - JDK Upgrade - if any required
2nd Checkpoint to perform Application healthcheck to rule out any issue at this stage (by my experience recommanded way)
7 - ATG RUP patches before applying any apps patches
8 - Oracle E-Business Application Patches
3rd Checkpoint to perform Application healthcheck to rule out any issue at this stage (by my experience recommanded way)
PS: It is very important to carefully read patch readme's and metalink note to cover all pre-req patches and manual steps. Before applying any patch it is very important to apply the pre-req patches.
Needs inputs from all my blog readers to improve the blogs. I am writing this blog whenever i am getting time from family and work. I will try to update this blog on frequent basis with my all efforts.