Symptom
The message "Invalid token length encountered" may be reported in the SAP Replication Server log when a stored procedure is compiled with string values more bigger than Rep. Server can support. This would require to split the store procedure.
In the Replication Server log the following messages are raised:
*********************************
T. 2014/10/13 LTITRACE com.sybase.ra.lti.rs.LTLSession SQLException: : Line 1, character 101: Invalid token length encountered.: Error ID=2081; SQLState= null
E. xxxx/xx/xx xx:xx:xx.xxx ERROR com.sybase.ra.lti.rs.LTLSession Replication Server refused the following invalid LTL command; LTI thread is now stopping.
E. xxxx/xx/xx xx:xx:xx.xxx ERROR com.sybase.ra.lti.rs.LTLSession _ds 4 ~,A{0x}00000000ff0d00000b940019000003ff0000ff0c00001c74000200001c210150,6 ~,>{0x}53525756303132385f44432e636f625f72656d65736173051824ea0000 sqlddl _apd _fi last ~90$R
E. xxxx/xx/xx xx:xx:xx.xxx ERROR com.sybase.ra.lti.rs.LTLSession
E. xxxx/xx/xx xx:xx:xx.xxx ERROR com.sybase.ra.lti.rs.LTLSession create proc [dbo].[sp_pago_chq_tr_mas_local]
…
*********************************
Read more...
Environment
SAP Replication Server (RS) 15.7.1 SP203 and later.
Product
Keywords
limitation, RS string value length , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.