SAP Adaptive Server Enterprise Database (SAP ASE)

This page explains how to prepare a SAP Adaptive Server Enterprise (ASE) database for the connectivity to SAP Focused Run.

Currently the following monitoring application are supported for SAP ASE databases:

Preparations in the Managed Database

TaskActions
Install ASE DB 15.7 or higher

You need at least ASE DB 15.7, optionally install the latest ASE DB and latest Patches from support.sap.com/swdc -> Databases -> SAP Adaptive Server Enterprise

To check details which ASE DB monitoring feature is requiring which SAP Hostagent version please see SAP Note 2577046.

Check Security Guide and especially SAP Note 2236137 - SYB: saphostctrl/sapdbctrl - enable discovery for native ASE database installations.

SAP Focused Run supports monitoring of ASE HADR configurations with Replication Management Agents (RMA) accordingly to the documentation:

Run Outside Discovery on the Host

As prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in page Preparing Outside Discovery.

Be aware the hostname interpreted as DB Hostname by Outside Discovery is the first entry set in file in $ASE_HOME$/interfaces

Note: This hostname should be the same as SLDSYSTEMHOME set in SAP NetWeaver ABAP or j2ee/dbhost in SAP NetWeaver JAVA (see also SAP Note 1052122).

ASE HADR cluster: The configuration of outside discovery for ASE HADR cluster is described in SAP Note 2577046 "SYB: saphostctrl - Changelog for ListDatabaseMetrics function of SAP Host Agent" in section “Setup”.

Check Needed Data Suppliers

The SAP ASE DB can be used in stand-alone or associated to an ABAP or Java Stack

The SAP ASE DB can be used in stand-alone or associated to an ABAP or Java Stack. Therefore, the corresponding Data Supplier needs to be setup. See the SAP NetWeaver Application Server ABAP Preparation or SAP NetWeaver Application Server Java Preparation pages.

Create DB monitoring user and provide connection credentials

SAP Focused Run utilizes SAP Host Agent Web methods to get DB monitoring data from sapsa as in rsecssfs secure store with key DB_CONNECT/SYB/SADB_USER.

  1. Create the DB monitoring user for the ASE database with the right authorization. 
  2. Create an entry for the monitoring user in the secure store.

    Note: The SAP Host Agent provides a simple method, for 1 and 2, following SAP Note 1797040.

  3. Initialize (once) the ASE DB monitoring

If the ASE DB monitoring was not initialized with the Transaction "DBACockpit" do the following: 

For all ASE DB, the execution of the SAP Host Agent method 

saphostctrl -function SetDatabaseProperty -dbname <SID> -dbtype syb SETUP_LIST_METRICS=saptools is recommended (easier than to configure a remote DBA Cockpit Connection to a remote ABAP System).

Note: All SAP Host Agent methods can be executed and scripted local or remote by a saphostctrl or any other webservice client.

Alternative process: The monitoring user can be created by ASE user management sqls using ISQL. The secure store can be maintained by OS command rsecssfx.

Support of ASE HADR scenarioIn order to get the replication scenario correctly reported by the Outside Discovery and registered in the LMDB, following prerequisite steps are required:

Maintain the SLDSYSTEMHOME parameter on SAP NetWeaver ABAP or j2ee/dbhost on SAP NetWeaver JAVA to match the hostname of a floating IP.
Perform system restart and re-execution of the data supplier.

Remark: as a result, for every primary/HA/DR site a dedicated system will be created in the LMDB with a virtual DB entry on top of it.
Example: for a two tier replication setup with an ABAP system there must be 4 entries: 1 for ABAP, 1 for virtual DB, 1 for primary and 1 for secondary DB.

To be able to collect the ASE metrics on HADR hosts following minimum versions are required:

  • SAP Focused Run 4.0 SP0
  • SDA 1.63.0
  • SAP Host Agent 7.21 PL64*
  • Monitoring Content Delivery Version 12

Remark: at the moment, if a failover occurs there will be no automatic detection triggered by the Outside Discovery. Means, in worst case, it could take up to 12 hours to detect and to reflect it in SAP Focused Run. In order to ensure that the monitoring getting reconfigured on a new primary as soon as possible, either set the Outside Discovery frequency to the highest supported - 60 minutes (by passing additional parameter "- frequency <minutes>" while executing the ConfigureOutsideDiscovery) or perform the ExecuteOutsideDiscovery manually.
In the near future, in one of the upcoming SAP Host Agent patch levels, it is planned to introduce the failover detection mechanism.

*To be applied only in combination with other minimum versions from the above list, else this will lead to grey metrics on some of the replication hosts. If this is not possible due to some reasons, please use a patch level lower than 64!