saphosctrl and HANA DB with same SID as SYSTEMDB and tenant

[MarcinOzdzinski]

Hi

Native SLES HA cluster tools (pacemaker , hawk) are using saphostctrl to control status of Hana DB components (for starting , stopping , promoting etc). They should report SYSTEMDB state , but in case we have tenant with same SID as main multitenant database saphosctrl is returning tenant DB state:

/usr/sap/hostctrl/exe/saphostctrl -function GetDatabaseStatus -dbname SID -dbtype hdb:

Database Status: Running
Component name: sapstartsrv (SAP Start service), Status: Running (Running)
Component name: hdbdaemon (HDB Daemon), Status: Running (Running)
Component name: hdbpreprocessor (HDB Preprocessor), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HMD), Status: Running (Running)
Component name: hdbwebdispatcher (HDB Web Dispatcher), Status: Running (Running)
Component name: hdbxsengine (HDB XS Engine-HMD), Status: Running (Running)
Component name: hdbcompileserver (HDB Compileserver), Status: Running (Running)
Component name: hdbMDC (HDB Multi Database Container), Status: Running (Tenant DB)
Component name: hdbconnectivity (HDB Connectivity), Status: Running (connect possible)
Component name: hdbalertmanager (HDB Alertmanager), Status: Warning (alerts on database:High=1)
Component name: hdbstatisticsserver (HDB embedded Statisticsserver), Status: Running (Running)

When we drop tenant database we have following output:

/usr/sap/hostctrl/exe/saphostctrl -function GetDatabaseStatus -dbname SID -dbtype hdb

Database Status: Running
Component name: sapstartsrv (SAP Start service), Status: Running (Running)
Component name: hdbdaemon (HDB Daemon), Status: Running (Running)
Component name: hdbnameserver (HDB Nameserver), Status: Running (Running)
Component name: hdbpreprocessor (HDB Preprocessor), Status: Running (Running)
Component name: hdbwebdispatcher (HDB Web Dispatcher), Status: Running (Running)
Component name: hdbcompileserver (HDB Compileserver), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HSD), Status: Running (Running)
Component name: hdbdiserver (HDB Deployment Infrastructure Server-HSD), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HFD), Status: Running (Running)
Component name: hdbdiserver (HDB Deployment Infrastructure Server-HFD), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HSM), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HSJ), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HPD), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HST), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HFT), Status: Running (Running)
Component name: hdbdiserver (HDB Deployment Infrastructure Server-HFT), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HPT), Status: Running (Running)
Component name: hdbdiserver (HDB Deployment Infrastructure Server-HST), Status: Running (Running)
Component name: hdbscriptserver (HDB Scriptserver-HSD), Status: Running (Running)
Component name: hdbindexserver (HDB Indexserver-HND), Status: Running (Running)
Component name: hdbMDC (HDB Multi Database Container), Status: Running (System DB)
Component name: hdbconnectivity (HDB Connectivity), Status: Running (connect possible)
Component name: hdbalertmanager (HDB Alertmanager), Status: Warning (alerts on database:High=1)
Component name: hdbstatisticsserver (HDB embedded Statisticsserver), Status: Running (Running)

I've opened ticket but support answered that this is not an error it should report tenant if it is exist under given.

Anyway i was uanble to configure cluster until i've dropped tenant DB.

It is strange cause having same SID for Multitenant and Tenant is default after upgrade db from Hana 1.0 to Hana 2.0

Any ideas ?

Regards

Marcin

[HakanHaslaman]

Your incident is still open at the side of SAP and waiting for your answer.

[MarcinOzdzinski]

I've answered. However i guess that support doesn't understand that current saphostctrl architecture is wrong. There is no possibility to enforce SYSTEMDB status reporting if tenent database with same SID exist. In such case it is not possible to use SLES HA cluster configuration at all !

Regards

Marcin