Configuration of TibTimeWrkldTest

This test reports the current CPU usage of the server to indicate its current load. In addition, the test reveals the number and type of transactions the server processes every second, so that administrators can understand how well the server handles the load and can accurately identify where bottlenecks lie. By comparing the CPU usage of the server with its processing ability, administrators can intelligently figure out if the server requires additional CPU resources for improved performance.

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

• The port number to which the server is listening is to be provided in the PORT text box. By default, this will be 8629.

• In order to monitor a Tibero database server, a special database user account has to be created in every Tibero database instance that requires monitoring. A Click here hyperlink is available in the test configuration page, using which a new Tibero database user can be created. Alternatively, you can manually create the special database user. When doing so, ensure that this user is vested with the select any dictionary and create session privileges.

  The sample script we recommend for user creation for eG monitoring is:

  create user tibeg identified by tibeg default tablespace <users> temporary tablespace<temp>;
  grant create session, select any dictionary tibeg;

  The name of this user has to be specified in the USER text box, and the password of this user has to be entered in the PASSWORD text box. This login information is required to query Tibero's internal dynamic views, so as to fetch the current status / health of the various database components.

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

• Specify the SID of the target Tibero database instance that is to be monitored in the TIBERO SID text box.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button 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 "$" or contain a series of "*". A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.