ocf_heartbeat_SAPDatabase

ocf_heartbeat_SAPDatabase
Prev	Appendix C. Resource agent manual pages	Next

Name

ocf_heartbeat_SAPDatabase — Manages any SAP database (based on Oracle, MaxDB, or DB2)

Synopsis

Description

Resource script for SAP databases. It manages a SAP database of any type as an HA resource.

Supported Parameters

SID: The unique SAP system identifier. e.g. P01 (required, string, no default)
DIR_EXECUTABLE: The full qualified path where to find sapstartsrv and sapcontrol. (optional, string, no default)
DBTYPE: The name of the database vendor you use. Set either: ORA,DB6,ADA (required, string, no default)
NETSERVICENAME: The Oracle TNS listener name. (optional, string, no default)
DBJ2EE_ONLY: If you do not have a ABAP stack installed in the SAP database, set this to TRUE (optional, boolean, default false)
JAVA_HOME: This is only needed if the DBJ2EE_ONLY parameter is set to true. Enter the path to the Java SDK which is used by the SAP WebAS Java (optional, string, no default)
STRICT_MONITORING: This controls how the resource agent monitors the database. If set to true, it will use SAP tools to test the connect to the database. Do not use with Oracle, because it will result in unwanted failovers in case of an archiver stuck (optional, boolean, default false)
AUTOMATIC_RECOVER: The SAPDatabase resource agent tries to recover a failed start attempt automaticaly one time. This is done by running a forced abort of the RDBMS and/or executing recovery commands. (optional, boolean, default false)
DIR_BOOTSTRAP: The full qualified path where to find the J2EE instance bootstrap directory. e.g. /usr/sap/P01/J00/j2ee/cluster/bootstrap (optional, string, no default)
DIR_SECSTORE: The full qualified path where to find the J2EE security store directory. e.g. /usr/sap/P01/SYS/global/security/lib/tools (optional, string, no default)
DB_JARS: The full qualified filename of the jdbc driver for the database connection test. It will be automaticaly read from the bootstrap.properties file in Java engine 6.40 and 7.00. For Java engine 7.10 and higher the parameter is mandatory. (optional, string, no default)
PRE_START_USEREXIT: The full qualified path where to find a script or program which should be executed before this resource gets started. (optional, string, no default)
POST_START_USEREXIT: The full qualified path where to find a script or program which should be executed after this resource got started. (optional, string, no default)
PRE_STOP_USEREXIT: The full qualified path where to find a script or program which should be executed before this resource gets stopped. (optional, string, no default)
POST_STOP_USEREXIT: The full qualified path where to find a script or program which should be executed after this resource got stopped. (optional, string, no default)

Supported Actions

This resource agent supports the following actions (operations):

start: Starts the resource. Suggested minimum timeout: 1800.
stop: Stops the resource. Suggested minimum timeout: 1800.
status: Performs a status check. Suggested minimum timeout: 60.
monitor: Performs a detailed status check. Suggested minimum timeout: 60. Suggested interval: 120.
validate-all: Performs a validation of the resource configuration. Suggested minimum timeout: 5.
meta-data: Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
methods: Suggested minimum timeout: 5.

Example

The following is an example configuration for a SAPDatabase resource using the crm(8) shell:

primitive example_SAPDatabase ocf:heartbeat:SAPDatabase \
  params \
    SID=string \
    DBTYPE=string \
  op monitor depth="0" timeout="60" interval="120"

Prev	Up	Next
ocf_heartbeat_rsyncd	Home	ocf_heartbeat_SAPInstance