Skip to main content
๐Ÿ““ Tibero Online Manual Click here ๐Ÿ““

Search

Welcome to Tibero GTS!

Repeated Internal Error Occurrences Due to Condition '!"invalid itl flag"'

Document Type | Troubleshooting

Category | Monitoring/Inspection

Applicable Product Version | 6FS06

Document Number | TMOTS010

 

Issue

If an abnormal ITL (Interested Transaction List) value is recorded in a block, an Internal Error with condition '!"invalid itl flag"' error may occur.
 
Error Messages in sys.log
[2023-10-16T21:08:39.403152] [COM-669] [I] Internal Error with condition '!"invalid itl flag"' (tx_cr.c:770) (pid=266737, sessid=669, tid=669, os_thr_id=267265)
[2023-10-16T21:08:53.207415] [COM-143] [I] Internal Error with condition '!"Background thread exited abnormally!"' (tbsvr_cthr.c:3082) (pid=266737, sessid=143, tid=143, os_thr_id=266737)

Error Messages in tbsvr.out File
[669] 2023/10/16 21:08:39.403 Internal Error with condition '!"invalid itl flag"' (tx_cr.c:770) (pid=266737, sessid=669, tid=669, os_thr_id=267265)
[669] client : ip [] process [] logon time : []
[669] prev sql : "NULL"
[669] current sql : "NULL"
[669] *** 2023/10/16 21:08:39.403 ***
[669] callstack dump from tbsvr_ACSD for [CMPT508, 669, 267265/266737]
[669] SEE DUMP tbsvr.callstack.266737 (lwpid 267265) BY PSTACK
================================
Thread #669 (Session #669): tb_thread_exit: (signo:0, sigtype:15)
Tibero: wthr killed. (pid=266737, tid=669 spinlock cnt=1)
[143] 2023/10/16 21:08:53.207 Internal Error with condition '!"Background thread exited abnormally!"' (tbsvr_cthr.c:3082) (pid=266737, sessid=143, tid=143, os_thr_id=266737)
[143] client : ip [] process [] logon time : []
[143] prev sql : "NULL"
[143] current sql : "NULL"
[143] *** 2023/10/16 21:08:53.207 ***
[143] callstack dump from tbsvr_ACSD for [ACSD, 143, 266737/266737]
[143] SEE DUMP tbsvr.callstack.266737 (lwpid 266737) BY PSTACK

 

Cause

During the processing of a consistent read request, while searching for a block requiring cleanout, a thread assert occurred because the flag value of the blockโ€™s ITL was not between 0 and 4.
The flag value of a blockโ€™s ITL must always be a value between 0 and 4.
 
 

Solutions

To perform an accurate root cause analysis, dump information of the problematic block is required, and for this, applying patch FS06_328015a is necessary.
 
This patch includes a feature that checks the dstream's file descriptor (fd) and uses a debug stream if the value is -1.
Caution
Apply the patch through technical support provided by Tmax Tibero.

 

 

 

Related to