[Fwd: Problems starting SAP dispatcher on SuSE SLES7, SAP Version 4.6D]

Jan Schreckenbach Jan.Schreckenbach at sap.com
Wed Nov 20 18:53:50 MET 2002


-------- Original Message --------
Subject: Problems starting SAP dispatcher on SuSE SLES7, SAP Version 4.6D
Date: Mon, 18 Nov 2002 22:31:58 +0100
From: "Furnes, Kjell-Erik" <Kjell-Erik.Furnes at tybring-gjedde.com>
To: "'linux.general-admin at listserv.sap.com'"	 <linux.general-admin at listserv.sap.com>

Hello list !

We have installed a Proliant DL360 server 2x1100Mhz, 2GB RAM, 5GB swap and
would like to test SAP application server on this server.
We have installed SuSE SLES 7 with a 2.4.18 kernel from SuSE, and performed
a dialog instance installation connecting up to our TRU64 central instance
and oracle database.

df -k shows
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/ida/c0d0p1        1036076    256412    727032  27% /
/dev/ida/c0d0p4        2501872   1073924   1300856  46% /usr
shmfs                  1099476         0   1099476   0% /dev/shm

Installation works fine, but when we try to run startsap output tells us
Instance started, but no dw processes are created ( Dispatche dies )

dev_disp shows

Mon Nov 18 21:55:30 2002
relno      4640
patchlevel 0
patchno    534
intno      0
pid        4289
***LOG Q00=> DpSapEnvInit, DPStart (00 4289) [dpxxdisp.c   877]
*** ERROR => SigISaveOldFunctions: sigaction sig 32 (22: Invalid argument)
[sigux.c      315]
*** ERROR => SigIReaction: sigaction sig 34 (22: Invalid argument) [sigux.c
454]
MtxInit: -2 0 0
***LOG Q06=> DpProfileRead, sapgparam (rdisp/btcname ) [dpxxtool2.c  730]
*** ERROR => DpIPCInit: DpProfileRead [dpxxtool2.c  358]
*** ERROR => DpSapEnvInit: DpIPCInit [dpxxdisp.c   11220]
*** ERROR => DpRqIQRemove: ShmDelete [dpxxqueu.c   405]
***LOG Q05=> DpHalt, DPStop ( 4289) [dpxxdisp.c   6530]

ipcs -l shows
------ Shared Memory Limits --------
max number of segments = 4096
max seg size (kbytes) = 1048576
max total shared memory (kbytes) = 8388608
min seg size (bytes) = 1

------ Semaphore Limits --------
max number of arrays = 1024
max semaphores per array = 250
max semaphores system wide = 32000
max ops per semop call = 32
semaphore max value = 32767

------ Messages: Limits --------
max queues system wide = 1024
max size of message (bytes) = 8192
default max size of queue (bytes) = 16384

files in the /usr/sap/<SID>/work are
ESSTATS   dev_disp      dev_sapstart   sapstart.log   sapstart2.trc  stderr1
stdout1
INSTSTAT  dev_disp.old  dw.sapTSC_D00  sapstart1.trc  se.sapTSC_D00  stderr2
stdout2

I have searched the archives and the SAPNet, but have not found good
explanations as to why this happens.
One article I found was close, but no cigar

http://listserv.sap.com/pipermail/linux.general/2001-October/001666.html

Have anyone experienced these kind of problems ?
Any input is appretiated.


Best regards

Kjell Erik Furnes


-- 
_______________________________________________________________________

THE BEST RUN E-BUSINESSES RUN SAP
_______________________________________________________________________

Jan Schreckenbach                      email: Jan.Schreckenbach at sap.com
SAP AG Walldorf/Baden, Germany         Phone: +49 6227  7-47474
LinuxLab                               Fax  : +49 6227 78-31414

SAP LinuxLab support address: linux at sap.com




More information about the linux.general mailing list