13-26 Oracle Application Management Pack for Oracle E-Business Suite Guide
• Schedule
• Indefinite Grace Period
For the Prepare phase, specify Pause After Prepare. This option will stop execution
of the deployment procedure after the adop prepare phase has been run. A user
would then need to manually acknowledge the pause for Enterprise Manager to
continue with the next step.
For the Apply phase, specify Pause After Apply. This option will stop execution of
the deployment procedure after the adop apply phase has been run. A user would
then need to manually acknowledge the pause for Enterprise Manager to continue.
For the Apply phase, specify Actualize All Objects. This option will run the adop
actualize_all phase. If this option is chosen then the cleanup mode is switched to
"full".
For the Apply phase, specify Hotpatch. This option will disable all other adop
phases and run adop in hotpatch mode. This option is not supported unless
specifically stated in the patch readme. A warning message is also displayed in
Patch Manager when this option is chosen.
For the Finalize phase, specify the Finalize Mode. This option runs adop finalize
phase in either Quick or Full mode.
Specify Pause After Finalize. This option stops the execution of the deployment
procedure after the adop finalize phase has been run. A user would then need to
manually acknowledge the pause for Enterprise Manager to continue.
Cutover Deployment Procedure
Specify the Cutover Options.
The Cutover deployment procedure has three options for execution:
• Start Immediately
• Schedule
• No Cutover
It can start immediately or be scheduled as above. In this case an immediate start
means immediately after the "apply" deployment procedure executes. If a user
schedules this deployment procedure and the apply deployment procedure is still
running after the schedule date the apply deployment procedure will fail when it
attempts to submit cutover. The cutover deployment procedure can also be skipped
entirely with the "No Cutover" option. "No Cutover" may be useful on a
development environment where ten developers are patching a single target and
they only want to bounce the instance at midnight. Another example may be when
a prerequisite patch was missed. In this situation a user could do a patch run
Comentários a estes Manuais