Tibero Database Growth Test

Periodic monitoring of the usage of the database is essential to ensure that the database is always adequately sized to handle current and future loads. The Tibero Database Growth test monitors the usage of a managed Tibero database instance, and indicates if it requires resizing.

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.
Use Max Size	Set the Use Max Size flag to Yes, if you want the Free space in database, Space usage, and Space free measures of this test to be computed based on the maximum size up to which a database can grow. Set this flag to No, so that the aforesaid measures are computed based on the space allocated to a database.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total size of database	Indicates the total size of this database instance.	MB
Used space in database	Indicates the amount of database space that has been currently utilized.	MB
Free space in database	Indicates the amount of free space in this database instance currently.	MB	If the USE MAX size parameter of this test has been set to Yes, then the value of this measure will include the amount of allocated space that is still unused by the database and the amount of space that will be available to the database if more free space is added to it until its maximum size is reached. If the USE MAX size parameter of this test has been set to No, then the value of this measure will only indicate the amount of allocated space that is still unused by the database. In this case, the database's growth capacity will be disregarded.
Space usage	Indicates the percentage of database space that has been utilized.	Percent	If the USE MAX size parameter of this test has been set to No, then the value of this measure will be computed using the following formula: Used space/Total size of database * 100 If the USE MAX size parameter of this test has been set to Yes, then the value of this measure will be computed using the following formula: Used space/Maximum size up to which the database can grow * 100 Ideally, this value should be low. A value close to 100% is a cause for concern.
Space free	Indicates the percentage of free space in this database instance.	Percent	If the USE MAX size parameter of this test has been set to No, then the value of this measure will be computed using the following formula: Free space/Total size of database * 100 If the USE MAX size parameter of this test has been set to Yes, then the value of this measure will be computed using the following formula: Free space/Maximum size up to which the database can grow * 100 Ideally, this value should be high. A sudden/consistent decrease in the value of this measure could indicate excessive utilization of the database caused by a sporadic/steady increase in database activity. Very low free space in a database instance could significantly deteriorate its performance. Under such circumstances therefore, you might want to check the measures reported by the Tibero Datafile Growth test to figure out which datafile is consuming too much space. You might then want to resize the datafile.