Tibero Database File Status Test
This test reports the status of each datafile in each database of a Tibero Database instance and the current access mode of every datafile.
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.
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. |
Measurement | Description | Measurement Unit | Interpretation | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
File status |
Indicates the current status of this datafile. |
Number |
The table below indicates the values that this measure can report and their corresponding numeric equivalents:
If a datafile is part of the SYSTEM tablespace, its status is SYSTEM (unless it requires recovery). If a datafile in a non-SYSTEM tablespace is online, its status is ONLINE. If a datafile in a non-SYSTEM tablespace is offline, its status can be either OFFLINE or RECOVER. Note: By default, this measure reports the above-mentioned Measure Values while indicating the current status of a datafile. However, in the graph of this measure, data file states will be represented using the corresponding numeric equivalents only - i.e., 1 to 4. |
||||||||||
File access mode |
Indicates the current access mode of this datafile. |
|
The table below indicates the values that this measure can report and their corresponding numeric equivalents:
Note: By default, this measure reports the above-mentioned States while indicating the mode through which this data file can be accessed. However, the graph of this measure will be represented using the corresponding numeric equivalents i.e., 0 to 3. |