Document Type | Technical Information
Category | Monitoring/Inspection
Applicable Product Versions | 6FS07, 6FS07PS, 7FS02, 7FS02PS, 6FS07, 6FS07PS, 7FS02, 7FS02PS
Document Number | TMOTI004
Overview
This guide explains how to extract ilog using tbiv and key parameters related to ilog.
ilog
ilog is an abbreviation for Internal Log, a file that records system logs for events set per thread.
It provides more detailed information than slog.
It provides more detailed information than slog.
ilog content is stored in binary format, and tbiv must be used to view ilog logs.
tbiv
tbiv is a utility that converts the binary ilog file so users can check its contents.
Method
tbiv Options
| Option | Description |
|---|---|
| -x | Extract ilog format to ilog_fmtmap.bin file; this file is required to view on another server |
| -o | Specify output file (default: stdout) |
| -l | Split output file by specified size (Mb) |
| -T | Do not output time |
| -k | Display system tick |
| -s | Display sequence number |
| -i | Check ilog file information |
| -r | Keep only specified interval in output file (YYYYMMDDHH24MISS ~ YYYYMMDDHH24MISS) |
Usage Examples
1. Check sys log to find the thread (session id).
[2025-05-07T13:24:18.215148] [DDL-89] [I] Executing DDL: create table t (c number) [2025-05-07T13:24:18.231006] [DDL-89] [I] DDL execution succeeded [2025-05-07T13:24:34.358752] [FRM-89] [I] THROW. ec=ERROR_NUMBER_INVALID_NUMBER(-5074) [ Given string does not represent a number in proper format. ] [2025-05-07T14:24:04.215148] [DDL-89] [I] Executing DDL: create table s (c number) [2025-05-07T14:24:04.231006] [DDL-89] [I] DDL execution succeeded [2025-05-07T14:24:12.358752] [FRM-89] [I] THROW. ec=ERROR_NUMBER_INVALID_NUMBER(-5074) [ Given string does not represent a number in proper format. ]
2. Extract the ilog corresponding to the thread id from the ilog path using tbiv.
[tibero@ENT-ROCKY8 ilog]$ ls -alrt |grep 89 -rw-r--r--. 1 tibero tibero 65536 Apr 24 07:21 tibero-189.ilg -rw-r--r--. 1 tibero tibero 8781824 May 7 14:27 tibero-89.ilg Perform tbiv on ilg number 89 [tibero@ENT-ROCKY8 ilog]$ tbiv -o test.txt tibero-89.ilg - using only the -o option Tibero Internal Log Viewer (7 r292332, little-endian) TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. Completed. [tibero@ENT-ROCKY8 ilog]$ tbiv -o test2.txt -r 20250507140000 20250507143000 tibero-89.ilg - using -r option to specify a time range Tibero Internal Log Viewer (7 r292332, little-endian) TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. Completed.
3. Check the tbiv extracted files.
[test.txt] 05/07 13:24:18.2 0-0089 ddl_fram:230 Executing DDL: create table t (c number) 05/07 13:24:18.2 0-0089 tx_sgmt.:2601 sgmt create: ts=0 sgmt=4460 type=1 extsz=16 blksz=8192 05/07 13:24:18.2 0-0089 tx_sgmt.:2088 sgmt creation completed. ts=0 sgmt=4460 type=1 extsz=16, extdba=00_00013815 05/07 13:24:18.2 0-0089 ddl_tabl:506 create dsgmt(tbl) obj_id:4460 sgmt_id:4460 05/07 13:24:18.2 0-0089 ddl_fram:269 DDL execution succeeded 05/07 13:24:34.2 0-0089 tbsvr_er:181 THROW. ec=ERROR_NUMBER_INVALID_NUMBER(-5074) [ Given string does not represent a number in proper format. ] (sql_id:fn8wyr324hzaq, sub_sql_id:fn8wyr324hzaq, user:SYS, ap_module:(null), program:tbsql, host:ENT-ROCKY8) [number.c:963:number_from_str_ctx] [test2.txt] Only logs for the specified time range 2025/05/07 14:00 ~ 2025/05/07 14:30 are output. 05/07 14:27:04.3 0-0089 ddl_fram:230 Executing DDL: create table s (c number) 05/07 14:27:04.3 0-0089 tx_sgmt.:2601 sgmt create: ts=0 sgmt=4461 type=1 extsz=16 blksz=8192 05/07 14:27:04.3 0-0089 tx_sgmt.:2088 sgmt creation completed. ts=0 sgmt=4461 type=1 extsz=16, extdba=00_00013831 05/07 14:27:04.3 0-0089 ddl_tabl:506 create dsgmt(tbl) obj_id:4461 sgmt_id:4461 05/07 14:27:04.4 0-0089 ddl_fram:269 DDL execution succeeded 05/07 14:27:12.5 0-0089 tbsvr_er:181 THROW. ec=ERROR_NUMBER_INVALID_NUMBER(-5074) [ Given string does not represent a number in proper format. ] (sql_id:730p0jh9bh6u2, sub_sql_id:730p0jh9bh6u2, user:SYS, ap_module:(null), program:tbsql, host:ENT-ROCKY8) [number.c:963:number_from_str_ctx]
ilog Parameters
| Parameter | Description | Default Value (As of 7.2.3) |
|---|---|---|
ILOG_BACKUP_SIZE_LIMIT | Total size limit for backed-up ilog files | (MAX_SESSION_COUNT + 150) * (ILOG_FILE_SIZE) |
ILOG_DEST | ilog creation path | $TB_HOME/instance/$TB_SID/ilog |
ILOG_FILE_BACKUP_ON_BOOT | Whether to create ilog backup and back up existing files on startup | YES |
ILOG_FILE_SIZE | Size limit per ilog file; when this size is exceeded, the file is renamed and a new file is created | 10MB |
ILOG_KEEP_BACKUP_ASIDE | Whether to manage ilog backup size separately; if set to Y, it is managed separately from ILOG_TOTAL_SIZE_LIMIT | NO |
ILOG_TOTAL_SIZE_LIMIT | Total size of ilog files plus ilog backups | ((MAX_SESSION_COUNT + 150) * (ILOG_FILE_SIZE) * 2) |
USE_ILOG | Whether to use ilog | YES |