This issue with SSH timeout.
START: Creating FMW Home.
Running
/erp_appl/apps/fs2/EBSapps/comn/clone/FMW/pasteBinary.sh -javaHome
/erp_appl/apps/fs1/EBSapps/comn/util/jdk -al
/erp_appl/apps/fs2/EBSapps/comn/clone/FMW/FMW_Home.jar -tl /erp_appl/apps/fs1/FMW_Home
-invPtrLoc /var/opt/oracle/oraInst.loc -ldl
/erp_appl/apps/fs2/inst/apps/TEST_erpappsserver1/admin/log/clone/patch/fmwT2PApply
-silent true -debug true -executeSysPrereqs false
Script Executed in 7200410 milliseconds, returning status -1
ERROR: Script timed out.
Below are the values set by customer:
ClientAliveInterval 900
ClientAliveCountMax 0
Definition for these parameters:
ClientAliveInterval - The interval value indicates in seconds the server sends a alive message to client after no data has been received from client
ClientAliveCountMax - indicates the max times the alive message should be sent
With these settings SSH connection will be closed after 900 seconds which is 15 minutes. This is very low and needs to be increased as there is every chance that FS_CLONE might take more time. Also, since ClientAliveCountMax is set to ZERO, there will no live message sent at all.
Below are the suggested values to fix the time out issue:
ClientAliveInterval 120
ClientAliveCountMax 720
This will make the server send the clients a “null packet” every 120 seconds and not disconnect them until the client have been inactive for 720 intervals (120 seconds * 720 = 86400 seconds = 24 hours).