adop errors at fsclone Stage.
Error :
1. Error occurred while executing <perl /sid/applmgr/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl
2. Error occurred while CONFIG_CLONE Patch File System from Run File System using command
Check the adop logfile for errors, and also verify the errors in fsclone logfiles
location : /sid/applmgr/fs_ne/EBSapps/log/adop/<adop session id>/prepare_20140110_003210/ohs1/TXK_SYNC_migrate_Fri_Jan_10_00_40_18_2014
Solutions for different issues.
Error 1: (/sid/applmgr/fs_ne/EBSapps/log/adop/<adop session id>/adop_20140110_003210.log)
Running [filesystem]/fs1/EBSapps/comn/clone/FMW/pasteBinary.sh -javaHome [filesystem]/fs1/EBSapps/comn/clone/FMW/t2pjdk -al [filesystem]/fs1/EBSapps/comn/clone/FMW/FMW_Home.jar -tl [filesystem]/fs2/FMW_Home -invPtrLoc /etc/oraInst.loc -ldl [filesystem]/fs1/EBSapps/comn/clone/FMW/logs -silent true -executeSysPrereqs false
Script Executed in 7200015 milliseconds, returning status -1
Script timed out.
Solution
1. Open a new terminal.
2. Execute :
export TIMEDPROCESS_TIMEOUT=-1
export CONFIG_JVM_ARGS="-Xms1024m -Xmx2048m"
3. Execute :
adop phase=fs_clone
Error 2: (/sid/R122UPGR/fs1/EBSapps/comn/clone/FMW/logs)
FSCloneStageAppsTier_<datestamp>.log, the following error will be seen:
/d01/R122UPGR/fs1/FMW_Home/oracle_common/bin/copyBinary.sh -javaHome /d01/R122UPGR/fs1/EBSapps/comn/clone/FMW/t2pjdk -al /d01/R122UPGR/fs1/EBSapps/comn/clone/FMW/FMW_Home.jar -smw /d01/R122UPGR/fs1/FMW_Home -ldl /d01/R122UPGR/fs1/EBSapps/comn/clone/FMW/logs -invPtrLoc /etc/oraInst.loc -silent true
Script Executed in 28420 milliseconds, returning status 255
Script failed, exit code 255
In: /d01/R122UPGR/fs1/EBSapps/comn/clone/FMW/logs the following error is seen:
SEVERE : Dec 4, 2013 6:17:41 PM - ERROR - CLONE-20275 Insufficient space to create /tmp/CLONINGCLIENT3005869153400434600
Solution
Create space in /tmp or assign more disk storage to /tmp.
OR
assign the diffrent mountpoint as temp directory
export T2P_JAVA_OPTIONS="-Djava.io.tmpdir=/<sid>/applmgr/temp"
Error 3 (/sid/applmgr/fs_ne/EBSapps/log/adop/<adop session id>/prepare_20140110_003210/ohs1/TXK_SYNC_migrate_Fri_Jan_10_00_40_18_2014/wlsTechStack_FSCloneStageAppsTier_01100041.log)
Edit session is enabled in domain. Current Editor = weblogic
Please activate all of your changes before proceed clone
Solution
Login to weblogic console, in home page click on Release configuration button and rerun the adop preprae phase
Error 4 (/sid/applmgr/fs_ne/EBSapps/log/adop/<adop session id>/adop_20140110_003210.log)
adop=prepare encountering [ERROR] Error: While executing on all other nodes
Solution
Since the all nodes are not currently implemented the issue is cause by this autoconfig variable setting.
<shared_file_system oa_var="s_shared_file_system">false </shared_file_system>
It seems your half way to enabling another app node hence this setting
Since there is no extra app node registered.
What happens is that adop then looks for another app node and cannot find the node and it fails .
Please change the setting to false, run autoconfig, and re-test adop prepare
Issue should be resolved
Error :
1. Error occurred while executing <perl /sid/applmgr/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl
2. Error occurred while CONFIG_CLONE Patch File System from Run File System using command
Check the adop logfile for errors, and also verify the errors in fsclone logfiles
location : /sid/applmgr/fs_ne/EBSapps/log/adop/<adop session id>/prepare_20140110_003210/ohs1/TXK_SYNC_migrate_Fri_Jan_10_00_40_18_2014
Solutions for different issues.
Error 1: (/sid/applmgr/fs_ne/EBSapps/log/adop/<adop session id>/adop_20140110_003210.log)
Running [filesystem]/fs1/EBSapps/comn/clone/FMW/pasteBinary.sh -javaHome [filesystem]/fs1/EBSapps/comn/clone/FMW/t2pjdk -al [filesystem]/fs1/EBSapps/comn/clone/FMW/FMW_Home.jar -tl [filesystem]/fs2/FMW_Home -invPtrLoc /etc/oraInst.loc -ldl [filesystem]/fs1/EBSapps/comn/clone/FMW/logs -silent true -executeSysPrereqs false
Script Executed in 7200015 milliseconds, returning status -1
Script timed out.
Solution
1. Open a new terminal.
2. Execute :
export TIMEDPROCESS_TIMEOUT=-1
export CONFIG_JVM_ARGS="-Xms1024m -Xmx2048m"
3. Execute :
adop phase=fs_clone
Error 2: (/sid/R122UPGR/fs1/EBSapps/comn/clone/FMW/logs)
FSCloneStageAppsTier_<datestamp>.log, the following error will be seen:
/d01/R122UPGR/fs1/FMW_Home/oracle_common/bin/copyBinary.sh -javaHome /d01/R122UPGR/fs1/EBSapps/comn/clone/FMW/t2pjdk -al /d01/R122UPGR/fs1/EBSapps/comn/clone/FMW/FMW_Home.jar -smw /d01/R122UPGR/fs1/FMW_Home -ldl /d01/R122UPGR/fs1/EBSapps/comn/clone/FMW/logs -invPtrLoc /etc/oraInst.loc -silent true
Script Executed in 28420 milliseconds, returning status 255
Script failed, exit code 255
In: /d01/R122UPGR/fs1/EBSapps/comn/clone/FMW/logs the following error is seen:
SEVERE : Dec 4, 2013 6:17:41 PM - ERROR - CLONE-20275 Insufficient space to create /tmp/CLONINGCLIENT3005869153400434600
Solution
Create space in /tmp or assign more disk storage to /tmp.
OR
assign the diffrent mountpoint as temp directory
export T2P_JAVA_OPTIONS="-Djava.io.tmpdir=/<sid>/applmgr/temp"
Error 3 (/sid/applmgr/fs_ne/EBSapps/log/adop/<adop session id>/prepare_20140110_003210/ohs1/TXK_SYNC_migrate_Fri_Jan_10_00_40_18_2014/wlsTechStack_FSCloneStageAppsTier_01100041.log)
Edit session is enabled in domain. Current Editor = weblogic
Please activate all of your changes before proceed clone
Solution
Login to weblogic console, in home page click on Release configuration button and rerun the adop preprae phase
Error 4 (/sid/applmgr/fs_ne/EBSapps/log/adop/<adop session id>/adop_20140110_003210.log)
adop=prepare encountering [ERROR] Error: While executing on all other nodes
Solution
Since the all nodes are not currently implemented the issue is cause by this autoconfig variable setting.
<shared_file_system oa_var="s_shared_file_system">false </shared_file_system>
It seems your half way to enabling another app node hence this setting
Since there is no extra app node registered.
What happens is that adop then looks for another app node and cannot find the node and it fails .
Please change the setting to false, run autoconfig, and re-test adop prepare
Issue should be resolved
When i run adop phase=fs_clone
ReplyDeletegot an error msg below
ERROE: managed servers are not in sync between file system context and db context
any solution ply..?
Easily, the article is actually the best topic on this registry related issue. I fit in with your conclusions and will eagerly look forward to your next updates. Application
ReplyDeleteActually I read it yesterday but I had some thoughts about it and today I wanted to read it again because it is very well written. Application
ReplyDelete