Specifying delta uses the file system synchronization command specified in the $APPL_TOP_NE/ad/admin/delta_sync_drv.txt file. In the prepare phase, used to specify method of file synchronization between run and patch file.Ĭan have a value of delta or patch. Set the value to 'yes' in order to work around synchronization failures that may occur when patches that failed to apply correctly in a previous patching cycle are synchronized during the prepare phase. Most parameters can be specified with any phase: where a parameter only applies to certain phases, this is noted in brackets after the parameter name.Īdop Parameters Parameter Įnables the user to specify that any synchronization errors in the prepare phase are expected to be fixed automatically in the synchronization that takes place with subsequent patches.ĭefault value is 'no'. Some parameters override other parameters, and some have a higher order of precedence over others. Some parameters are required, while others are optional. Key characteristics include:Īll parameters must be entered in name=value pairs. Run from the command line, adop accepts many parameters. If adop detects a previously failed patching session, it will attempt to recover that session. If a patch contains no new updates to files or database objects in your system, adop takes no action.
Editions are described in more detail later. It automatically sets its environment correctly, regardless of the edition it is run from. The adop utility always runs from the run edition file system.
Runs AutoConfig to update configuration files if any template files are introduced or updated by the patchīe aware of the following important points about adop: Generates forms, reports, messages, graphics, and Java archive (JAR) filesĬompiles JSP files and invalid database objects
Reads and validate the patch driver file and reads the product driver filesĬompares version numbers of object modules from the product libraries and version numbers of the existing files against the patch filesīacks up all existing files that will be changed by the patch Uploads patch information from a prior patch session to the database (if applicable) Reads patch metadata to determine patch dependencies and requirements Whichever method you choose, adop will then perform the tasks required to apply the patch: You can either allow adop to prompt for the information required to apply a patch, or enter the information without being prompted. You use the adop (AD Online Patching) utility to apply patches to the Oracle E-Business Suite file system or database.