Document Type | Technical Information
Category | Administration
Applicable Product Versions | Tibero5, Tibero6, Tibero7
Document Number | TADTI218
Overview
This document describes a BMT scenario to verify the proper operation of the monitoring function in a SINGLE environment.
Method
Check whether query execution plans and statistics for queries or sessions are provided
Verify via the CLI client program screen or a separate trace file.
Execution
| Execution Order | Scenario |
|---|---|
| 1 | Create test table (TIBERO.PLAN_TEST) |
| 2 | Insert data into test table (TIBERO.PLAN_TEST) |
| 3 | Create index (TIBERO.PLAN_TEST_IDX) on test table (TIBERO.PLAN_TEST) |
| 4 | Enable viewing of query execution plan (PLAN) |
| 5 | Check query execution plan (PLAN) after running query |
| 6 | Enable separate trace for session statistics (execution time, IO) |
| 7 | Check separate trace after query execution |
Results
Execution Order | Scenario |
|---|---|
1 | Create test table (TIBERO.PLAN_TEST) |
tbsql TIBERO/TMAX CONNECTED TO TIBERO. CREATE TABLE PLAN_TEST(C1 NUMBER,C2 NUMBER, C3 NUMBER); | |
| 2 | Insert data into test table (TIBERO.PLAN_TEST) |
declare for i in 1..10000 loop insert into plan_test values(i,i,i); end; / PSM completed.
SQL> COMMIT; Commit completed. | |
| 3 | Create index (TIBERO.PLAN_TEST_IDX) on test table (TIBERO.PLAN_TEST) |
CREATE INDEX PLAN_TEST_IDX ON PLAN_TEST(C1); Index 'PLAN_TEST_IDX' created. | |
| 4 | Enable viewing of query execution plan (PLAN) |
SET LINES 200 SET AUTOT TRACEONLY EXP PLANSTAT | |
| 5 | Check query execution plan (PLAN) after running query |
select * from plan_test where c1 between 10 and 100; SQL ID: 63qt2v8qbnum4 Execution Plan
| |
| 6 | Enable separate trace for session statistics (execution time, IO) |
| set autot off; alter session set sql_trace=y; | |
| 7 | Check separate trace after query execution |
select * from plan_test where c1 between 10 and 100; C1 C2 C3
exit
cd $TB_HOME/instance/$TB_SID/log/sqltrace tbprof tb_sqltrc_2939_120_12145.trc result_trqce.log vi result_trqce.log TBPROF 7 TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. input file name : tb_sqltrc_2939_120_12145.trc ================================================================= |
Audit Function for DML and DDL Queries
Verify via the CLI client program screen or a separate trace file.
Execution
| Execution Order | Scenario |
|---|---|
| 1 | Set environment file (TIP) to enable audit function |
| 2 | Create test table (TIBERO.AUDIT_TEST) |
| 3 | Set DML audit on test table (TIBERO.AUDIT_TEST) |
| 4 | Set DDL audit on test table (TIBERO.AUDIT_TEST) |
| 5 | Perform DML and DDL queries on test table (TIBERO.AUDIT_TEST) |
| 6 | Check audit logs |
Results
| Execution Order | Scenario |
|---|---|
| 1 | Set environment file (TIP) to enable audit function |
| AUDIT_SYS_OPERATIONS=Y AUDIT_TRAIL=OS AUDIT_FILE_DEST=/home/tibero/audit | |
| 2 | |
tbsql sys/tibero tbSQL 7 TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. Connected to Tibero.
SQL> create table tibero.audit_test(id number); Table 'TIBERO.AUDIT_TEST' created. | |
| 3 | Set DML audit on test table (TIBERO.AUDIT_TEST) |
AUDIT insert on tibero.audit_test BY SESSION WHENEVER SUCCESSFUL; Audited.
AUDIT update on tibero.audit_test BY SESSION WHENEVER SUCCESSFUL; Audited.
AUDIT delete on tibero.audit_test BY SESSION WHENEVER SUCCESSFUL; Audited. | |
| 4 | Set DDL audit on test table (TIBERO.AUDIT_TEST) |
AUDIT create table by tibero; Audited. | |
| 5 | |
insert into tibero.audit_test values(1); 1 row inserted. commit; Commit completed.
update tibero.audit_test set id = 2; 1 row updated. commit; Commit completed.
delete from tibero.audit_test ; 1 row deleted. commit; Commit completed. | |
| 6 | Check audit logs |
| 2025/12/05 14:00:05.646 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[0] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[CONNECT] 2025/12/05 14:00:32.204 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[0] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[create table tibero.audit_test(id number)] 2025/12/05 14:01:21.744 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[0] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[AUDIT insert on tibero.audit_test BY SESSION WHENEVER SUCCESSFUL] 2025/12/05 14:01:33.535 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[0] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[AUDIT update on tibero.audit_test BY SESSION WHENEVER SUCCESSFUL] 2025/12/05 14:01:37.906 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[0] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[AUDIT delete on tibero.audit_test BY SESSION WHENEVER SUCCESSFUL] 2025/12/05 14:02:17.377 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[0] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[AUDIT create table by tibero] 2025/12/05 14:02:23.463 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[149] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[insert into tibero.audit_test values(1)] 2025/12/05 14:02:26.266 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[0] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[commit] 2025/12/05 14:02:30.960 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[151] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[update tibero.audit_test set id = 2] 2025/12/05 14:02:34.379 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[0] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[commit] 2025/12/05 14:02:38.706 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[153] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[delete from tibero.audit_test] 2025/12/05 14:02:40.802 110 SESS_ID:[110] SERIAL_NO:[90] STMT_ID:[0] USER_NAME:[SYS] USER_HOST:[127.0.0.1] OS_USER:[tibero] CLIENT_ID:[tbsql] PID:[3530] SQLTEXT:[commit] |
Check Support for GUI-Based DBMS Management Monitoring Tools
Execution
| Execution Order | Scenario |
|---|---|
| 1 | Session Monitoring |
| 2 | Transaction Monitoring |
| 3 | DBMS Instance Monitoring |
Results
| Execution Order | Scenario |
|---|---|
| 1 | Session Monitoring |
| 2 | Transaction Monitoring |
| 3 | DBMS Instance Monitoring |