Skip to main content

Creating new WLS domain ends with exit code 255

By Unknown
Cloning the instance I ran into this weird error. Was not sure what to do but after learning my lesson I dug through the error logs after seeing this in the adcfgclone log file.
START: Creating new WLS domain.
Running /u03/APPLYES/YES/fs2/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /u03/APPLYES/YES/fs2/EBSapps/comn/util/jdk64 -al /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/EBSdomain.jar -tdl /u03/APPLYES/YES/fs2/FMW_Home/user_projects/domains/EBS_domain_YES -tmw /u03/APPLYES/YES/fs2/FMW_Home -mpl /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/plan/moveplan.xml -ldl /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/tempinfo.txt
Script Executed in 1903 milliseconds, returning status 255
ERROR: Script failed, exit code 255

Dig a bit deeper into the log files
cd /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply
cat CLONE2016-01-10_04-37-11PM.log

Something is not working with a file called EBSDataSource, has something to do with permissions.
FINE : Jan 10, 2016 4:37:12 PM - [GenericPasteConfigSteps:getClusterList] Source Cluster1 = forms_cluster1 : unicast :  : 239.192.0.0 : 7001 :
FINE : Jan 10, 2016 4:37:12 PM - [GenericPasteConfigSteps:getClusterList] Source Cluster2 = oafm_cluster1 : unicast :  : 239.192.0.0 : 7001 :
FINE : Jan 10, 2016 4:37:12 PM - [GenericPasteConfigSteps:getClusterList] Source Cluster3 = oacore_cluster1 : unicast :  : 239.192.0.0 : 7001 :
INFO : Jan 10, 2016 4:37:12 PM - CLONE-23289  Paste DataSource Configuration.
FINE : Jan 10, 2016 4:37:12 PM - [FileUtil:isAFileAndNonZeroSize] The file /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/EBSDataSource has no read permission.
FINE : Jan 10, 2016 4:37:12 PM - CLONE-22264   Time taken to restore sourceid "J2EECOMPONENT@EBS_domain_PROD" is "1,049" milliseconds.
FINE : Jan 10, 2016 4:37:12 PM - [ApplyCloneRequest:applyArchive] One cloner object was not executed properly, so rest were not executed.
INFO : Jan 10, 2016 4:37:12 PM - CLONE-21037   Time taken to restore all cloners from archive was "1" seconds.
INFO : Jan 10, 2016 4:37:12 PM - CLONE-21006   Total time taken by T2P process was 1 seconds.

Found the error, how it happened I have no idea. But found the solution in MOS
ll /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/EBSDataSource
-rw------- 1 root root 44 Jan 10  2016 /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/EBSDataSource

Solution

Remove the files before the clone
rm -rf /u03/APPLYES/YES/fs1
rm -rf /u03/APPLYES/YES/fs2/FMW_Home
rm -rf /u03/APPLYES/YES/fs2/inst

Remove inventory directory
echo /etc/oraInst.loc
inventory_loc=/u03/APPLYES/oraInventory
inst_group=dba
rm -rf /u03/APPLYES/oraInventory

Exit the system and retry the clone
exit
su - applyes

Retry the clone from the start
cd $COMMON_TOP/clone/bin
perl adcfgclone.pl appsTier

References




Labels:

Comments

Post a Comment

Popular posts from this blog

Cancel or abort adop session

By Unknown
ADOP is in my opinion still pretty half baked. This is a critical tool that just isn't as intuitive as the old adpatch was. However we move with the times and get the hang of the new way of doing things. Along the way you might want to abort or cancel a patching cycling. With the two file systems and db editioning this can be a bit more to manage. I have learnt the hard way so you need to use the full cleanup after aborting a session. adop phase=abort adop phase=cleanup cleanup_mode=full
Post a Comment
Read more

Launching a Concurrent with Form Personalization on EBS 11i

By Unknown
There are two methods when it comes to running a concurrent from a Form Personalization in Oracle. The thing you need to do in either case is create a menu option for the form in question. This is generally done on a WHEN-NEW-FORM-INSTANCE Trigger Event. If you already have an event like this then you can add it there. I personally like to group my customizations together so there is not much overlap. Whichever catches your fancy will work. Setup the menu with the name: You now have a menu item for the launching of the concurrent program. This is where the two methods separate and you may choose which ever is more appropriate to you. Launch FNDRSRUN (Submit Request) This will use the zoom feature of Oracle Form Personalization to open the Submit Request Form, and pass the parameters to it. This involves personalization in two forms. The sending form needs to call the Form Function and pass the parameters and the Submit Request form needs to receive and process those parameters....
2 comments
Read more