One of the most important and time-consuming aspects of an Oracle Applications DBA’s job isapplying patches to the E-Business Suite. Patches may be required to resolve problems with theapplication code, to fix production issues, to install new features, or to upgrade components of the technology stack. Patching is not a simple one-step process, but rather requires carefulresearch in order to determine all of the prerequisite steps, patching steps, and post-patchingsteps required.Oracle E-Business Suite patching can be divided into two categories:
Oracle Applications patching:
This includes all patching that changesthe underlying Oracle Applications code.
Technology stack components patching:
This includes all upgradesand fixes for the Oracle Database software, JDK, Oracle Developer 6
(Oracle Formsand Reports), Developer 6
Client library files, Oracle Discoverer, JDBC, Oracle JavaServer Page (OJSP), Oracle Application Server (iAS), and iAS Client library files(Required Support Files or RSF).The focus of this chapter will be on Oracle Applications patching, and a brief overview of OracleDatabase software patching will also be provided. Patching the Applications Technology Stack willnot be covered, as this type of patching effort has numerous operating system dependencies.
There are several steps involved in patching Oracle Applications. In this section we’ll discusseach of these stages:
Preparing to patch:
Before patching, it is important to document therequirements and determine what steps and patches are needed. This section willexplain how to document and manage the overall process of applying patches, anddiscuss patch reporting, where you investigate which version, if any, of a patch iscurrently installed.
Applying a patch involves several steps, such asunbundling the patch, enabling maintenance mode, applying the patch with adpatch,and implementing manual steps. This section will discuss each of the steps involved.