on 10-10-2008 8:36 AM
Hi Gurus,
I am installing Ecc 6.0 on a cluster environment.
The Centarl Instance Installtion is done.
while installing Dialog Instance on Node 2 of the cluster...
I am getting error...
The instance D02 is not getting started...
After checking log dev_disp....
-
use SAPLOCALHOST=<DBCIP11> as internal hostname
***LOG Q0I=> NiIBindSocket: bind (227: Can't assign requested address) [nixxi.cpp 3172]
ERROR => NiIBindSocket: SiBind failed for hdl 3 / sock 12
(SI_EADDR_NAVAIL/227; I4; ST; 192.168.1.200:0) [nixxi.cpp 3172]
ERROR => NiIMyAddrVerify: NiIListen failed ('DBCIP11'; 192.168.1.200; rc=-16) [nixxi.cpp 7528]
ERROR => SAPLOCALHOST=<DBCIP11> [dpxxdisp.c 11818]
DP_FATAL_ERROR => DpMsAttach: incorrect value for SAPLOCALHOST
DISPATCHER EMERGENCY SHUTDOWN ***
-
Can you help me with this...
Thanks
Sagar
Hi,
The Default Profile doesnt have entry of SAPLOCALHOST.
It only has entry of SAPGLOBALHOST : which is the Virtual Hostname...
and all the folders in /usr/sap are owned by p11adm only..
I tried changing the SAPLOCALHOST on apllication Server I.e Node 2 where second dialog instance is installed....
same issue again..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sagar,
I am facing the same issue in a dialog instance installation.
Im finding the below mentioned error message in the dev_disp log file.
Please suggest.
Sat Jul 31 21:24:59 2010
WLM Tag 'BCP/DSP' successfully set for this process
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1682]
***LOG Q0K=> DpMsAttach, mscon ( SAPECCPRD) [dpxxdisp.c 12593]
use SAPLOCALHOST=<SAPECCPRD> as internal hostname
***LOG Q0I=> NiIBindSocket: bind (68: Can't assign requested address) [nixxi.cpp 3239]
ERROR => NiIBindSocket: SiBind failed for hdl 3 / sock 11
(SI_EADDR_NAVAIL/68; I4; ST; 192.190.24.12:0) [nixxi.cpp 3239]
ERROR => NiIMyAddrVerify: NiIListen failed ('SAPECCPRD'; 192.190.24.12; rc=-16) [nixxi.cpp 7746]
ERROR => SAPLOCALHOST=<SAPECCPRD> [dpxxdisp.c 12658]
DP_FATAL_ERROR => DpMsAttach: incorrect value for SAPLOCALHOST
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
Thank you
Regards,
Vineeth
Hi Sunil,
The SAPLOCALHOST was refering to virtual Host name.
I changed it to hostname of Second node...
And it worked...The second dialog instance started from Node 2.
But it is not starting from Virtual Host name.
it gives error
"touch: /usr/sap/P11/D02/work/dev_tp cannot create"
And after checking the startsap_D02 log ... it says....
-
Called command: /usr/sap/P11/SYS/exe/run/startsap D02
Starting SAP Instance D02
-
Instance Service on host bancopd1 started
Unable to change to Directory /usr/sap/P11/D02/work
(29372) Exiting with Return-Code -102. (Change Directory failed)
Startup of Instance failed
-
I dont understand ...how is it that the Dialog Instance started on Node 2, but not on Cluster Virtual Host...
Do Reply...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Have you changed the SAPLOCALHOST in DEFAULT.PFL cause it is needed there for the Central Instance. If so you will need to reset it back.
Try setting the SAPLOCALHOST within the Instance profile of Application Instance, I guess that should do it.
Regarding the problem with accessing the directory, please make sure that the directories are owned by p11adm, It doesn't look like that now. /usr/sap and all directories under it need to be owned by p11adm.
Thanks and Best Regards,
Sunil.
Hi Sagar,
Your SAPLOCALHOST variable seem to be pointing to the virtual hostname (i guess). It should be the physical hostname of Node 2. Can you confirm if that is the case.
DP_FATAL_ERROR => DpMsAttach: incorrect value for SAPLOCALHOST
Also you could run 'R3trans -d' as p11adm and paste the output of trans.log into the message for someone in the forum to help you.
Thanks and Best Regards,
Sunil.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.