FS clone cannot be called while a patching cycle is active

1 shutdown all apps services on RUN and PATCH file systems.
. <EBS_ROOT>/EBSapps.env run
cd $INST_TOP/admin/scripts
adstpall.sh apps/apps
. <EBS_ROOT>/EBSapps.env patch
cd $INST_TOP/admin/scripts
adstpall.sh apps/apps
2. On the RUN file system, start up admin server via the following command
. <EBS_ROOT>/EBSapps.env run
cd $INST_TOP/admin/scripts
$ adadminsrvctl.sh start
Ensure the Weblogic Admin Server and Node Manager are running on the Run File
system. You can run the following commands to check the status:
$ adadminsrvctl.sh status
$ adnodemgrctl.sh status
3. Run these in order:
$ adop phase=abort
$ adop phase=cleanup cleanup_mode=full
$ adop phase=fs_clone force=yes
4. If any adop phase fails, please generate a new diagnostic info tar.
Diagnostic script to collect information required for AD/TXK 12.2.x bugs ( Doc ID 1901242.1 ).
Hopefully, this one will collect the many queries needed.