Tibero Datafiles Test

This test indicates the level of activity on a specific datafile in terms of the rate of physical reads and physical writes.

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.


The host for which the test is to be configured.


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.


This test reports a set of results for each datafile on the target Tibero database server. This means that every datafile is a descriptor of this test. By default, while displaying the descriptors of this test, the eG monitoring console does not prefix the datafile names with the full path to the datafiles. This is why, the IncludePath flag is set to No by default. If you want the data file names to be prefixed by the full path to the data files, then, set the IncludePath flag to Yes.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Physical block read rate

Indicates the rate at which disk blocks are being read from this datafile.


A scenario in which more than 50% of blocks are being read from a single datafile could signify a problem.

Physical block write rate

Indicates the rate at which disk blocks are being written to this datafile.


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.

Percent total I/O

Indicates the percentage of total I/O operations on the database server that were handled by a data file.


Disk reads and writes are expensive operations and all I/Os should be balanced across the different data files of an Tibero database for optimal performance. This metric reports the percentage of all I/O of an Tibero database that are happening on each of the data files of the Tibero database. This metric allows an Tibero administrator to determine which is/are the hot data file(s) (e.g., which data file is handling 80% of the total I/O).