Symptom
- Replication Agent (for Oracle or MS SQL Server) is dropping out of "Replicating" mode.
- You are seeing the following messages:
- Replication Server refused the following invalid LTL command; LTI thread is now stopping
- SQM had an error writing to the inbound-queue.
- In the repagent log there is a stacktrace similar to:
E. ERROR com.sybase.ra.lti.rs.LTLSession Replication Server refused the following invalid LTL command; LTI thread is now stopping.
E. ERROR com.sybase.ra.lti.rs.LTLSession _ds 4 ~,A{0x}0006000c86ed00003ca7000300000400000c86ed00003ca7000200003ca60004,6 ~,C{0x}57494e5649415353514c30312e653067625f625f63617073616e7465a359471d0000 _bg _tr for ~"'E0GBTP osid 164
E. ERROR com.sybase.ra.lti.rs.LTLSession SQM had an error writing to the inbound-queue.
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.jdbc3.jdbc.SybSQLException: SQM had an error writing to the inbound-queue.
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.jdbc3.tds.Tds.processEed(Unknown Source)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.jdbc3.jdbc.SybStatement.executeLoop(Unknown Source)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.jdbc3.rstds.RSStatement.execute(RSStatement.java:183)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.jdbc3.rstds.RSStatement.write(RSStatement.java:211)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.ra.lti.rs.LTLSession.executeLTLBuffer(LTLSession.java:1083)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.ra.lti.rs.LTLSession.rs_send_ltl_command(LTLSession.java:1233)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.ra.lti.rs.LTLSession.rs_send_ltl_commands(LTLSession.java:1181)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.ra.lti.rs.LTLSession.rs_send_ltl_batch(LTLSession.java:1156)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.ra.lti.rs.LTLSession.distribute(LTLSession.java:939)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.ra.lti.LTIDistributeThread.sendBatch(LTIDistributeThread.java:223)
E. ERROR com.sybase.ra.lti.rs.LTLSession com.sybase.ra.lti.LTIDistributeThread.run(LTIDistributeThread.java:131)
E. ERROR com.sybase.ra.lti.rs.LTLSession java.lang.Thread.run(Thread.java:662)
I. INFORMATION com.sybase.ra.lti.LTIThreadManager LTI Thread Manager received notification that thread LTI <RS Distribution> completed with <com.sybase.ra.lti.LTIException> exception.
Read more...
Environment
- SAP Replication Server (RS)
- SAP Replication Server Heterogeneous Edition
- SAP Replication Server Option for Oracle
- SAP Replication Server Option for Microsoft SQL Server
- Sybase Replication Server
- Sybase Replication Server Heterogeneous Edition
Product
Keywords
RAX, RAM, RAO , KBA , BC-SYB-REP-RSO , Rep Server Options (RSO) , BC-SYB-REP-HET , Replication Server Heterogeneous Edition (RSHE) , 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.
SAP Knowledge Base Article - Preview