Add an SAP HANA database instance

Use SolarWinds Observability SaaS to monitor the performance and health of your SAP HANA databases. This guide walks you through the guided setup wizard end to end, from selecting an Agent to observing your first metrics.

Applies to self-managed SAP HANA (single-container and multi-tenant/MDC systems) and SAP HANA Cloud.

Overview

After onboarding, SolarWinds Observability SaaS deploys a database monitoring plugin to a SolarWinds Observability Agent that has network access to your SAP HANA instance. The plugin connects with a read-only monitoring user and continuously collects data so you can track:

Database availability and overall health
Query performance and expensive (long-running or memory-intensive) statements
SQL plan cache statistics
Active sessions and connections
Resource utilization such as CPU and memory

Before you begin

Make sure the following prerequisites are in place before you start the wizard:

A SolarWinds Observability organization with a plan that includes Database Performance Monitoring.
A SolarWinds Observability Agent (UAMS client) installed on a host (Linux or Windows) that can reach your SAP HANA instance over the network. You can install a new host from within the wizard if you don’t have one yet.
Network connectivity from the agent host to the SAP HANA endpoint on the correct port (see the table below).
Database credentials with permission to create a monitoring user, or an existing SAP HANA user that already has the MONITORING system privilege.

Connection and port reference

Deployment	Default port	Notes
Single-container SAP HANA	30015	Connect directly to the index server SQL port.
Multi-tenant (MDC) SAP HANA	30015	Connect to the tenant database, not `SYSTEMDB` (port 30013).
SAP HANA Cloud	443	SSL is required. Use the Verify CA SSL mode.

Add the instance

In SolarWinds Observability SaaS, click Add Data at the top.
On the Add Data dialog Intro, click Monitor my database performance.
Click SAP HANA.
Choose an existing SolarWinds Observability Agent on a monitored host.

Use the search box to filter agents by name. If no suitable Agent exists, install a new host directly from this step, then select it.

Click Next to continue.

The Agent must be able to open a network connection to your SAP HANA endpoint. For cloud databases, ensure the Agent host’s outbound traffic and any firewall or security-group rules allow access to the endpoint and port.

For more information about installing the SolarWinds Observability Agent on your host, see Add a self-managed host or Run the SolarWinds Observability Agent as a Docker image or Kubernetes deployment.

If the Agent you want to use is not displayed in the wizard, make sure it has host monitoring enabled. See Enable host monitoring on an Agent.
Enter your database credentials, enable SSL (optional), set your Packet Capture method, add any applicable tags (optional):
1. In the DBMS Instance Address box, enter the hostname (the IP address or fully qualified domain name) and the port (for example, myserver.example.com:30015).
2. In the Display Name box, enter a user-facing name to identify the database in SWO. (A default is generated automatically.)
3. Specify the database username and password of a new or existing user to be the monitoring user.
4. (Optional.) To enable SSL, click the Enable SSL toggle and select the SSL mode:
  - Require: SSL is enabled and the connection is encrypted, but no certificate checks are performed.
  - Verify CA: SSL is enabled and the connection is encrypted. The client verifies that the server is trustworthy by checking the certificate chain up to a trusted certificate authority (CA).
    
    SAP HANA Cloud uses port 443. Select the SSL Verify CA mode for cloud instances.
    
    If you select Verify CA, set SSL Authority Path to the location of the CA file on the agent host. The file must contain PEM-encoded data. For example:
    - On Linux: /etc/solarwinds/certs/ca.pem
    - On Windows: C:\ProgramData\SolarWinds\UAMSClient\plugin-storage\ca.pem
5. (Optional.) Click Add Tags to add any tags to organize and filter the database entity. Enter a tag key and value, and then click Add Tag. Repeat this step as necessary for any tags you want to add.
6. Click Next to continue.
Copy and execute the scripts against your SAP HANA instance so the monitoring user and sampling settings are in place. Run the statements with an administrative SAP HANA user (for example, using the HANA SQL console or hdbsql).
1. Create a new database user, if you don't already have one.
  
  Copy and execute the script to create a new user and grant the MONITORING system privilege. You can copy the snippet directly from the wizard, which fills in the username and password you entered in the Credentials step.
```
CREATE USER SWO_MONITOR PASSWORD password NO FORCE_FIRST_PASSWORD_CHANGE;
GRANT MONITORING TO SWO_MONITOR;
```
  - For MDC (multi-tenant) systems, connect to the tenant database (port 30015), not SYSTEMDB (port 30013).
  - SAP HANA Cloud requires SSL. Use the endpoint format <instance>.hana.<region>.hanacloud.ondemand.com:443.
2. Configure sampling.
  
  Configure sampling so SWO can capture expensive statements and plan-cache statistics while keeping overhead on the database low.
```
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('expensive_statement', 'enable') = 'true' WITH RECONFIGURE;
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('expensive_statement', 'threshold_duration') = '1000000' WITH RECONFIGURE;
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('expensive_statement', 'threshold_memory') = '100000000' WITH RECONFIGURE;
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') SET ('sql', 'plan_cache_statistics_enabled') = 'true' WITH RECONFIGURE;
```
3. The Advanced Configuration field is optional. The field provides a metric agent configuration path for you to indicate a different config file that can add to or override the dbo-global.conf file.
  
  This field should be used if you need to monitor multiple database instances from the same host Agent and you want to provide different configuration file paths to each DBO plugin on that same host Agent. Enter any parameters for metric collection in the Metric Agent field.
  
  See Database configuration files for information about configuration options.
  
  The /etc/solarwinds/dbo-global.conf configuration file is used for all database hosts. If you don't need to override configuration options in the dbo-global.conf file for this database instance, you do not need to provide a configuration file path for the Metric Agent field.
  
  The config files are JSON. When editing or creating a new configuration file, be sure to include the opening and closing brackets" { " and " }" . All options must be comma-separated.
  
  For example, a file might look like the following:
  
  { "disable-sampling":"false", "enable-explains":"false" }
4. Click Observe Database to continue.
The database plugin status and the other information you entered in the wizard is displayed on the Review tab.
1. If your plugin deployment was unsuccessful, check the Agent status you entered in the wizard, and verify your database credentials. Click Test Connection to refresh your plugin connection.
2. If your plugin deployment was successful, your database instance is being monitored with SolarWinds Observability.
3. Click Close to exit the wizard.

When the plugin is deployed and reporting, your SAP HANA instance appears in Database Performance Monitoring and the Databases entity views in SolarWinds Observability.

SAP HANA Cloud specifics

Use the endpoint format <instance>.hana.<region>.hanacloud.ondemand.com:443 as the DBMS instance address.
Enable SSL and select the Verify CA mode. Provide the CA file path in SSL Authority Path field.
Ensure the agent host can reach the cloud endpoint on port 443.

Multi-tenant (MDC) systems

On multi-container SAP HANA systems, connect the monitoring user to the tenant database on port 30015. Do not point the monitoring connection at SYSTEMDB (port 30013). Create the monitoring user inside the tenant database you want to observe.

Verify monitoring data

After Observe Database reports success, open Database Performance Monitoring or the Databases entity list.
Locate your database by the Display Name you set when you added the instance.
1. Confirm that availability, query, and resource metrics start to populate. It can take a few minutes for the first data to appear.

Troubleshooting

Plugin deployment or connection test fails

Confirm the selected Agent is online, the DBMS instance address and port are correct, and the username and password are valid.

Connection times out

Verify that the network is reachable from the agent host to the SAP HANA endpoint, including firewall and security-group rules.

Authentication error

Ensure the monitoring user exists and has the MONITORING privilege. On MDC systems, confirm you connected to the tenant database (30015), not SYSTEMDB (30013).

SAP HANA Cloud connection rejected

Enable SSL, use Verify CA, provide a valid CA file in SSL Authority Path, and use port 443.

No expensive statements or plan-cache data

Re-run the sampling configuration statements from Configure sampling, and confirm they applied with WITH RECONFIGURE.

Search SolarWinds Support