Configuration of HanaRepServiceTest

This test auto-discovers the secondary servers that are communicating with the target database server and for each secondary server, this test reports the amount of data that needs to be currently replicated. This test also throws light on the time taken for completing the replication and the time that elapsed since the last delta replication /last full replication were initiated on each secondary server. In addition, the difference in log position and savepoint log position between each primary server and the secondary server is reported. Using this test, administrators can determine the secondary server that is up to-date with the primary server and on which the replication is completed successfully.

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, specify the IP address of the host for which this test is to be configured.

• In the PORT text box, specify the port number at which the specified HOST listens. By default, this 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 password grant monitoring to

  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.

  • 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.

  • 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 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.

  • 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.