Document Type | Technical Information
Category | Monitoring/Inspection
Applicable Product Versions | 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS
Document Number | TMOTI015
Overview
This guide explains how to extract the query causing an error through a callstack dump when a specific error is repeatedly logged in sys.log but the query information is not recorded.
Method
[2025-05-30T16:43:00.929537] [FRM-88] [I] THROW. ec=ERROR_NUMBER_INVALID_NUMBER(-5074) [ Given string does not represent a number in proper format.] (csr_id:70) [number.c:980:number_from_str_ctx]
When an error like the one above occurs periodically in sys.log, the method to identify the query causing this error is as follows.
Syntax Example
alter system dump callstack on error -error_number on;
Example Application
SQL> alter system dump callstack on error -5074 on; System altered.
Afterwards, you can check the executed query within the dump file.
How to Check Dump File Creation Path
- Default path: $TB_HOME/instance/$TB_SID/dump/tracedump/
- Check the parameter specified in the tip file (Parameter name: TRACE_DUMP_DEST)
- Find the dump file path in tbsql SQL> show param TRACE_DUMP_DESTTRACE_DUMP_DEST /home/tibero/tibero7/instance/hwtibero/dump/tracedump/
Cautionโป Since excessive dumps may occur for frequently occurring errors, turn off the dump using the query below after obtaining the desired dump.SQL> alter system dump callstack on error -15114 off; System altered.
NoteOnly one error number can be specified at a time, and even if multiple commands are executed, dumping is performed only for the last applied error; therefore, dumping must be done separately for each error.SQL> alter system dump callstack on error -15114 on; System altered. SQL> alter system dump callstack on error -5074 on; System altered.Although the system was altered, only the dump for the last executed error 5074 can be confirmed.