Installation guide

Attribute Description Required
POST_STOP_
USEREXIT
uses. Those programs can include by
writing an OCF resource agent into the
Heartbeat cluster. However, sometimes
writing a resource agent is too much
effort for this task. With the provided
userexits, one can easily include their
own scripts, that do not follow the OCF
standard, into the cluster. Note that the
returncode of said script will not be used
by the SAPInstance resource agent. The
call of userexit is syncron, meaning the
time the script requires is going into the
timeout of the start/stop operation
defined in the Heartbeat cluster
configuration.
If the script hangs, SAP may not be
started.
DEFAULT: empty
7.4.5 SAPDatabase
The purpose of the resource agent is to start, stop, and monitor the database instance of an
SAP system. Together with the RDBMS system, it will also control the related network service
for the database (such as the Oracle Listener or the MaxDB xserver). The resource agent
expects a standard SAP installation and therefore requires less parameters configured.
The monitor operation of the resource agent can test the availability of the database by using
SAP tools (R3trans or jdbcconnect). With that, it ensures that the database is truly accessible
by the SAP system.
After an unclean exit or crash of a database, require a recover procedure to restart can be
required. The resource agent has a procedure implemented for each database type. If
preferred, the attribute AUTOMATIC_RECOVER provides this functionality.
Attribute Description Required
SID The unique SAP system identifier.
e.g., RHC
DEFAULT: empty
Yes
DBTYPE The name of the database vendor used.
Set either: ORA,DB6,ADA
DEFAULT: empty
Yes
48 | www.redhat.com