Agents Administration - Tests
 

Configuration of HanaDeltaMrgTest

This test monitors the delta merge operations in the target database server and reports the number of merged tables and number of merge failed tables. In addition, this test also reports the time taken for merge operations. Using the detailed diagnosis of these measures, administrators can identify the number of merged records and thereby determine the server load along with the execution time for the merge operations. This may help them to proactively detect and resolve any performance issues before the end user is affected.

This page depicts the default parameters that need to be configured for the HanaDeltaMrgTest test.

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, specify the IP address of the host for which this test is to be configured.

  • In the PORT text box, specify port number through which the Apache Hive communicates. The default port is 30015.

  • In order to monitor a SAP HANA database server, a special database user account with Monitoring privileges has to be created in every SAP HANA database instance that requires monitoring. The syntax of the script that is used for user creation is discussed in Pre-requisites for Monitoring the SAP HANA Database Server.

    The name of such a USER has to be specified here.

  • Enter the password of the specified User in the PASSWORD text box and confirm it by retyping in the CONFIRM PASSWORD text box.

  • In the ISPASSIVE flag, if the value chosen for this parameter is Yes, then the SAP HANA database server under consideration is a passive server in a SAP HANA cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

  • By default, the detailed diagnosis of this test, if enabled, will report only the top-10 tables. This is why, the DD ROW COUNT parameter is set to 10 by default. If you want to include more or less tables in detailed diagnosis, then change the value of this parameter accordingly.

  • To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability

    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

  • Once the above values are provided, click on the UPDATE button to register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.