Tibero SQL Network Test

Using the JDBC API, this test reports the availability and responsiveness of the server, and collects statistics pertaining to the traffic into and out of the database server.

Target of the test : A Tibero Database server

Agent deploying the test :An internal agent

Outputs of the test : One set of results for each target database server being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The port to which the specified host listens. By default, the port number is 8629.
User and Password	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 Password	Confirm the Password by retyping it here.
Tibero SID	Specify the SID of the target Tibero database instance that is to be monitored in this text box.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Tibero server availability	Indicates whether the databaSse instance is responding to requests.	Percent	The availability is 100% when the instance is responding to a request and 0% when it is not. Availability problems may be caused by a misconfiguration/malfunctioning of the database instance, or because the instance is using an invalid user account. Besides the above, this measure will report that the server is unavailable even if a connection to the database instance is unavailable, or if a query to the database fails. In this case, you can check the values of the Conn_availability and Query processor availability measures to know what is exactly causing the database instance to not respond to requests - is it owing to a connection unavailability? or is it due to a query failure?
Total response time	Indicates the time taken by the database to respond to a user query. This is the sum total of the connection time and query execution time.	Secs	A sudden increase in response time is indicative of a bottleneck at the database server. This could even be owing to a connection delay and/or long running queries to the database. Whenever the value of this measure is high, it would be good practice to compare the values of the Connection time to database server and Query execution time measures to zero-in on the root-cause of the poor responsiveness of the server - is it because of connectivity issues? or is it because of inefficient queries?
Database connection availability	Indicates whether the database connection is available or not.	Percent	If this measure reports the value 100, it indicates that the database connection is available. The value 0 on the other hand indicates that the database connection is unavailable. A connection to the database may be unavailable if the database is down or if the database is listening on a port other than the one configured for it in the eG manager or owing to a poor network link. If the ibero server availability measure reports the value 0, then, you can check the value of this measure to determine whether/not it is due to the unavailability of a connection to the server.
Connection time to database server	Indicates the time taken by the database connection.	Secs	A high value could indicate a connection bottleneck. Whenever the Total response time soars, you may want to check the value of this measure to determine whether a connection latency is causing the poor responsiveness of the server.
Query processor availability	Indicates whether the database query is executed successfully or not.	Percent	If this measure reports the value 100, it indicates that the query executed successfully. The value 0 on the other hand indicates that the query failed. In the event that the Tibero server availability measure reports the value 0, check the value of this measure to figure out whether the failed query is the reason why that measure reported a server unavailability.
Query execution time	Indicates the time taken for query execution.	Secs	A high value could indicate that one/more queries to the database are taking too long to execute. Inefficient/badly designed queries to the database often take too long to execute. If the value of this measure is higher than that of the Connection time to database server measure, you can be rest assured that long running queries are causing the respond slowly to requests.
Records fetched	Indicates the number of records fetched from the database.	Number	The value 0 indicates that no records are fetched from the database.