Document Type | Technical Information
Field | Utility
Applicable Product Versions | 5, 6FS07, 6FS07PS, 7FS02, 7FS02PS
Document Number | TUTTI027
Overview
This document explains each menu of the engineer's Monitor Tool, Monitor Shell.
Method
Note
To check whether tm is installed, depending on the type of OS Shell, you need to verify if there is an alias in .profile or .bash_profile.
This document is based on tm version 1.4.3; features and output may differ by version.
5. SPACE
This menu allows you to check the size and usage of tablespaces and datafiles.
1) Database File Info
This menu displays the paths and sizes of files used by the database.
========================
Controlfile Infomation
========================
Control Files
---------------------------------------------------------------------------------------
/sdiske/ps1/pjha/tbdata7/c1.ctl
====================
Logfile Infomation
====================
Group# Member Type Size(MB)
-------- ------------------------------------------------------------ -------- ----------
0 /sdiske/ps1/pjha/tbdata7/redo01.log ONLINE 500
0 /sdiske/ps1/pjha/tbdata7/redo02.log ONLINE 500
1 /sdiske/ps1/pjha/tbdata7/redo11.log ONLINE 500
1 /sdiske/ps1/pjha/tbdata7/redo12.log ONLINE 500
2 /sdiske/ps1/pjha/tbdata7/redo21.log ONLINE 500
2 /sdiske/ps1/pjha/tbdata7/redo22.log ONLINE 500
=====================
Datafile Infomation
=====================
Tablespace Name File Name Size(MB) MaxSize(MB)
-------------------- ------------------------------------------------------------ ------------ ------------
SYSSUB /sdiske/ps1/pjha/tbdata7/syssub001.dtf 820 1,024
SYSTEM /sdiske/ps1/pjha/tbdata7/system001.dtf 5,120 10,240
TEMP /sdiske/ps1/pjha/tbdata7/temp001.dtf 10,240 32,768
UNDO0 /sdiske/ps1/pjha/tbdata7/undo001.dtf 10,240 32,768
USR /sdiske/ps1/pjha/tbdata7/usr001.dtf 3,072 10,240- Control Files: Displays the path of the controlfile.
- Group#: Displays the group to which the Redolog belongs.
- Member: Displays the path of the Redolog.
- Type: Displays whether the RedoLog is online.
- Tablespace Name: Displays the name of the tablespace.
- File Name: Displays the actual path of the datafile.
- Size(MB): Displays the current file size.
- MaxSize(MB): This value is shown when tablespaces are created with AUTOEXTEND enabled or when datafiles are added.
Note
When AUTOEXTEND occurs, the datafile size can only expand up to MaxSize(MB).
2) Tablespace Usage
This menu allows you to check the size and usage of each tablespace.
=======================
Tablespace Infomation
=======================
Tablespace Name Bytes(MB) Used(MB) Percent(%) Free(MB) Free(%) MaxBytes(MB) MAX_Free(%)
-------------------- ------------ ------------ ----------- ------------ -------- ------------ -----------
SYSSUB 820 815 99.39 5 .61 1,024 20.41
UNDO0 10,240 960 9.38 9,280 90.63 32,768 97.07
SYSTEM 5,120 105 2.05 5,015 97.95 10,240 98.98
USR 3,072 0 .00 3,072 100.00 10,240 100.00
============================
Temp Tablespace Infomation
============================
Tablespace Name Size(MB) MaxSize(MB)
-------------------- ---------------- ----------------
TEMP 10,240.00 32,768.00- Tablespace Name: Displays the name of the tablespace.
- Bytes(MB): Displays the size of the datafiles belonging to the tablespace.
- Used(MB): Displays the actual size occupied by data within the datafiles.
- Percent(%): Displays the usage percentage of the datafiles.
- Free(MB): Displays the amount of free space within the current datafile size.
- Free(%): Displays the percentage of free space within the current datafile size.
Note
If AUTO EXTEND is not set, it is recommended to secure at least 10% free space.
For Undo, since it is reused internally, it is recommended to add space only when a CANT_EXTEND error occurs during a transaction, not based on free space.
- MaxBytes(MB): Indicates the maximum size limit to which datafiles can extend according to AUTOEXTEND settings.
3) Undo Segment Usage
This menu allows you to check the usage of the Undo tablespace.
3-1) Current Undo Information
==========================
Current Undo Information
==========================
=================================
===== Undo Freespace =======
=================================
TABLESPACE_NAME TOTAL_SIZE(MB) USED_SIZE(MB) FREE_SIZE(MB) FREE_SIZE(%)
--------------- -------------- ------------- ------------- ------------
UNDO0 10240 479.53 9760.47 95.32
=================================
===== Undo Segment Info =======
=================================
SEGMENT_ID TABLESPACE_NAME STATUS EXTENTS RSSIZE(MB) CUREXT CURSIZE(MB) SHRINKS WRAPS EXTENDS XACTS
---------- --------------- --------------- ---------- ---------- ---------- ----------- ---------- ---------- ---------- ----------
0 SYSTEM ONLINE 2 16 0 8 0 0 0 0
1 UNDO0 ONLINE 2 16 0 8 0 0 0 0
2 UNDO0 ONLINE 2 16 0 8 0 0 0 0
3 UNDO0 ONLINE 2 16 0 8 0 0 0 0
4 UNDO0 ONLINE 2 16 0 8 0 0 0 0
... truncated- SEGMENT_ID: Displays the ID of the segment internally assigned when using Undo.
- TABLESPACE_NAME: Displays the name of the tablespace used for Undo operations. Operations performed internally by the SYS account or SYSTEM use the SYSTEM tablespace, while general user operations use the UNDO tablespace.
- STATUS: Displays the status of the segment as managed internally by the system during Undo segment management.
Note
ONLINE: The segment is active and can be used in transactions. If Undo segments are ONLINE or OFFLINE_PENDING, the Undo tablespace cannot be dropped.
OFFLINE: The segment cannot be used. For example, when switching from Undo tablespace A to B, segments created in A are marked OFFLINE.
OFFLINE_PENDING: Segments in use by transactions at the time of switching Undo tablespaces from A to B remain in OFFLINE_PENDING status until the transaction ends (commit/rollback).
- EXTENTS: Displays the number of extents (continuous blocks) allocated to the segment.
- RSSIZE(MB): Displays the size of the segment.
- CUREXT: Displays the ID of the extent currently used in the transaction.
- CURSIZE(MB): Displays the size of the segment currently used by the transaction.
- SHRINKS: Displays the number of times the segment has been shrunk.
- WRAPS: Displays the number of times the segment has been reused.
- EXTENDS: Displays the number of times the segment has been extended.
- XACTS: Displays the number of transactions using the segment.
3-2) Undo Segment Activity
Undoseg Activity COUNT
---------------------------- ----------
Online Undosegs Cnt 61
Active Undosegs Cnt 0
undo segment seqno reset 0
undo segment seqno overflow 0
- Online Undosegs Cnt: Displays the count of segments in the online state.
- Active Undosegs Cnt: Displays the count of segments currently in use.
- undo segment seqno reset: Displays the number of resets of the Undo segment sequence managed internally.
- undo segment seqno overflow: Displays the number of overflows of the Undo segment sequence managed internally.
3-3) Undo Block Per Sec
Displays the usage of UNDO BLOCK per second.
UNDO_BLOCK_PER_SEC
------------------
12.604
3-4) Necessary Undo Size
This menu shows the current size and estimated required usage of the Undo tablespace.
=================================
===== Necessary Undo Size =======
=================================
TABLESPACE_NAME Current UNDO SIZE(MB) UNDO RETENTION
--------------- --------------------- ----------------------------------------------------------------------------------------------------
Necessary UNDO SIZE(MB)
-----------------------
UNDO0 10240 1800
3- TABLESPACE_NAME: Only displays Undo tablespaces.
- Current UNDO SIZE(MB): Displays the current datafile size of the Undo tablespace.
- UNDO RETENTION: Displays the time Undo data is retained after transaction completion (unit: seconds).
- Necessary UNDO SIZE(MB): Displays the estimated minimum size of the Undo tablespace based on previous transaction usage. This may vary depending on transaction volume and frequency.
3-5) Undo Usage Type
This menu shows the Undo currently used by ongoing transactions.
=================
Undo Usage Type
=================
SID SERIAL# SEGMENT_ID SQL Type SQL_ID TABLESPACE_NAME USED_BLK CUREXT CURSIZE XACTS
---------- ---------- ---------- ---------- ---------------- --------------- ---------- ---------- ---------- ----------
20 3186 3 INSERT 77 UNDO 1 0 511 1- SID: Displays the session ID.
- SERIAL#: Displays the session serial number. Together with SID, it uniquely identifies the session.
- SEGMENT_ID: Indicates the Undo segment ID.
- SQL Type: Indicates the type of SQL.
- SQL ID: The ID of the SQL currently executed by the session.
- TABLESPACE_NAME: Displays the name of the Undo tablespace in use.
- USED_BLK: Displays the number of blocks used.
- CUREXT: Displays the current extent number in use.
- CURSIZE: Displays the size currently in use.
- XACTS: Displays the number of transactions using the segment.
4) Temp Segment Usage
This menu allows you to check the usage of the Temp tablespace.
4-1) Temp Segment Usage
Displays session information using the Temp tablespace.
====================
Temp Segment Usage
====================
SID USERNAME SQL_ID SEGTYPE TEMP(MB) SQL_TEXT
---------------------------------------------------------------------------------------------------------------------
20 TIBERO 161 SORT 17.56 select * from (select * from (select * from (select * from ( sel- SID: Displays the session ID.
- USERNAME: Displays the connected user's name.
- SQL_ID: Displays the ID of the SQL currently executed by the session.
- SEGTYPE: Displays the purpose of the Temp segment usage (SORT, HASH, ANALYTIC, INDEX, DATA, LOBDATA).
- TEMP(MB): Displays the size of the Temp segment used by the transaction.
- SQL_TEXT: Displays the SQL text of the transaction. Detailed information can be checked in the v$sqltext view using the SQL_ID.
4-2) Temp Total Usage
Displays the usage of the Temp tablespace.
====================
Temp Total Usage
====================
Temp Name Total(MB) Used(MB) Free(MB) Free(%) Max(MB)
----------------------------------------------------------------------
TEMP 1024.06 17.56 1006.5 98.3 0- Temp Name: Displays the name of the Temp tablespace.
- Total(MB): Displays the total size of the Temp tablespace.
- Used(MB): Displays the size of currently used segments.
- Free(MB): Displays the amount of free space in the Temp tablespace.
- Free(%): Displays the percentage of free space in the Temp tablespace.
- Max(MB): If Auto Extend is enabled, displays the maximum extendable size (0 means Auto Extend OFF).
6. I/O
Menus related to disk I/O.
1) File I/O Info
This menu shows File I/O (disk write/read) information for each datafile.
Note
When I/O concentration occurs on a specific disk among multiple disks, distributing the tablespace across multiple disks is advantageous for performance.
======================
File I/O Information
======================
TABLESPACE_NAME FILE_NAME PHYRDS PHYWRTS Read(%) Write(%) Total_I AvgTime(s
--------------- -------------------------------------------------- ------------ ------------ -------- -------- ------- ---------
SYSSUB /sdiske/ps1/pjha/tbdata7/syssub001.dtf 1,094 3,254 57.3 57.6 57.5 .010
SYSTEM /sdiske/ps1/pjha/tbdata7/system001.dtf 671 242 35.1 4.3 12.1 .007
UNDO0 /sdiske/ps1/pjha/tbdata7/undo001.dtf 143 2,155 7.5 38.1 30.4 .016
USR /sdiske/ps1/pjha/tbdata7/usr001.dtf 2 0 .1 .0 .0 .000
- TABLESPACE_NAME: Displays the name of the tablespace.
- FILE_NAME: Displays the path and file name of the datafile.
- PHYRDS: Displays the number of physical disk reads.
- PHYWRTS: Displays the number of physical disk writes.
- Read(%): Displays the percentage of total physical disk reads accounted for by the datafile.
- Write(%): Displays the percentage of total physical disk writes accounted for by the datafile.
- Total_IO(%): Displays the percentage of total physical disk I/O (read/write) accounted for by the datafile.
- AvgTime(s): Displays the average I/O response time. (Less than 0.01: Fast / Less than 0.05: Good / Less than 0.1: Slow / 0.1 or more: I/O inspection needed)
2) Session I/O Info
This menu shows I/O counts per session.
=========================
Session I/O Information
=========================
Sid User Program BLOCK_GETS CONSISTENT_GETS PHYSICAL_READS BLOCK_CHANGES CONSISTENT_CHANGES
------- --------------- ------------- ---------- --------------- -------------- ------------- ------------------
123 SYS tbsql 0 2 0 0 0- Sid: Displays the session ID.
- User: Displays the connected user's name.
- Program: Displays the type of client program connected.
- BLOCK_GETS: Displays the number of blocks read in Current Mode.
- CONSISTENT_GETS: Displays the number of blocks read in Consistent Read (CR) mode.
- PHYSICAL_READS: Displays the number of times data was read from disk.
- BLOCK_CHANGES: Displays the number of blocks changed in Current Mode.
- CONSISTENT_CHANGES: Displays the number of blocks changed in Consistent Read mode.
Note
Current Mode: Reading to modify actual data, e.g., DML.
Consistent Read mode: Reading with read consistency guaranteed, e.g., SELECT, subqueries in WHERE clause of DML.
3) Archive Log Count
In Archive Log mode, this menu shows the count of archive logs generated by date and hour (=Log Switch count).
=====================================
Archive Log Count (Archivelog Only)
=====================================
LOG HISTORY (Since Last Month)
-------------------------------------------------------------------------------------------------------
Hourly 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
-------------------------------------------------------------------------------------------------------
11/10| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 3| 0| 0| 0| 0| 0| 0| 0|
11/12| 0| 0| 0| 0| 0| 0| 0| 0| 1| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0|
11/25| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 1| 2| 0| 1| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0|
12/05| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 1| 0| 0| 0| 0| 0| 0| 0|
[ARCHIVED LOG COUNT : 9]7. OBJECT
This menu allows you to check object information.
1) Schema Object Count
This menu shows the count of objects per schema.
=====================
Schema Object Count
=====================
OWNER OBJECT_TYPE COUNT
-------------------- ----------------------- ----------
LBACSYS INDEX 30
LBACSYS PACKAGE 14
LBACSYS PACKAGE BODY 13
LBACSYS PROCEDURE 2
LBACSYS SEQUENCE 5
LBACSYS TABLE 23
LBACSYS TYPE 5
LBACSYS TYPE BODY 4
LBACSYS VIEW 50
OUTLN INDEX 1
OUTLN TABLE 4
PUBLIC SYNONYM 1192
SYS DIRECTORY 3
SYS FUNCTION 7
SYS INDEX 361
SYS INDEX PARTITION 540
SYS JAVA 1
SYS LOB 17
SYS PACKAGE 131
SYS PACKAGE BODY 72
SYS SEQUENCE 34
SYS SQL TRANSLATION PROFILE 2
SYS SYNONYM 1
SYS TABLE 540
SYS TABLE PARTITION 405
SYS TRIGGER 2
SYS TYPE 96
SYS TYPE BODY 1
SYS VIEW 337
SYSCAT VIEW 425
SYSGIS FUNCTION 1
SYSGIS INDEX 2
SYSGIS PROCEDURE 2
SYSGIS TABLE 2
SYSGIS VIEW 6- OWNER: Displays the owner of the object (=user name).
- OBJECT_TYPE: Displays the type of the object.
- Count: Displays the count of objects.
2) Object Invalid Count
This menu shows the count of objects in an invalid state.
Owner Object type Status Count
-------------------- -------------------- ------- ----------
PUBLIC SYNONYM INVALID 1
SYSGIS PROCEDURE INVALID 1
- OWNER: Displays the owner of the object (=user name).
- OBJECT_TYPE: Displays the type of the object.
- Status: Displays the status of the object (if Invalid, recompilation or recreation is needed).
- Count: Displays the count of objects.
3) Object Invalid Object
This menu shows information on objects in an invalid state.
OWNER Object type Object name Status Last DDL Time
-------- ------------- --------------------------- ------- -------------------
SYSGIS PROCEDURE REGISTER_SPATIAL_REF_SYS INVALID 2015-11-21 08:21:49- OWNER: Displays the owner of the object (=user name).
- OBJECT_TYPE: Displays the type of the object.
- Object name: Displays the name of the object.
- Status: Displays the status of the object (if Invalid, recompilation or recreation is needed).
- Last DDL Time: Displays the last time a DDL was executed on the object.
4) Segment Size (Top 50)
This menu shows the top 50 segments by size in use, owned by users excluding SYS, SYSGIS, and SYSCAT accounts.
Owner Segment Name Segment Type Tablespace Name Extents Size(MB)
-------------------- --------------- ------------------ -------------------- ------------ ------------
TIBERO TEST TABLE USR 111 379
OUTLN OL$HINTS TABLE USR 1 0
TIBERO TBL1 TABLE USR 1 0
TIBERO LINEITEM TABLE USR 1 0
OUTLN OL$ TABLE USR 1 0- Owner: Displays the segment owner (=user name).
- Segment Name: Displays the name of the segment.
- Segment Type: Displays the type of the segment.
- Tablespace Name: Displays the name of the tablespace to which the segment belongs.
- Extents: Displays the number of extents used by the segment.
- Size(MB): Displays the size of the segment.
8. SQL
This menu allows you to check information related to SQL.
1) SQL Plan (Input SQL_ID)
This menu allows you to check the execution plan using the SQL_ID.
2) Top SQL
This menu displays the top 10 SQL statements based on execution time, block gets, and average execution time.
USERNAME Elapsed_Time(s) EXECUTIONS Gets/Exec Elap/Exec(s) MODULE SQL_ID
----------- --------------- ---------- ---------- ------------ --------------- ----------------
TIBERO 8.105 1 47979 8.105 tbsql@npaudb01 161
TIBERO 7.542 1 47979 7.542 tbsql@npaudb01 160
TIBERO 1.735 1 0 1.735 tbsql@npaudb01 159
SYS .5 2 17038 .25 tbAdmin@Tmax-PC 44
SYS .361 2 52249.5 .181 APM SESSION 132- USERNAME: Displays the user name who executed the transaction.
- Elapsed_Time(s): Displays the total execution time.
- EXECUTIONS: Displays the total number of executions.
- Gets/Exec: Displays the number of blocks read per execution during the transaction.
- Elap/Exec(s): Displays the average execution time per execution.
- MODULE: Displays the connected client information.
- SQL_ID: Displays the ID of the executed SQL.
- BUFFER_GETS: Displays the number of blocks read.
3) Check Static Query Pattern
This menu checks whether SQL statements with the same first 40 characters are repeatedly executed multiple times.
9. TPR
Menu for using the APM feature for performance analysis.
1) Create TPR Snapshot
Creates a DB snapshot at the current time.
2) Create TPR Snapshot for TAC
Creates snapshots for all TAC instances at the current time.
3) Show TPR Snapshot
Displays information about snapshots stored in the DB.
3-1) TPR Snapshot List
INS INSTANCE_NAME STARTUP_TIME
--- ------------------------- -------------------
0 jh_tibero 2025/12/08 08:36:26
- INSTANCE_NUMBER: Displays the instance number of the DB. For TAC, numbers differ by node.
- INSTANCE_NAME: Displays the instance name of the DB.
STARTUP_TIME: Displays the startup date of the DB.
INS INSTANCE_NAME STARTUP_TIME
--- ------------------------- -------------------
0 jh_tibero 2025/12/08 08:36:26
Enter the number of days of snapshots : 3
=> Enter how many days of snapshot information to view starting from today- INSTANCE_NUMBER: Displays the instance number of the DB. For TAC, numbers differ by node.
- INSTANCE_NAME: Displays the instance name of the DB.
STARTUP_TIME: Displays the startup date of the DB.
THR SNAP_ID BEGIN_INTERVAL_TIME END_INTERVAL_TIME
--- ---------- ------------------- -------------------
0 29 2025/12/05 16:56:19 2025/12/05 17:56:15
0 30 2025/12/05 17:56:15 2025/12/05 18:56:15
0 31 2025/12/05 18:56:15 2025/12/05 19:56:15
0 32 2025/12/05 19:56:15 2025/12/05 20:56:15
- THREAD#: Displays the instance number.
- SNAP_ID: Displays the snapshot ID, used when generating reports.
- BEGIN_INTERVAL_TIME: Displays the start time of the DB information stored in the snapshot.
- END_INTERVAL_TIME: Displays the end time of the DB information stored in the snapshot.
4) Create TPR Report
Generates a report using stored snapshot information.
===================
TPR Report Create
===================
INS INSTANCE_NAME STARTUP_TIME
--- ------------------------- -------------------
0 jh_tibero 2025/12/08 08:36:26
Enter the number of days of snapshots : 1
=> Enter how many days of snapshot information to view starting from today
old value : where begin_interval_time >= sysdate - &last_day
new value : where begin_interval_time >= sysdate - 1
THR SNAP_ID BEGIN_INTERVAL_TIME END_INTERVAL_TIME
--- ---------- ------------------- -------------------
0 94 2025/12/08 10:36:29 2025/12/08 11:36:29
0 95 2025/12/08 11:36:29 2025/12/08 12:36:29
0 96 2025/12/08 12:36:29 2025/12/08 13:36:29
Create TPR Report?(Y/N): Y
=> Decide whether to create the report
Enter begin snapshots ID : 91
=> Enter the snapshot ID for the report start time
Enter end snapshots ID : 91
=> Enter the snapshot ID for the report end time
old value : where snap_id = &begin_snap_id;
new value : where snap_id = 91;
old value : where snap_id = &end_snap_id;
new value : where snap_id = 91;
Create TPR Report : 2025-12-08 06:56:16 ~ 2025-12-08 07:56:15
[TPR report] 'tpr_report.jh_tibero.20251208_140911.txt' completed!
/sdiske/ps1/pjha/tibero7/instance/jh_tibero/tpr_report.jh_tibero.20251208_140911.txt
-> Displays the path and name of the generated report file
10. OTHER
Other menus.
10.1 M - Auto Refresh Monitoring
- This menu is used when periodic monitoring is needed for specific tasks. .
10.2 S - Save To File
- This menu allows you to query various information about the current DB state and save it to a file.
10.3 I - Setting SQL_ID Format
- This menu changes the format displayed in each menu.
10.4 X - EXIT
- Command to exit the tm program.