fs_clone not started on slave node

[applprd@apdbablog01 ~]$ adop -status -detail
Enter the APPS password:
==============================================================
ADOP (C.Delta.6)
Session Id: 53
Command: status
Output: /u11/home/ebsprd/fs_ne/EBSapps/log/status_20151126_001321/adzdshowstatus.out
===============================================================
Node Name       Node Type  Phase           Status          Started              Finished             Elapsed
--------------- ---------- --------------- --------------- -------------------- -------------------- ------------
apdbablog01    master     FS_CLONE        COMPLETED       2015/11/25 05:48:47  2015/11/25 11:59:42  6:10:55
apdbablog02    slave      CONFIG_CLONE    NOT STARTED     2015/11/25 05:48:47
apdbablog03    slave      CONFIG_CLONE    NOT STARTED     2015/11/25 05:48:47
apdbablog04    slave      CONFIG_CLONE    NOT STARTED     2015/11/25 05:48:47
apdbablog05    slave      CONFIG_CLONE    COMPLETED       2015/11/25 05:48:47  2015/11/26 12:06:10  6:17:23
apdbablog06    slave      CONFIG_CLONE    COMPLETED       2015/11/25 05:48:48  2015/11/26 12:06:17  6:17:29
File System Synchronization Type: Full
Generating full ADOP Status Report at location: /u11/home/ebsprd/fs_ne/EBSapps/log/status_20151126_001321/adzdshowstatus.out
adop exiting with status = 0 (Success)
[applprd@apdbablog01 ~]$
Solution:
FS_CLONE completed successfully on all nodes.
It was failing on node 4 as the context file value “s_web_admin_status” was set to enabled.
Now the value is set to disabled and FS_CLONE completed successfully.