Why is ADOP Status Still Showing "ACTIVE" if the Patch Application in "adop phase=apply hotpatch=yes" Completed Successfully?

 

Ref: Oracle support - (Doc ID 1928798.1)

When the patch is applied with adop hotpatch=yes mode, there are no Online Patching cycle started yet -- all is on the RUN filesystem --
adop commands status indicates what potential next adop command could be run:
NOT STARTED: both adop finalize and cleanup can be run after a apply in hotpatch mode
NOT APPLICABLE: since there were no online patching cycle prepare was skipped over hence there is no point in referring to the prepare status; and cutover is not possible after hotpatch on run fs

Hence prepare and cutover status are not applicable in regards to the last adop hotpatch active status, while finalize and cleanup could be called. 
Note that prepare can also be called to start a new patching lifecycle;
Prepare is in NOT APPLICABLE status in relation to the last hotpatch apply that is still ACTIVE until a new adop online patching cycle is started where prepare will become ACTIVE and apply will turn to NOT STARTED at that time

Example:
When one applies in hotpatch mode the APPLY phase will remain active until such time as run a PREPARE during the next patching cycle.
The APPLY phase is active because you can potentially run another hotpatch.
Once one apples a hotpatch, there are no further actions required.

When needing to apply a new patch -- this time in Online Patching mode -- run the adop phase=prepare command.
At that time, adop config change detector will find that the RUN filesystem has had patches applied in hotpatch mode and will sync the PATCH filesystem as part of the prepare phase.