on 06-29-2007 11:04 AM
Hi friends
I have a Central Instance which is on UNIX and one application server again on UNIX. Now we want to add one more application server which is a Windows based server.
I'm refering to SAP note 592747, wherein it states " release the directory /usr/SAP as SAPMNT under UNIX"
Can some one help in on this part.
Regards
Alfred
This works and is supported.
you need to make sure, your central instance (on Unix) has a directory, which will be mounted under \usr\sap\<SID>\exe to copy over the kernel files automatically, so you need to update only on one box.
We had some time ago also a mixed environment with Linux IA64 as the Central Instance, and Linux_32 and Linux_x86_64 application servers. I solved that the following way:
on the CI I created two additional directories:
/usr/sap/<SID>/exe (for Linux IA64)
/usr/sap/<SID>/exe32 (for Linux_32)
/usr/sap/<SID>/exe64 (for Linux_x86_64)
and I mounted those on the respective application servers under /usr/sap/<SID>/exe. This worked like a charm.
To get your windows boxes connected to the Unix box, you need either a CIF server (like "samba", which is available for all kinds of platforms for free) or an NFS client on the Windows side (such as SFU from Microsoft, also free).
Get back to me if you have more questions.
--
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Markus
I've configured the samba server, however while running the sapinst for the ABAP Dialog instance I get the following error message
My CI+DB is on HPUX and my application server is on Windows.
Error Message
-
ERROR 2007-12-13 20:38:15
MOS-01105 Processing of one or more file system node operations of table Content of table: t_SAPComponent_Filesystem_Action_SHARED with condition WHERE WapsSystemName='EPM' AND WapsInstanceName='D06' AND WapsInstanceHost='miapp2' AND OpMode NOT IN('CHECKFREESPACE', 'CHECKIF') Row[0] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/prfclog" FollowLinks="TRUE" NodeName="D:\usr\sap/prfclog" NodeType="DIRECTORY" OpMode="CREATE" Row[1] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/EPM" FollowLinks="TRUE" NodeName="D:\usr\sap/EPM" NodeType="DIRECTORY" OpMode="CREATE" Row[2] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/EPM/D06" FollowLinks="TRUE" NodeName="D:\usr\sap/EPM/D06" NodeType="DIRECTORY" OpMode="CREATE" Row[3] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/EPM/D06/data" FollowLinks="TRUE" NodeName="D:\usr\sap/EPM/D06/data" NodeType="DIRECTORY" OpMode="CREATE" Row[4] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/EPM/D06/data/cache" FollowLinks="TRUE" NodeName="D:\usr\sap/EPM/D06/data/cache" NodeType="DIRECTORY" OpMode="CREATE" Row[5] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/EPM/D06/exe" FollowLinks="TRUE" NodeName="D:\usr\sap/EPM/D06/exe" NodeType="DIRECTORY" OpMode="CREATE" Row[6] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/EPM/D06/log" FollowLinks="TRUE" NodeName="D:\usr\sap/EPM/D06/log" NodeType="DIRECTORY" OpMode="CREATE" Row[7] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/EPM/D06/sec" FollowLinks="TRUE" NodeName="D:\usr\sap/EPM/D06/sec" NodeType="DIRECTORY" OpMode="CREATE" Row[8] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/EPM/D06/work" FollowLinks="TRUE" NodeName="D:\usr\sap/EPM/D06/work" NodeType="DIRECTORY" OpMode="CREATE" Row[9] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="D:\usr\sap/tmp" FollowLinks="TRUE" NodeName="D:\usr\sap/tmp" NodeType="DIRECTORY" OpMode="CREATE" Row[10] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans" NodeType="DIRECTORY" OpMode="CREATE" Row[11] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/tmp" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/tmp" NodeType="DIRECTORY" OpMode="CREATE" Row[12] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/EPS" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/EPS" NodeType="DIRECTORY" OpMode="CREATE" Row[13] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/EPS/in" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/EPS/in" NodeType="DIRECTORY" OpMode="CREATE" Row[14] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/EPS/out" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/EPS/out" NodeType="DIRECTORY" OpMode="CREATE" Row[15] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/EPS/log" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/EPS/log" NodeType="DIRECTORY" OpMode="CREATE" Row[16] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/bin" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/bin" NodeType="DIRECTORY" OpMode="CREATE" Row[17] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/buffer" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/buffer" NodeType="DIRECTORY" OpMode="CREATE" Row[18] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/cofiles" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/cofiles" NodeType="DIRECTORY" OpMode="CREATE" Row[19] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/data" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/data" NodeType="DIRECTORY" OpMode="CREATE" Row[20] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/etc" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/etc" NodeType="DIRECTORY" OpMode="CREATE" Row[21] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/log" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/log" NodeType="DIRECTORY" OpMode="CREATE" Row[22] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="
eflmi\sapmnt\trans/sapnames" FollowLinks="TRUE" NodeName="
eflmi\sapmnt\trans/sapnames" NodeType="DIRECTORY" OpMode="CREATE" Row[23] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="WAPS_COPY_F:/Soft/master\IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE_D:\usr\sap\EPM\D06\exe\..\UNINSTSAP.EXE" NodeName="F:/Soft/master\IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE" NodeTarget="D:\usr\sap\EPM\D06\exe\..\UNINSTSAP.EXE" OpMode="COPY" Row[24] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="WAPS_COPY_
eflmi\sapmnt\EPM\SYS\exe\nuc\NtI386/SAPSTARTSRV.EXE_D:\usr\sap\EPM\D06\exe/SAPSTARTSRV.EXE" NodeName="
eflmi\sapmnt\EPM\SYS\exe\nuc\NtI386/SAPSTARTSRV.EXE" NodeTarget="D:\usr\sap\EPM\D06\exe/SAPSTARTSRV.EXE" OpMode="COPY" Row[25] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="WAPS_COPY_
eflmi\sapmnt\EPM\SYS\exe\nuc\NtI386/SAPOSCOL.EXE_D:\usr\sap\EPM\D06\exe/SAPOSCOL.EXE" NodeName="
eflmi\sapmnt\EPM\SYS\exe\nuc\NtI386/SAPOSCOL.EXE" NodeTarget="D:\usr\sap\EPM\D06\exe/SAPOSCOL.EXE" OpMode="COPY" Row[26] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="WAPS_COPY_
eflmi\sapmnt\EPM\SYS\exe\nuc\NtI386/SAPEVENTS.DLL_D:\usr\sap\EPM\D06\exe/SAPEVENTS.DLL" NodeName="
eflmi\sapmnt\EPM\SYS\exe\nuc\NtI386/SAPEVENTS.DLL" NodeTarget="D:\usr\sap\EPM\D06\exe/SAPEVENTS.DLL" OpMode="COPY" Row[27] WapsSystemName="EPM" WapsInstanceName="D06" WapsInstanceHost="miapp2" Key="WAPS_COPY_
eflmi\sapmnt\EPM\SYS\exe\nuc\NtI386/SAPCPE.EXE_D:\usr\sap\EPM\D06\exe/SAPCPE.EXE" NodeName="
eflmi\sapmnt\EPM\SYS\exe\nuc\NtI386/SAPCPE.EXE" NodeTarget="D:\usr\sap\EPM\D06\exe/SAPCPE.EXE" OpMode="COPY" failed.
H Markus,
For the Installation I've carried out the following steps
1. On the HPUX Server (CI+DB) I've configured Samba Server
2. I've created a share on the samba server as SAPMNT for the unix folder /usr/sap/mnt.
3. I've done the Oracle Client Installation.
4. Then I started the installation of the ABAP Dialog instance during this it gave some error message at the first step this got resolved.
5. Now I'm getting an error on the 11 of the 18 step of the ABAP Dialog instance
at the step where it create or re-register sap Services
6. The error message in the View log is as pasted below
INFO 2007-12-15 15:19:20
Output of D:\usr\sap\EPM\D06\exe/sapstartsrv.exe '-r' '-q' '-p' '
eflmi\sapmnt\EPM\SYS\profile\START_D06_miapp2' '-s' 'EPM' '-n' '06' '-U' 'miapp2\SAPServiceEPM' '-P' 'XXXXXX' '-e' 'miapp2\epmadm' is written to the logfile sapstartsrv.exe.log.
WARNING 2007-12-15 15:19:22
Execution of the command "D:\usr\sap\EPM\D06\exe/sapstartsrv.exe '-r' '-q' '-p' '
eflmi\sapmnt\EPM\SYS\profile\START_D06_miapp2' '-s' 'EPM' '-n' '06' '-U' 'miapp2\SAPServiceEPM' '-P' 'XXXXXX' '-e' 'miapp2\epmadm'" finished with return code -1. Output: Cannot open Startprofile.If the Service user cannot access the Startprofile too, the Service will not run.
ERROR 2007-12-15 15:19:22
MOS-01011 'D:\usr\sap\EPM\D06\exe/sapstartsrv.exe' returned with '-1'.
-
Some pointers on where I'm going wrong will be of great help
Thanks
Alfred
Hi Markus,
One more thing I forgot to mention is that I have also tried the following
1. From my Windows Server when I try to access the shared filesystem i.e sapmnt, I can access it and all sub-folders under them
2. When I execute the sapstartsrv.exe from the Windows server present in
x:/usr/sap/EPM/D06/exe and give the inputs as the SID, System No, the start profile path to the UNIX system (as if shows in the error log.), The windows service user SAPServiceSID or SIDadm, it says cannot start service.
3. I've copied the Start profile from the UNIX system to the Windows system, then I tried giving this path as the path of the start profile and it works, the Service starts and shows in the Windows Event Viewer.
This is just an addtion which I thought I'll mention.
Is there anything that needs to be done in the Samba settings.....?
Regards,
Alfred
Message was edited by:
Alfred DSouza
Hi Markus
I've mounted the entire directory /usr/sap as sapmnt i.e the share Samba
I'm putting the details of the samba files
CONFIG FILES
Samba config file created using SWAT
from 192.168.9.17 (192.168.9.17)
Date: 2007/12/17 16:50:57
Global parameters
[global]
server string = EFLMI-SAMBA
encrypt passwords = No
password server =
log file = /var/opt/samba/log.%m
max log size = 1000
local master = No
username = epmadm, SAPServiceEPM,root
admin users = epmadm, SAPServiceEPM, root
read list = epmadm, SAPServiceEPM, root
write list = epmadm, SAPServiceEPM, root
read only = No
hide dot files = No
dos filetime resolution = Yes
[SAPMNT]
path = /usr/sap
username = SAPServiceEPM,epmadm,root
read list = SAPServiceEPM, epmadm, root
write list = SAPServiceEPM, epmadm, root
case sensitive = Yes
SHARES RELATED FILE
Samba config file created using SWAT
from 192.168.9.17 (192.168.9.17)
Date: 2007/12/17 16:48:10
Global parameters
[global]
server string = EFLMI-SAMBA
encrypt passwords = No
password server =
log file = /var/opt/samba/log.%m
max log size = 1000
local master = No
username = epmadm, SAPServiceEPM,root
admin users = epmadm, SAPServiceEPM, root
read list = epmadm, SAPServiceEPM, root
write list = epmadm, SAPServiceEPM, root
read only = No
hide dot files = No
dos filetime resolution = Yes
[SAPMNT]
path = /usr/sap
username = SAPServiceEPM,epmadm,root
read list = SAPServiceEPM, epmadm, root
write list = SAPServiceEPM, epmadm, root
case sensitive = Yes
I checked the profile on the UNIX system there it has created
START_D06_miapp2
EPM_D06_miapp2
and these are existing....
In fact I've copied the START profile from the UNIX server to the windows server and it is working, if I give the path of the Local system in the SAPSTARTSRV.EXE when I run it manually on the Windows server.
The service also starts....
I've got the step on the installation procedure in a word file which is around 2 MB, however I can't put it in the post.
Regards,
Alfred
Hi,
We are also getting same error message. When we are installing Dilaog Instance on Windows.
Our CI and DI on AIX.5.2
In Step 8 (out of 9) of installation, we are getting error Service Not Started
sapinst.log file content :-
-
INFO 2008-02-18 03:46:44
Creating SAP start service of instance CID/D02...
INFO 2008-02-18 03:46:45
Creating file C:\Program Files\sapinst_instdir\NW04S\LM\AS\ORA\DI\sapstartsrv.exe.log.
INFO 2008-02-18 03:46:45
Output of D:\usr\sap\CID\D02\exe\sapstartsrv.exe -r -q -p
centralhost\sapmnt\CID\SYS\profile\START_D02_DIALOGHOST -s CID -n 02 -U DIALOGHOST\SAPServiceCID -P XXXXXX -e DIALOGHOST\cidadm is written to the logfile sapstartsrv.exe.log.
WARNING 2008-02-18 03:46:51
Execution of the command "D:\usr\sap\CID\D02\exe\sapstartsrv.exe -r -q -p
centralhost\sapmnt\CID\SYS\profile\START_D02_DIALOGHOST -s CID -n 02 -U DIALOGHOST\SAPServiceCID -P XXXXXX -e DIALOGHOST\cidadm" finished with return code -1. Output:
Service not started.
ERROR 2008-02-18 03:46:52
MOS-01011 'D:/usr/sap/CID/D02/exe/sapstartsrv.exe' returned with '-1'.
ERROR 2008-02-18 03:46:52
MOS-01011 'D:/usr/sap/CID/D02/exe/sapstartsrv.exe' returned with '-1'.
ERROR 2008-02-18 03:46:52
FCO-00011 The step createService with step key |NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|ind|ind|ind|ind|1|0|createService was executed with status ERROR .
-
Service User SAPSERVICECID is aligned to administrator group.
And when we tried to start the windows service (SAPCID_02) we got below message
"The SAPCID_02 service on Local computer Started and then stopped. Some Services stop automatoically,if they have no work to do, for example , the performane logs and Alert service"
From Windows we are able access all unix dirextories.We logged into windows host as "cidadm" user.
If use "cidadm" user we are able to start the service. But if we retry the installtion , installation will try to start the service by SAPServiceCID user id and it fails.
-
Please help me on this..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.