Document Type | Technical Information
Category | Monitoring/Inspection
Applicable Product Version | Tibero7.2.3
Document Number | TMOTI064
Overview
This document describes how to configure Tibero to automatically perform a Callstack Dump when a specific error number occurs.
Method
1. Setting Automatic Callstack Dump
Using the following command, a Callstack Dump will be automatically generated when the specified specific error occurs.
ALTER SYSTEM DUMP CALLSTACK ON ERROR -number ON;
Note
In addition to the Callstack, sqlmemlog content can also be generated.
2. Disabling Automatic Callstack Dump
After confirmation, execute the following command to deactivate the automatic Callstack Dump setting.
ALTER SYSTEM DUMP CALLSTACK ON ERROR -number OFF;
Test
Test version: Tibero 7 FS02 (DB 7.2.3)
CREATE TABLE TEST_TABLE (C1 NUMBER PRIMARY KEY, C2 VARCHAR(10), C3 VARCHAR(10))
/
INSERT INTO TEST_TABLE VALUES (1, 'ABC', 'DEF')
/
INSERT INTO TEST_TABLE VALUES (2, 'ABC', 'DEF')
/
COMMIT
/
ALTER SYSTEM DUMP CALLSTACK ON ERROR -10007 ON
/
INSERT INTO TEST_TABLE VALUES (1, 'TEST', 'DATA');
/
TBR-10007: UNIQUE constraint violation ('TEST'.'_TEST_CON55100872'). occurred
Confirm memlog generation
TiberoVM@tibero7:/home/tibero/tibero7/instance/tibero/log/memlog # ll -rlt [testuser@testuser:tibero:/home/tibero/tblog/dump/memlog]ls -lart -rw-r-----. 1 testuser testgroup 48920 Oct 2 11:23 sql_memlog.2079.87.0
Confirm tbsvr.callstack generation
TiberoVM@tibero7:/home/tibero/tibero7/instance/tibero # ll -rlt
-rw-------. 1 testuser testgroup 16685 Oct 2 11:23 tbsvr.callstack.2082