Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Appendix A. Component options


A.1. SAPInstance resource parameters

Parameters that are available for the configuration of SAPInstance resources are shown below:

Expand
Resource optionsRequiredDefaultDescription

InstanceName

yes

 

The full SAP instance profile name (<SID>_<NAME><instance>_<virt_ hostname>), for example, S4H_ASCS20_s4ascs.

START_PROFILE

no

 

The name of the SAP instance profile. Specify this parameter, if you have changed the name of the SAP instance profile after the default SAP installation.

SAP standard paths are searched by default.

IS_ERS

no

false

Only used for ASCS/ERS SAP Netweaver installations without implementing a promotable resource to allow the ASCS to find the ERS running on another cluster node after a resource failure.

You must set this parameter to true for the ERS instance resource in an ENSA1 setup.

DIR_EXECUTABLE

no

 

The fully qualified path to binaries such as sapstartsrv and sapcontrol. Specify this parameter if you have changed the SAP kernel directory location after the default SAP installation.

SAP standard paths are searched by default.

DIR_PROFILE

no

 

The fully qualified path to the SAP START profile. Specify this parameter if you have changed the SAP profile directory location after the default SAP installation.

SAP standard paths are searched by default.

AUTOMATIC_RECOVER

no

false

The resource agent tries to recover a failed start attempt automatically one time. This is done by killing running instance processes, removing the kill.sap file, and executing cleanipc. Sometimes a crashed SAP instance leaves some processes or shared memory segments behind. Set this option to true to remove those leftovers during a start operation.

MONITOR_SERVICES

no

disp+work|msg_server|enserver|enrepserver|jcontrol|jstart|enq_server|enq_replicator

The list of services of an SAP instance that need to be monitored to determine the health of the instance. To monitor more, less or other services that sapstartsrv supports, change the list using this parameter. Names must match the strings used in the output of the command sapcontrol -nr <instance> -function GetProcessList. Use the pipe sign to specify multiple services. The value for this parameter must always be the complete list of the services to monitor.

SHUTDOWN_METHOD

no

normal

Usually a SAP instance is stopped by the command sapcontrol -nr <instance> -function Stop.

Set this to KILL to kill the SAP instance using operating system commands. This terminates SAP processes of the instance with kill -9, deletes shared memory using cleanipc and deletes the kill.sap file. That method is much faster than the graceful stop, but the instance does not have the chance to notify other SAP instances in the same system. Use with care!

START_WAITTIME

no

3600

The maximum time in seconds the cluster waits after a resource start, before the resource executes a monitor operation.

ERS_InstanceName

no

 

Only enable this in a promotable resource configuration.

The fully qualified SAP enqueue replication instance name. Usually this is the name of the SAP instance profile. You must use the following properties for the promotable configuration in the cluster:

  • clone_max = 2
  • clone_node_max = 1
  • master_node_max = 1
  • master_max = 1

ERS_START_PROFILE

no

 

Only use this in a promotable resource configuration.

Specify this parameter, if you have changed the name of the ERS instance profile after the default SAP installation.

SAP standard paths are searched by default.

MINIMAL_PROBE

no

false

Setting this to true forces the resource agent to do only a minimal check during the resource probe. This is needed for special file system setups.

Enabling this is only supported when specified in the configuration steps.

A.2. SAPStartSrv resource parameters

Parameters that are available for the configuration of SAPStartSrv resources are shown below:

Expand
Resource optionsRequiredDefaultDescription

InstanceName

yes

 

The full SAP instance profile name (<SID>_<NAME><instance>_<virt_ hostname>), for example, S4H_ASCS20_s4ascs.

START_PROFILE

no

 

The name of the SAP instance profile. Specify this parameter, if you have changed the name of the SAP instance profile after the default SAP installation.

SAP standard paths are searched by default.

A.3. SAPDatabase resource parameters

Parameters that are available for the configuration of SAPDatabase resources are shown below:

Expand
Resource optionsRequiredDefaultDescription

SID

yes

 

SAP system identifier.

DBTYPE

yes

 

The name of the database vendor you use. Set this to ADA, DB6, ORA or SYB accordingly.

DBINSTANCE

no

 

You must set this for implementations where the database instance name is not the same as the SID, for example when using Oracle DataGuard.

DBOSUSER

no

 

Set this parameter when your database is using a different user than the default.

Defaults per database type:

  • ADA: defined in /etc/opt/sdb
  • DB6: db2<sid>
  • ORA: ora<sid> and oracle
  • SYB: syb<sid>

STRICT_MONITORING

no

false

This parameter controls how the resource agent monitors the database. Set to true to use saphostctrl -function GetDatabaseStatus for testing the database state. By default, and when set to false, only operating system processes are monitored.

AUTOMATIC_RECOVER

no

false

Set this to true to always call saphostctrl -function StartDatabase with the -force option.

MONITOR_SERVICES

no

 

Defines which services are monitored by the SAPDatabase resource agent. Service names must correspond to the output of the saphostctrl -function GetDatabaseStatus command.

The database type DBTYPE defines the default value as follows:

  • ADA: "Database"
  • DB6: "{SID}|{db2sid}"
  • ORA: "Instance|Database|Listener"
  • SYB: "Server"

Set this parameter only if you need to monitor different services than the ones listed above.

Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2026 Red Hat
Nach oben