Agents Administration - Tests
 

Configuration of HanaExpensStmtTest

This test reports the count of expensive SQL statements and the maximum duration for which such statements ran.

The default parameters associated with this test are as follows:

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

  • In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

  • Specify the port number at which the specified HOST listens to in the PORT text box. 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:

      create user <username> password <password>
      grant monitoring to <username>

    A sample script for user creation is:

      create user sapegadmin password eGurkha@123;
      grant monitoring to sapegadmin;

    The name of this user has to be specified in the USER text box.

  • Specify the password of the specified USER in the PASSWORD text box.

    Note:

    The password should be alpha-numeric containing atleast one uppercase alphabet and a special character.

  • Confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • In the DD RECORDS text box, specify the number of expensive SQL statements for which the detailed analysis is to be reported in the DETAILED DIAGNOSIS section. By default, the value specified in this text box is 10. This indicates that detailed analysis of the top 10 expensive SQL statements executing on the SAP HANA database server will alone be listed in the DETAILED DIAGNOSIS section.

  • Typically, the detailed diagnosis of this test reports the top-10 (by default) queries to SAP HANA in terms of execution time. In many environments, it was noticed that the less critical background jobs (eg., Create, Alter, Backup etc.) hogged this top-10 list, because they normally take a long time to execute. The crucial user queries on the other hand, were often omitted from this top-10 list, as they usually take less time to execute than the background jobs. To enable administrators to focus on expensive user queries instead of background jobs, you can use the EXCLUDE EMPTY OBJECTS flag. By default, this flag is set to No. This means that, to identify the top-10 queries (in terms of execution time), this test will consider even those queries for which the output does not contain the object name. Since background jobs usually do not have object names in their output, this default setting implies that such jobs will by default be considered when generating detailed metrics. To disregard these jobs, set this flag to Yes. In this case, the test will only look at the execution time of those queries that return an output containing object names to generate the top-10 expensive queries list. This automatically excludes background jobs from detailed diagnosis.

  • If the value chosen for the ISPASSIVE 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.

  • To make diagnosis more efficient and accurate, the eG Enterprise suite 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 enable/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.
  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the Update button will 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 *ldquo;$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.