How to handle SAP systems during server reboots/downtime

[akpetteroe2]

Hi,

I would like to document how SAP systems need to be handled when the server reboots (both controlled and unplanned downtime) for instance by OS patches. Are there any guidelines from SAP for how this is done correctly?

Does anyone know if there is such official documentation from SAP somewhere?

I cannot find anything on SDN or in the SAP library.

Best,

Anne Kathrine

[andreas_zigann]

Hello,

does any standard procedure exist to start a SAP sytsem automatically after a reboot of a Windows Server?

The Service starts, but the SAP Instance does not. Do I have to create a new service with startsap command? Does a parameter exist, that the SAP Instance will start automatically when the service ist started?

Regards

Andreas

[former_member204746]

Andreas,

use the trick from SAP note Note 80474 - Automatic start of a gateway instance under NT

it works for ABAP instance as well.

also, next time, start your own topic.

[Former Member]

Hello Anne,

If you want to use startsap or stopsap & If there are multiple SAP instances on one host u2013 for example, a central instance and a dialog instance u2013 you must add an extra parameter to the scripts

UNIX

startsap <instanceID>

stopsap <instanceID>

For example, enter: startsap DVEBMGS00

SAP Web AS J2EE only system

The instance name (instance ID) of the central instance is JC<Instance_Number>, the instance name of a J2EE dialog instance is J<Instance_Number>.

To start the central instance and database instance

startsap: This checks if the database is already running. If not, it starts the database before starting the central services instance and the central instance.

You can start the database and SAP system separately by entering the following commands:

startsap DB <instanceID>

startsap R3 <instanceID of central services instance>

startsap R3 <instanceID of central instance>

Make sure that you always start the database first because otherwise the central services instance and the central instance cannot be started.

If you have a distributed system u2013 that is, central instance, central services instance and database instance on different hosts u2013 do the following:

On the database host, enter: startdb

On the central services instance host, enter:startsap R3

On the central instance host, enter: startsap R3

Enter the following to start dialog instances, if there are any: startsap

Stopiiing SAP System:

Normally you can give stopsap

For SAP Web AS ABAP+J2EE systems, you can enter either the command stopsap R3 or stopsap J2EE to stop the SAP instance comprising both ABAP and J2EE.

If you have a distributed system u2013 that is, central instance, central services instance and database instance on different hosts u2013 do the following:

On the central instance host, enter: stopsap R3

On the central services instance host, enter:stopsap R3

On the database host, enter:stopdb

PS: Make sure that no SAP instance is running before you enter stopdb on a standalone database server. No automatic check is made. Also if any kind of unplanned reboot happned you can see the logs (sapstop log and other logs related to db in Home directory of SIDadm user in Unix and for Windows you need to get the information from Event Manager (Logs)

Windows: One can start and stop SAP with the help of SAP MMC which can called by double cliking on SAP MMC from Desktop and it got installed automatically... while installing the SAP.

Hope it will help you to understand better how to make SAP up and down with clean commands....

.

Edited by: I tried it to make it little more readable but its coming like this ... No Bold and No Italics.. !!

[UweFetzer_se38]

Hi Anne,

and here's the SAP Help link for all NW Systems

[SAP Help link|http://help.sap.com/saphelp_nw2004s/helpdata/en/71/1c9a4267f9c66ae10000000a155106/frameset.htm]

Regards, Uwe (@se38)

P.S.: all links can also be found in [SAP Standard for System Administration Whitepaper|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10f0bfa8-e0a8-2b10-2da4-ef14a8c72541]

Edited by: Uwe Fetzer on Apr 15, 2010 2:17 PM

[JimSpath]

Anne Kathrine:

A base SAP install should leave "stopsap" and "startsap" scripts in a standard place. I don't have access to a Windows machine at the moment, but that's the standard procedure for a clean shutdown and startup. These will hook into both the disp+work processes and the database functions to do an orderly cleanup of open transactions and user sessions.

While you (or a lazy admin) could simply shut the system down with Ctrl-Alt-Del or equivalent, they are risking catastrophic data loss every time they do this. Yes, databases and SAP processes are designed to deal with crashes and power faults, but why tempt fate when the standard processes are well-known and well-tested?

Jim

p.s. also see SAP Note 1052203

https://service.sap.com/sap/support/notes/1052203

It is the only one I found on a quick search that references the newer sapcontrol.exe function.

p.p.s

Also see the SAP Help page (says CRM, but, well, you know):

http://help.sap.com/saphelp_crm50/helpdata/en/74/a6956ded9a214cb45828c65b9b8df0/frameset.htm

Edited by: Jim Spath on Apr 15, 2010 7:36 AM

[Former Member]

Hi Anne,Jim

Just to add a point.

For Primary/Standby disaster recovery systems, switch logs on the Primary, and ensure the logs are applied on the Standby.

Deactivate Oracle Data Guard before shutdown and Activate the Oracle Data Guard after start up.

Not necessarily every one have DR systems in place.

Checking SAPOSCOL, IPC, webdisp at OS leavel and performing system/health checks at SAP leave after successful restart.

Yes agree with Jim, SAP Process are designed to deal with crashes.

Hope this helps you.

Bharath.