You use the adop (AD Online Patching) utility to apply patches to the Oracle E-Business Suite file system or database. You can either allow adop to prompt for the information required to apply a patch, or enter the information without being prompted. Whichever method you choose, adop will then perform the tasks required to apply the patch:
- Reads patch metadata to determine patch dependencies and requirements
- Uploads patch information from a prior patch session to the database (if applicable)
- Reads and validate the patch driver file and reads the product driver files
- Compares version numbers of object modules from the product libraries and version numbers of the existing files against the patch files
- Backs up all existing files that will be changed by the patch
- Copies files
- Archive files in libraries
- Relinks executables
- Generates forms, reports, messages, graphics, and Java archive (JAR) files
- Compiles JSP files and invalid database objects
- Updates database objects
- Runs AutoConfig to update configuration files if any template files are introduced or updated by the patch
- Saves patch information to the database
Be aware of the following important points about adop:
- The adop utility always runs from the run edition file system. It automatically sets its environment correctly, regardless of the edition it is run from. Editions are described in more detail later.
- If a patch contains no new updates to files or database objects in your system, adop takes no action.
- If adop detects a previously failed patching session, it will attempt to recover that session.