Skip to main content

Search

Welcome to Tibero GTS!

Occurrence of ERROR_LOB_INVALID_LOCATOR(-26009)

Document Type | Troubleshooting

Category | Interface/Integration

Applicable Product Versions | 6FS01, 6FS02, 6FS03, 6FS04, 6FS05, 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS, 5SP1FS06

Document Number | TIITS010

 

Issue 

This explains the occurrence of the ERROR_LOB_INVALID_LOCATOR(-26009) error in sys.log.
The ERROR_LOB_INVALID_LOCATOR error occurs in the following two cases.
  • When querying a lob column using a client tool (Dbeaver)
  • When querying long (long raw) columns in tbsql
[sys.log]
[08-26T21:45:44.351917] [FRM-95] [I] THROW. ec=ERROR_LOB_INVALID_LOCATOR(-26009) [ Invalid LOB locator specified.] (csr_id:4294967295) [tbsvr_msg_lob.c:490:tbsvr_msg_lob_delete_temp]
[08-26T21:45:44.352409] [FRM-95] [I] THROW. ec=ERROR_LOB_INVALID_LOCATOR(-26009) [ Invalid LOB locator specified.] (csr_id:4294967295) [tbsvr_msg_lob.c:490:tbsvr_msg_lob_delete_temp]
[08-26T21:45:44.352965] [FRM-95] [I] THROW. ec=ERROR_LOB_INVALID_LOCATOR(-26009) [ Invalid LOB locator specified.] (csr_id:4294967295) [tbsvr_msg_lob.c:490:tbsvr_msg_lob_delete_temp]

 

 

Cause

  • The client tool cannot identify the LOB type and always sends a free request, causing a general error when the LOB is not a temp LOB in the DB.
  • When querying long type columns in tbsql, the issue occurs because a temp LOB deletion message is sent regardless of whether it is a temp LOB or not.
 
 
 

Solutions

Apply the patch to resolve the issue. (Applied patches: FS06_CS_244092a, 233991a_jdbc )
Caution
Apply the patch through technical support provided by Tmax Tibero.
Note
From Tibero 6 FS07PS version and above, this issue is already included by default, so this error does not occur.
 
 
 
 
 
 
 

Related to