Starting and Stopping SAP Systems and Instances Using Commands (Unix)

Starting and Stopping SAP Systems and Instances Using Commands (Unix)

 

You can start and stop SAP systems and instances using the startsap and stopsap commands.

You can use command line options to specify these commands. Command line options are available in new style or old style.

Using New Style for Command Line Options and Parameters

Using new style, the syntax is as follows:

stopsap | stopsap [-t | -task <task>] [-i | -instance <instance>] [-v | -vhost "<virtual hostname>[ <virtual hostname>]*"][-c | -check] [-h | -help] [-V | -VERSION] [-C | -checkVHost]

 Example

• If you want to start an ABAP or dual-stack (ABAP+Java) central instance DVEBGMS00 that has the virtual host names cic11 and cic12, enter the following commands :

  startsap -t r3 -i DVEBGMS00 -v "cic11 cic12"

• If you want to start a Java central instance JC00 that has the virtual host names cic11 and cic12, enter the following commands :

  startsap -t j2ee -i JC00 -v "cic11 cic12"

The following command line options and parameters are available:

Command Line Options (New Style)

Parameter Name

Description

[-t | -task <task>]	Specify task
[-i | -instance <instance>]	Specify SAP system instance
[-v | -vhost "<virtual hostname>[ <virtual hostname>]*"]	Specify virtual host names
[-c | -check]	Check database and SAP instance status
[-h | -help]	Display help
[-V | -VERSION]	Display startsap script version
[-C | -checkVHost]	Check virtual host name

Parameters for <task> (New Style)

Parameter Name

Description

check	Check status of database and SAP system instances
r3 | j2ee	Start or stop SAP instances only. You can use either r3 or j2ee, regardless if the instance to be started or stopped is an ABAP or Java instance.
db	Start or stop ABAP database only
jdb	Start or stop Java database only
all | <blank>	Start or stop database and SAP instance
startupsrv	Start or stop sapstartsrv program

Parameters for <instance> where <nn> is the instance number

Parameter Name

Description

DVEBMGS<nn>	ABAP central Instance
D<nn>	ABAP dialog instance
ASCS<nn>	ABAP central services instance (ASCS instance)
SCS<nn>	Java central services instance (SCS instance)
J<nn>	Java central instance
TRX<nn>	TREX instance
ERS<nn>	Enqueue replication server instance (ERS instance)
SMDA<nn>	Diagnostics agent instance
W<nn>	Web services instance
G<nn>	Gateway instance

Using Old Style for Command Line Options and Parameters

Using old style, the syntax is as follows:

stopsap | stopsap [db|r3|j2ee|all|check|startupsrv] [<instance>] [<virtual hostname>]

 Example

• If you want to start an ABAP or dual-stack (ABAP+Java) central instance DVEBGMS00 that has the virtual host names cic11 and cic12, enter the following commands :

  startsap r3 DVEBGMS00 cic11 cic12

• If you want to start a Java central instance DVEBGMS00 that has the virtual host names cic11 and cic12, enter the following commands :

  startsap j2ee JC00 cic11 cic12

The following command line options and parameters are available:

Command Line Options (Old Style)

Parameter Name

Description

check [<instance>] [<virtual hostname>]	Check status of database and SAP system instances
r3 | j2ee [<instance>] [<virtual hostname>]	Start or stop SAP instances only. You can use either r3 or j2ee, regardless if the instance to be started or stopped is an ABAP or Java instance.
db [<instance>] [<virtual hostname>]	Start or stop ABAP database only
jdb [<instance>] [<virtual hostname>]	Start or stop Java database only
all | <blank>	Start or stop database and all SAP system instances running on the same physical host
startupsrv	Start or stop sapstartsrv program

Parameters for <instance> where <nn> is the instance number

Parameter Name

Description

DVEBMGS<nn>	ABAP central Instance
D<nn>	ABAP dialog instance
ASCS<nn>	ABAP central services instance (ASCS instance)
SCS<nn>	Java central services instance (SCS instance)
JC<nn>	Java central instance
J<nn>	Java dialog instance
TRX<nn>	TREX instance
ERS<nn>	Enqueue replication server instance (ERS instance)
SMDA<nn>	Diagnostics agent instance
W<nn>	Web services instance
G<nn>	Gateway instance

Prerequisites

• Make sure that you have logged on to the physical host of the SAP system instances as user <sapsid>adm.

• Make sure that the host names defined in the DNS server match the names of the SAP system instance hosts. In particular, keep in mind that host names are case-sensitive. For example, if the names of the SAP system instance hosts are in upper case, but the same host names are defined in the DNS server in lower case, starting and stopping the system does not work.

• If you want to use startsap or stopsap (for example, in a script) and require the fully qualified name of these SAP scripts, create a link to thestartsap script in the home directory of the corresponding user.

• You cannot use startsap or stopsap commands in a switchover cluster environment. Therefore in a high-availability (HA) system you must use the failover cluster software of your HA partner to start or stop instances running on the switchover cluster.

• You cannot use startsap or stopsap commands to start or stop database-specific tools. For more information about how to start or stop database-specific tools, see the database-specific information in this documentation and the documentation from the database manufacturer.

• Make sure that no SAP instance is running before you execute stopsap on a standalone database server. No automatic check is made.

• When you use stopsap in a Multiple Components in One Database (MCOD) system with two central instances, only one central instance and the database are shut down. Therefore, you must first stop the other SAP system or make sure that it has already been stopped.

Procedure

Starting an SAP System

• If you want to start all SAP system instances running on the same host, execute the following command:

  New style: startsap or startsap -t all

  Old style:startsap or startsap all

• If you want to start SAP system instances separately, enter the following command:

  New style:startsap -t r3|j2ee -i <instance> [-v "<virtual host name>"]

  Old style:startsap r3|j2ee <instance> [<virtual host name>]

  Make sure that you adhere to the following sequence when starting the instances:

  ABAP system:

  1. Database instance

  2. Central instance

  3. Dialog instances (if available)

  Java system:

  1. Database instance

  2. SCS instance

  3. Central instance

  4. Dialog instances (if available)

  Dual-stack (ABAP+Java) system:

  1. Database instance

  2. SCS instance

  3. Central instance

  4. Dialog instances (if available)

Stopping an SAP System

• If you want to stop all SAP system instances running on the same host, execute the following command:

  New style: stopsap or stopsap -t all

  Old style:stopsap or stopsap all

• If you want to stop SAP system instances separately, enter the following command:

  New style:stopsap -t r3|j2ee -i <instance> [-v "<virtual host name>"]

  Old style:stopsap r3|j2ee <instance> [<virtual host name>]

  Make sure that you adhere to the following sequence when stopping the instances:

  ABAP system:

  1. Dialog instances (if available)

  2. Central instance

  3. Database instance

  Java system:

  1. Dialog instances (if available)

  2. Central instance

  3. SCS instance

  4. Database instance

  Dual-stack (ABAP+Java) system:

  1. Dialog instances (if available)

  2. Central instance

  3. SCS instance

  4. Database instance