Managing Serviceguard Extension for SAP Version B.05.10, December 2012

The package parameter db_vendor defines the underlying RDBMS database technology that is
to be used with the SAP application. It is preset to oracle in sgesap/oracledb, but should
otherwise be manually set to oracle. It is still optional to specify this parameter, but either
db_vendor or db_system needs to be set in order to include the database in the failover
package.
Optionally, listener_name can be set if the Oracle listener is defined on a name different from
the default value LISTENER.
Optionally, listener_password can be set if a password for the Oracle listener process is
configured. The root user and any user with a defined Serviceguard access role (full admin, package
admin or monitor) will be able to read this value.
sgesap/dbinstance can be used for databases of SAP JAVA-only, ABAP-only or dual stack
instances. The module will detect all available SAP tools to handle the database and use them if
possible. If no SAP tools are there or the SAP tools fail to work, a fallback is implemented to handle
the database with generic tools of the database vendor.
Subsection for the MaxDB database component: SD426
Parameters that can be set to handle a MaxDB database as part of a package with the
sgesap/dbinstance or sgesap/maxdb module.
The package parameter db_vendor defines the underlying RDBMS database technology that is
to be used with the SAP application. It is preset to maxdb in sgesap/maxdb, but should otherwise
be manually set to maxdb. It is still optional to specify this parameter, but either db_vendor or
db_system needs to be set in order to include the database in the failover package.
Optionally, maxdb_userkey sets the MaxDB userkey that is mapped for the operating system
level administrator to the database control user (via XUSER settings). The value needs to be set if
the default control userkey 'c' is not available to be used.
Subsection for the Sybase database component: SY427
Parameters that can be set to handle a Sybase database as part of a package with the
sgesap/dbinstance module.
The package parameter db_vendor defines the underlying RDBMS database technology which
must be used with the SAP application.
Set the parameter to sybase. This is an optional parameter if db_system is set. To include the
database in the failover package either db_vendor or db_system have to be set.
The optional attributes aseuser and asepasswd can be set to enable database native shutdown
and monitoring. Native mechanisms will be used as fallbacks in case SAP mechanisms fail.
The user is used for shutdown if it has the necessary privileges (sa_role), otherwise it is used for
monitoring only. A monitoring only user must have the right to run a selec statement on the DB’s
sysuser table. Native fallback is disabled if attributes are not set.
NOTE: db_system determines the name of the database (schema) for SAP. Usually it is a three
letter name, similar to a sap_system value (SID). If the database name is not specified with
db_system, but db_vendor is set, then db_system is set to sap_system.
Subsection for the SAP component: MS428
Parameters that can be set to handle one or more SAP instances as part of a package with module
sgesap/sapinstance.
A sap_instance defines any SAP Netweaver Application Server instance based on the SAP
ABAP technology-stack, the SAP JAVA technology-stack or a combination of both. All parts of the
instance are packaged together as a single entity. This includes instance parts like icman,
workprocesses, SAP JVMs or an IGS. System Central Service instances or the corresponding
Enqueue Replication Service instances can also be specified. SAP instances are defined by specifying
the instance name and instance number.
Modular Package Configuration 83