Default Parameters for TibTranWrkldTest

This test reports how many key database operations - eg., data modifications, block changes, reads/writes, parses, rollbacks, etc. - are performed on the server per transaction. This way, the test reveals the real workload of the server. In addition, the test also enables administrators to compare current CPU usage with the real workload, so that they can figure out whether/not the server needs to be resized to handle its load.

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

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

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

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.