Sunday, 23 October 2011

Dispatcher troubleshooting


DISPATCHER IS NOT COMING UP
Main reasons for Dispatcher down is :
Shared memory not realesed
Page memory
Network problem
Services(listener)
Changing profile parameters(if any parameters changed it will causes to dispatcher down)
 File system permissions
To solve these problems check the following……

1)need to check the services using services.msc
2)check the Developer trace files DEV_DISP,DEV_WO files in work directory
3)check the start profile whether it is modified or any line missing
4)check the permissions
5)go to your profile directory
Sappfpar pf=instanceprofile  check
It will display the errors and warnings
6)if problem is with shared memory try to perform shared memory cleanup and then start sap
Cleanipc  instancenumber  remove
It will clean the ipc
7)if problem with shared memory most of the cases restart will solve the problem,otherwise perform above step
8)hit r3trans –d at command prompt,it will generate trans.log file where you execute the command.
9)it may be cause of page memory
Em/address_space_mb we need to change this parameter at o/s level from 128mb  to 512 mb.
10)changing of parameters also cause dispatcher down,try to find out those changed parameters and reset them to previous values.to check changed parameters transaction is TU02
11)also need to check the value of  abap/buffersize
12) it may be cause of TNS service not active,start tns listener
Try to ping tns using command TNSPING  <SID>

No comments:

Post a Comment