12.2.4 E-Business Suite Upgrade Per Note 1983050.1 Fails During fs_clone Synchronize Step With Error'SEVERE :DATE / TIME - ERROR - CLONE-20362 Connection to AdminServer failed.' (Doc ID 2096313.1)

SYMPTOMS
12.2.4 E-Business Applications DBA, Upgrade related issues
Testing an upgrade from 12.2.4 to 12.2.5 using Note 1983050.1.
After applying the 12.2.5 patch and trying synchronize the file systems using fs_clone, it fails during the wls home clone with the following error:
WLS clone log:
SEVERE : Jan 11, 2016 9:57:38 AM - ERROR - CLONE-20362 Connection to AdminServer failed.
SEVERE : Jan 11, 2016 9:57:38 AM - CAUSE - CLONE-20362 AdminServer start failed. Make sure that AdminServer parameters specified in the move plan are correct.
SEVERE : Jan 11, 2016 9:57:38 AM - ACTION - CLONE-20362 Check the AdminServer logs.
oracle.as.t2p.exceptions.FMWT2PPasteConfigException: PasteConfig failed. Make sure that the move plan and the values specified in moveplan are correct
The adminserver log show the following:
Caused By: oracle.security.jps.service.igf.IGFException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: oracle.xml.parser.v2.XMLParseException; lineNumber: 0; columnNumber: 0; Element 'socketOptions' not expected.
  at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.pushLdapNamesTolibOvd(OvdIGFServiceProvider.java:321)
  at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.prepareDataPush2libOvd(OvdIGFServiceProvider.java:370)
  at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:339)
CAUSE
The above errors occur when the RUN and PATCH file systems are not in sync.
SOLUTION
To resolve the issue, test the following steps in a development instance and migrate accordingly:
1. Ensure no services or processes are running on the PATCH file system.
2. Ensure the Weblogic Admin Server and Node Manager are running on the Run File system.
   Use the following commands to check the status:
    $ adadminsrvctl.sh status
    $ adnodemgrctl.sh status
3. Run the below commands in order listed:
    $ adop phase=abort
    $ adop phase=cleanup cleanup_mode=full
    $ adop phase=fs_clone force=yes
4. Retest the synchronize process for the file systems using fs_clone to confirm the issue is resolved.