STARTING AND STOPPING SAP

SAP Systems are started by using startup scripts ‘startsap’ and stopped by using script ‘stopsap’
MS Windows:
1.Use SAP Microsoft Management Console to Start and Stop the System.
Double Click on SAPMMC icon to get the Console Window.select the SID right Click Start.
2.Browser Based Console:(requires Java) SAP Management Console:
it is part of SAP Adaptive Computing Console(ACC) used to start and stop the Engine from the Browser.Browser requires Java Environment to run the Java Applets. http://hostname:50013/mc.
All the Systems in the landscape can be added using SIDADM credentials.
3.Startsap and stop scripts at command level
startsap command followed by NAME=SID nr=instance number and sapdiahost=hostname
stopsap command followed by NAME=SID nr=instance number and sapdiahost=hostname
The Services are located in services.msc
All the Services in the SAP are started by using sapstartsrv.exe
Unix Systems:
1.SAP Management Console
Browser Based Console:(Requires Java)
2.Execute startsap and stopsap scripts from the home directory of <SIDADM)
Startup Mechanism:
The Daemon(service) sapstartsrv is started to start and stop the services.
if sapstartsrv is stopped the SAP System Could not be started.
initially the startup scripts invoke the startup profile START_ASCS00_HOSTNAME to start sapcpe, message server, and enqueue server.
START_DVEBMGS00_HOSTNAME to start the sapcpe, dispatcher, work processes,igs
START_D02_Hostname to start the sapcpe, dispatcher, work processes,igs
Developer Traces(Work) profile dir exe
/usr/sap/SID/ASCS00/work /sapmnt/SID/profile /sapmnt/SID/exe/
/usr/sap/SID/DVEBMGS00/work /sapmnt/SID/profile /sapmnt/SID/exe/
/usr/sap/SID/D01/work /sapmnt/SID/profile /sapmnt/SID/exe/
The Startup services behavior is controlled by profiles and the executables are in the exe directory and traces are written to work Directory.
  1. global exe: to maintain globally at one location.
  2. local exe : used by the instance during initiation
  3. sapcpe.exe sap copy executables is used to copy the executables from global exe to local exe directory based sapcpeft(copy executables file table) and writes log into sapcpe.log
  4. Start database by using startdb(uni) or strdbs.cmd(win) and writes logs into home directory of SIDADM(Unix) and work directory on windows
  5. starts the message server by msg_server(.exe-win) and writes logs into
    dev_ms and stderr0,1,2,3,4 logs
  6. starts the enque server by enqserver(.exe-win) and writes logs into
    dev_enqsrv and stderr0,1,2,3,4 logs
  7. starts the dispatcher by disp+work(.exe-win) and writes logs into
    dev_disp stderr0,1,2,3,4 logs
  8. starts the work processes by disp+work(.exe-win) and writes logs into
    dev_w0,w1,w2,w3,w4,…wn-1 logs.
  9. starts the Internet Graphics Server igswd(.exe-win) and writes logs into
    \usr\sap\SOL\DVEBMGS00\igs\log
Check the above logs if the system is not started and evaluate the following issues.
  1. Permissions on the File System.Ex: to write Logs
  2. Firewall block of Ports and Protocols to start the services, ports are in Use by some other services
  3. File System is full to write logs
  4. Database is full
  5. System Hardware Changed
  6. Service Owners Changed password
  7. Wrong kernel Update, version, database, Unicode or non-Unicode
  8. Parameters are wrong for Buffers and work processes
  9. Memory parameters are not set properly
  10. .dlls/lib/bin/exe are missing
  11. database could not be started(evaluate the reasons of DB)
  12. Message Server Could not be started
  13. SAPCPE could not copy the executables
  14. Enqueue server could not be started
  15. dispatcher could not be started
  16. work processes could not be started
  17. IGS server could not be started.

Comments

Post a Comment

Popular posts from this blog

SPOOL WORK PROCESS

Spool Process: It is the Only Process that is used to output the documents to a Printer, fax, email etc.. Spool Work Processes are created by using parameter risp/wp_no_spo=1 it is possible to configure more than one spool work process based on available resources. Spool Process Work Flow: User Submits the request to print a Document. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files) Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for S...
Read more

ENQUEUE WORK PROCESS

It is used to lock and unlock the Objects during an update.These locks are displayed in SM12 and Held for longer hours until the transaction is committed or rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...
Read more

DIALOG PROCESS

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...
Read more