OCF_HEARTBEAT_SAPDAT(7) | OCF resource agents | OCF_HEARTBEAT_SAPDAT(7) |
ocf_heartbeat_SAPDatabase - Manages a SAP database instance as an HA resource.
SAPDatabase [start | stop | status | monitor | meta-data | validate-all]
Resource script for SAP databases. It manages a SAP database of any type as an HA resource.
The purpose of the resource agent is to start, stop and monitor the database instance of a SAP system. Together with the RDBMS system it will also control the related network service for the database. Like the Oracle Listener and the xserver of MaxDB. The resource agent expects a standard SAP installation of the database and therefore needs less parameters to configure. The resource agent supports the following databases:
- Oracle 10.2, 11.2 and 12
- DB/2 UDB for Windows and Unix 9.x
- SAP-DB / MaxDB 7.x
- Sybase ASE 15.7
- SAP HANA Database since 1.00 - with SAP note 1625203 (http://sdn.sap.com)
In fact this resource agent does not run any database commands directly. It uses the SAP standard process SAPHostAgent to control the database. The SAPHostAgent must be installed on each cluster node locally. It will not work, if you try to run the SAPHostAgent also as a HA resource. Please follow SAP note 1031096 for the installation of SAPHostAgent. The required minimum version of SAPHostAgent is: Release: 7.20 Patch Number: 90 or compile time after: Dec 17 2011
A single HANA is managed as a primitive resource by the SAPDatabase RA. Therefor the parameter MONITOR_SERVICES has to match the output service names of the command "sapcontrol -nr $InstNr -function GetProcessList". "$InstNr" has to be replaced by the respective instance number.
For an HANA database with SID "TST" and instance number "10", the resource configuration looks like: primitive rsc_SAPDatabase_TST_HDB10 ocf:heartbeat:SAPDatabase \ params DBTYPE="HDB" SID="TST" \ MONITOR_SERVICES="hdbindexserver|hdbnameserver" \ op start interval="0" timeout="3600" \ op monitor interval="120" timeout="700" \ op stop interval="0" timeout="600"
SID
(unique, required, string, no default)
DIR_EXECUTABLE
(optional, string, default "/usr/sap/hostctrl/exe")
DBTYPE
(required, string, no default)
DBINSTANCE
(unique, optional, string, no default)
DBOSUSER
(unique, optional, string, no default)
NETSERVICENAME
(optional, string, no default)
DBJ2EE_ONLY
(optional, boolean, default false)
JAVA_HOME
(optional, string, no default)
STRICT_MONITORING
(optional, boolean, default false)
AUTOMATIC_RECOVER
(optional, boolean, default false)
MONITOR_SERVICES
(optional, string, no default)
DIR_BOOTSTRAP
(optional, string, no default)
DIR_SECSTORE
(optional, string, no default)
DB_JARS
(optional, string, no default)
PRE_START_USEREXIT
(optional, string, no default)
POST_START_USEREXIT
(optional, string, no default)
PRE_STOP_USEREXIT
(optional, string, no default)
POST_STOP_USEREXIT
(optional, string, no default)
This resource agent supports the following actions (operations):
start
stop
status
monitor
validate-all
meta-data
methods
The following is an example configuration for a SAPDatabase resource using the crm(8) shell:
primitive p_SAPDatabase ocf:heartbeat:SAPDatabase \
params \
SID=string \
DBTYPE=string \
op monitor depth="0" timeout="60s" interval="120s"
The following is an example configuration for a SAPDatabase resource using pcs(8)
pcs resource create p_SAPDatabase ocf:heartbeat:SAPDatabase \
SID=string \
DBTYPE=string \
op monitor depth="0" timeout="60s" interval="120s"
http://clusterlabs.org/
ClusterLabs contributors (see the resource agent source for information about individual authors)
06/27/2020 | resource-agents UNKNOWN |