Tibero Datafile I/O Test

If a Tibero datafile is able to process I/O requests to it quickly, it is a sign of the good health of the Tibero database server. On the other hand, any slowdown in IOPS could indicate a serious processing bottleneck on the server, probably caused by a poor indexing engine or badly structured tables in a datafile. Administrators should hence continuously track the I/O requests to every datafile on the Tibero database server, and measure the time taken by that datafile to process the requests. For this purpose, you can run the Tibero Datafile I/O test!

This test auto-discovers the datafiles on the Tibero database server and reports the time taken by each datafile to process I/O requests. In the process, I/O processing bottlenecks can be detected and the datafiles affected can be identified.

Target of the test : A Tibero Database server

Agent deploying the test :An internal agent

Outputs of the test : One set of results for every datafile on the target database server.

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
Read rate	Indicates the rate at which this datafile was read during the last measurement period.	Reads/sec	A scenario in which more than 50% of blocks are being read from a single datafile could signify a problem.
Write rate	Indicates the rate at which disk blocks were written to this datafile during the lsat measurement period.	Writes/sec	A scenario in which more than 50% of blocks are being written to a single datafile could signify a problem. Too much activity to a specific datafile can result in reduced database performance. To improve performance, consider balancing I/O across disks, and reorganize tables across tablespaces to reduce activity to a specific datafile.
Total I/O	Indicates the percentage of total I/O operations on the database server that were handled by this datafile.	Percent	Disk reads and writes are expensive operations and all I/Os should be balanced across the different data files of the database for optimal performance. This metric reports the percentage of all I/O of the database that are happening on each of the data files of the Tibero database. This metric allows the database administrator to determine which is/are the hot data file(s) (e.g., which data file is handling 80% of the total I/O).
Average I/O time	Indicates the average time taken by the I/O operations on the database server that were handled by this datafile.	Seconds	A high value could indicate a processing bottleneck with the datafile. Compare the value of this measure across datafiles to identify that datafile to which the read/write requests take too long to be serviced.
Average read time	Indicates the average time taken for disk block reads from this datafile during the last measurement period.	Seconds/read	A very high value of this measure could indicate a bottleneck when processing disk block write requests to a particular datafile. Compare the value of this measure across files to accurately identify that datafile from which block of data was read most slowly.
Average write time	Indicates the average time taken for disk block writes from this datafile during the last measurement period.	Seconds/write	A very high value of this measure could indicate a bottleneck when processing disk block write requests to a particular datafile. Compare the value of this measure across files to accurately identify that datafile to which block of data was written most slowly.