DpHalt, DPStop

[Former Member]

Hi,

Dispatcher is getting stopped after reart the instance, Below is the developer trace.

-

---

trc file: "dev_disp", trc level: 1, release: "640"

-

---

Thu Feb 15 21:05:20 2007

kernel runs with dp version 130(ext=102) (@(#) DPLIB-INT-VERSION-130)

length of sys_adm_ext is 312 bytes

sysno 00

sid CPQ

systemid 560 (PC with Windows NT)

relno 6400

patchlevel 0

patchno 108

intno 20020600

make: multithreaded, ASCII

pid 4784

***LOG Q00=> DpSapEnvInit, DPStart (00 4784) [dpxxdisp.c 1098]

shared lib "dw_xml.dll" version 108 successfully loaded

shared lib "dw_xtc.dll" version 108 successfully loaded

shared lib "dw_stl.dll" version 108 successfully loaded

shared lib "dw_gui.dll" version 108 successfully loaded

shared lib "dw_mdm.dll" version 108 successfully loaded

Thu Feb 15 21:05:32 2007

• WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0041.qqq.nxst) took 12 seconds

Thu Feb 15 21:05:48 2007

• WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 16 seconds

***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3887]

MtxInit: -2 0 0

DpSysAdmExtInit: ABAP is active

DpShMCreate: sizeof(wp_adm) 26496 (828)

DpShMCreate: sizeof(tm_adm) 2379840 (11840)

DpShMCreate: sizeof(wp_ca_adm) 18000 (60)

DpShMCreate: sizeof(appc_ca_adm) 6000 (60)

DpShMCreate: sizeof(comm_adm) 192000 (384)

DpShMCreate: sizeof(vmc_adm) 0 (364)

DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)

• ERROR => DpShMCreate: ShmCreate SHM_DP_ADM_KEY [dpxxtool2.c 1597]

• ERROR => DpIPCInit2: DpShMCreate [dpxxtool2.c 429]

• DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2

• DISPATCHER EMERGENCY SHUTDOWN ***

NiWait: sleep (5000 msecs) ...

NiISelect: timeout 5000 ms

NiISelect: maximum fd=1

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Thu Feb 15 21:05:53 2007

NiISelect: TIMEOUT occured (5000 ms)

Shutdown server ...

DpJ2eeDisableRestart

Switch off Shared memory profiling

ShmProtect( 57, 3 )

ShmProtect(SHM_PROFILE, SHM_PROT_RW

ShmProtect( 57, 1 )

ShmProtect(SHM_PROFILE, SHM_PROT_RD

detach from message server

***LOG Q05=> DpHalt, DPStop ( 4784) [dpxxdisp.c 8540]

Good Bye .....

Please help me to solve this problem

Thanks and regards

Seshu

[Former Member]

Hi Seshu

Seems memory issue.Increase the heap size and also check for java VM settings.Reboot the sever and start the instance

Reward points if usefull

[Former Member]

Hi

Thanks, This issue was resolved by rebooting the server.

Could you please tell me how to increase the heap size? How to find out how much needs to increase?. Where to check the JAVA VM settings.

Please clarify my doubts..

[Former Member]

Hi Seshu

Good your problem got solved.Your heap size and other memory parameters depends on your ram,os,load on the instance extra.You can change this parameter from configtool.

Sap has also provided one tool called templeteconfigurator which can help you in assigning memory parameters.

Frankly speaking it requires lot of experience and R and D for mastering this art.Comes only by practice because there is not any fixed rule.

Any speacific querry feel free to ask

I did not recieve any reward points from you seshu.

[Former Member]

Hi Rajat

Thank you!

From where we can down load templeteconfigurator tool

Regards

[Former Member]

HI Seshu

This tools comes with Netweaver.And is located in \usr\sap\SID\SYS\global\TemplateConfig folder

Award points :

[Former Member]

Hi Seshu,

Basically this issue occurs because there are memory segments still in use

since the instance was last restarted. On some Operating Systems this occurs

more often than on others.

SAP delivers a tool that can help you remove the remaining memory segments;

it is called 'cleanipc' and is located in the kernel directory. I'm not sure if this will

also work for Windows, but it will work for UNIX systems.

After you have stopped the instance, try a 'cleanipc <instance no>' first to see if

there are any memory segments remaining and then 'cleanipc <instance no> remove' to remove them. Do NOT try to run this command when the instance is

running because it may break it by removing memory segements that are in

use.

Please note that with NW2004S, the SCS has it's own instance number, so you

need to run this twice; once for the DVBEMGS / JC instance and once for the

SCS.

Also note that a dual-stack system (ABAP+JAVA) has one instance number (and

one for the SCS); so you need to stop the instance (both ABAP+JAVA) before

performing this command.

Hope this helps...

Kind regards,

Walter