adop finalize erroring out after restarting patch and skipping form compilation error

[ef_arg]

Hi Erman,

We are apliying 12.2.13 EBS RU Patch. It errored our while compiling some forms. We opened a case with oracle and they indicated to complete the adop cycle and manually recompile those on the new run file system.

We restarted current apply phase with the following command and completed successfully:

adop phase=apply patches=### wait_on_failed_job=yes restart=yes abandon=no flags=autoskip

Now next phase, adop finalize is erroring out with this error:

#############################

[PROCEDURE] [END 2024/11/01 12:19:55] Getting list of failed patches
[UNEXPECTED]The following patches failed to apply on admin node <ebsappqafe001> in online mode, session ID <19>
Patches: <34776655_ESA,34776655>
You can either resolve the failure and reapply the patches, or ignore the failure and allow processing to continue.
[WARNING] Only continue if you are sure it is safe to do so - continuing without first resolving the failure may lead to inconsistency and data loss.
To reapply the patches in the existing session, answer 'N'.
To ignore the failure and continue processing, answer 'Y'.
Do you want to continue [default: N] (Y/N)?
User's response for the prompt is set as : <n>.
Exiting out as user requested.
[PROCEDURE] [END 2024/11/01 12:19:55] Giving prompt for failed patches to user
[PROCEDURE] [START 2024/11/01 12:19:56] Unlocking sessions table

#############################

Session status in ad_adop_session_patches is "Success (Jobs Skipped)"

SQL> SELECT adop_session_id, bug_number, session_type,
       DECODE(status,'N','Applied on other nodes',
                     'R','Running',
                     'H','Failed (Hard)',
                     'F','Failed (Jobs Skipped)',
                     'S','Success (Jobs Skipped)',
                     'Y','Success',
                     'C','Clone Complete') status,
       applied_file_system_base, patch_file_system_base,
       node_name, start_date, end_date,
       ROUND((end_date - start_date) * 24*60,2) exec_time,
       adpatch_options, autoconfig_status, driver_file_name
FROM ad_adop_session_patches
WHERE session_type IN ('ADPATCH','HOTPATCH','DOWNTIME','ONLINE')
and adop_session_id=19
ORDER BY adop_session_id, start_date, end_date;

19 34776655 ONLINE Success (Jobs Skipped) /u01/app/oracle/fs2 ebsappqafe001 23-OCT-24 30-OCT-24 10031.7 Y u34776655.drv
19 34776655_ESA ONLINE Success (Jobs Skipped) /u01/app/oracle/fs2 ebsappqafe001 30-OCT-24 30-OCT-24 18.27 N u34776655.drv

And ad_adop_sessions status for session 19 is:

19 Y P N N N N F ebsappqafe001 master 194 V_20241023_1418

As always, thanks for your support.
Regards

[ErmanArslansOracleBlog]

Patch 34776655 that adop complains about tis the "ORACLE E-BUSINESS SUITE 12.2.13 RELEASE UPDATE PACK". So you ignored the failure as SR suggested and now you are getting a Warning.
That may be normal.. Check using the patches tables, ad_applied_patches and similar views to ensure the RU is applied also check the apply log and be sure you don't have nothing else other than those failed and skipped the compilations of those forms..

Example check:

select * from ad_adop_session_patches order by end_date desc;

set pagesize 200;
set linesize 160;
column adop_session_id format 999999999999;
column bug_number format a15;
column status format a15;
column applied_file_system_base format a23;
column patch_file_system_base format a23;
column adpatch_options format a15;
column node_name format a15;
column end_date format a15;
column clone_status format a15;

select ADOP_SESSION_ID, BUG_NUMBER, STATUS, APPLIED_FILE_SYSTEM_BASE, PATCH_FILE_SYSTEM_BASE, ADPATCH_OPTIONS, NODE_NAME, END_DATE, CLONE_STATUS
from ad_adop_session_patches
order by end_date desc;

The status should be S. (in your case)

Below are possible values of STATUS column:
N - Not Applied In the current node but applied in other nodes
R - Patch Application is going on.
H - Patch failed in the middle. (Hard Failure)
F - Patch failed in the middle but user tried to skip some failures.
S - Patch Application succeeded after skipping the failed jobs.
Y - Patch Application succeeded.
C - Reserved for clone and config_clone. Indicates clone completed

Still, get approval from Oracle Support because this is a big deal ( 12.2.13 RU) and if they approve, respond Y to the question that adop finalize asks.

->
To reapply the patches in the existing session, answer 'N'.
To ignore the failure and continue processing, answer 'Y'.
Do you want to continue [default: N] (Y/N)?

If the patch is really failed even after skipping those jobs, then you have to abort and reapply.. Again get Oracle Support 's redirections for this. You already have a SR open.

[ef_arg]

ErmanArslansOracleBlog wrote

Still, get approval from Oracle Support because this is a big deal ( 12.2.13 RU) and if they approve, respond Y to the question that adop finalize asks.

->
To reapply the patches in the existing session, answer 'N'.
To ignore the failure and continue processing, answer 'Y'.
Do you want to continue [default: N] (Y/N)?

If the patch is really failed even after skipping those jobs, then you have to abort and reapply.. Again get Oracle Support 's redirections for this. You already have a SR open.

The thing is that, the "Do you want to continue [default: N] (Y/N)?" question is automatically replied by adop. it is not interactive as in the old adpatch and there is no "autoskip" option for finalize phase.

Regarsd

[ErmanArslansOracleBlog]

Try adop's restart and abandon options. If they don't work for you, you may consider using the forceapply option.