Skip to main content

Search

Welcome to Tibero GTS!

Issue of DB Instance Forced Termination During UDF (User Defined Function) Usage

Document Type | Troubleshooting 

Category | Installation

Applicable Product Version | 6FS07

Document Number | TINTS006

 

Issue

During execution of UDF (User Defined Function), the DB instance may be forcibly terminated intermittently.
 
Example of related logs output when DB instance terminates abnormally
[02-05T13:10:43.676767] [FRM-144] [I] Signal 'SIGSEGV'(11) caught (TID = 144, OS_THR_ID = 7696, PID = 7554): si_addr = 0000000000000018 : the cause of the signal can be found in a process callstack file. 
[02-05T13:10:47.711271] [FRM-144] [I] THROW. ec=ERROR_SESS_KILLED(-12001) [ Session has been closed. ] (csr_id:3105) [tbsvr_signal.c:1610:sync_sig_handler] 
[02-05T13:33:57.330821] [COM-144] [I] Internal Error with condition '!"Signal caught in a critical section: DB instance must be shut down. " "The cause which generated the signal can be found " "in a process callstack file."' (2 args) (tbsvr_signal.c:1474:sync_sig_handler) (pid=7554, sessid=144, tid=144)


 

Cause

When the Result Cache feature is used in functions (PSM), a memory leak occurs, and this issue appears only when using the DETERMINISTIC clause.
During PSM execution, the memory allocated for the result block is not properly released, causing a memory leak.
 
 

Solutions

1. Apply the FS07_CS_227927b patch.

Caution

Apply the patch through technical support provided by TmaxTibero.

 

2. Disable the Result Cache feature by setting PSM_SQL_RESULT_CACHE=N. (Can be applied dynamically)
Note
You can bypass this issue by removing the DETERMINISTIC clause within the PSM before use.
 
 
 

Related to