idbasolutions

Following is a sample of where a large patch had failed and the fix is to apply another patch.

Reference: Metalink Note: 175485.1

Disclaimer: Apply to a TEST environment first. Use on production systems is at DBAs own risk.

In the following example, patch 3480000 was being applied and had run for over 16 hours before it failed. Metalink recommends
applying patch 4656019 to fix the problem encountered by patch 3480000.
Aborting 3480000 and applying 4656019 would cause me to lose 16 hours of work on 3480000 and would force me to re-start applying 3480000 from the begening causeing me to lose 16 hours of work applying 3480000.

The following will outline steps involved in saving adpatch work done on 3480000 then apply patch 4656019 then restore adpatch of 3480000 so I would not lose the 16 hours of application time from 3480000. This is on TRAIN instance.
Using the adctrl utility, shutdown the workers.
a. adctrl
b. Select option 3 “Tell worker to shutdown/quit”

Connect to TRAIN as applsys:
sqlplus applsys/<password>

create table FND_INSTALL_PROCESSES_3480000
as select * from FND_INSTALL_PROCESSES;
create table AD_DEFERRED_JOBS_3480000
as select * from AD_DEFERRED_JOBS;

From OS:
cd $APPL_TOP/admin/TRAIN
mv restart restart_3480000

mkdir restart
Connect to TRAIN as applsys:
sqlplus applsys/<password>

drop table FND_INSTALL_PROCESSES;
drop table AD_DEFERRED_JOBS;
Apply the new patch 4656019.
Once patch 4656019 completed.
cd $APPL_TOP/admin/TRAIN
mv restart restart_4656019
mv restart_3480000 restart
Connect to TRAIN as applsys:
sqlplus applsys/<password>

create table FND_INSTALL_PROCESSES
as select * from FND_INSTALL_PROCESSES_3480000;
create table AD_DEFERRED_JOBS
as select * from AD_DEFERRED_JOBS_3480000;
connect apps/train

create synonym AD_DEFERRED_JOBS for APPLSYS.AD_DEFERRED_JOBS;
create synonym FND_INSTALL_PROCESSES FOR APPLSYS.FND_INSTALL_PROCESSES;

Now reStart adpatch for 3480000, it will resume where it stopped previously.