The error in adop log file (adop_date_time.log) was:
Applying patch 18998116.
[UNEXPECTED]Error occurred executing "adpatch abandon=yes restart=no workers=88 wait_on_failed_job=yes options=hotpatch,forceapply console=no interactive=no defaultsfile=<directory>/appl/admin/DBOFINE1_BALANCE/adalldefaults.txt patchtop=<patch_top>18998116 driver=u18998116.drv logfile=u18998116.log"
[UNEXPECTED]Refer to the log files for more information.
[UNEXPECTED]Apply phase has failed.
and in the u*****.log was:
Do you wish to apply this patch now [No] ? No *
instead of following in the environment where the patch run successfully:
Do you wish to apply this patch now [Yes] ? Yes *
We solved the problem with modying the file adalldefaults.txt (in $APPL_TOP/admin/$TWO_TASK).
This file was providing default answer "No" during patch application so
Changing the adalldefaults.txt default value to "Yes" allowed the patching to continue instead of exit/fail:
# Do you wish to continue with applying this patch even if there are
621 # translated version of the same patch pending to be applied ?
624 ## Start of Defaults Record
630 Yes 631 %%END_OF_VALUE%%
632 ## End of Defaults Record
This file is generated with autoconfig. How could it be different from an environment to another one ?
There are adalldefaults.txt and/or autoconfig related bug fixes in some patches..
What are the difference between those environments that you are talking about?
There are also 2 important note on hotpatch mode
1)Note: This parameter has been superseded by the apply_mode parameter and is only retained for backward compatibility.
2)If adop is being run in hotpatch mode, your own defaults file should be located on the run file system, under $APPL_TOP/admin/$TWO_TASK. Otherwise, the defaults file should be in the same location, but on the patch file system.
Note: Instead of using your own defaults file, it is generally preferable to supply your own parameters via the command line or in an input file. Parameters supplied in either of these ways take precedence over parameters in the the defaults file.
Order of Parameters
If multiple different definitions are specified for a parameter, the following order of precedence is used.
Important: You should never need to edit the defaults file because you can always specify a parameter on the command line (highest precedence) or in the input file (second highest precedence).