SAP Knowledge Base Article - Preview

2679792 - RADB2 owner qualification causes Invalid token length encountered - SRS

Symptom

When setting the QUALIFY column to 'Y' in LTMOBJECTS causes the following ERROR in the LTMCONN output of the SAP Replication Agent for DB2 MVS (RADB2):

LTM02008 - msgno: '  2081', severity: '  12', message:
LTM02013 - MSG: Line 1, character 388: Invalid token length encountered.
LTM02010 - ct_command failed cmd= 'get truncation edsel.radb2db2t  '
LTM02024 - LTMOC GETTRUNC call failed.

The following errors can be seen in the SAP Replication Server (SRS) errorlog:

Replication Agent for edsel.radb2db2t connected in language mode.
Replication Agent version (770) for 'ds.db' does not match the default LTI version for this Replication Server 791 using version 770.
Replication Agent for ds.db connected in language mode.
The LTL stream buffer's contents: (50 characters printed per line)
L001:
L001:
L001:
L001:
L001:
L001:
L001: xC4C2F2E30000000000030000000000D4BFEC3520040000000
L001: 400D4BFEC352003868A0000,3 8 _ap owner=~DNEW
ERROR #2081 REP AGENT(ds.db) - generic/prs/prstok.c(614)
        Line 1, character 388: Invalid token length encountered.

OR

The LTL stream buffer's contents: (50 characters printed per line)
L001: ��
L001:
L001:
L001: ~!*rs_insert _yd _a
 ERROR #2056 REP AGENT(ds.db) - de/generic/prs/sql.y(26658)
Line 1, character 770: Incorrect syntax with '~'.

OR

Thread REP AGENT(ds.db) infected with signal 11.
.diag(linux_dump_all_func_stack+0x32) [0xbbff64]
.diag(dbg_dump_stack_noarg+0x25) [0xc03c29]
.diag(dbg_dump_stack+0x3c5) [0xc03557]
.diag(exc__appDumpStack+0x1f6) [0x881542]
.diag(exc_terminate+0x47d) [0x88a597]
.diag(linux_catch_signal+0x674) [0x5d5a54]
/lib64/libpthread.so.0() [0x32f720f790]
/lib64/libc.so.6() [0x32f6f34bfc]
.diag(_prs_dump_ltl_buffer+0x246) [0xa931e6]
.diag(_prs_get_token+0xc4b) [0xaad4db]
.diag(yylex+0x5d1) [0xa9389b]
.diag(yyparse+0xec) [0xb15db8]
.diag(prs_parse_sql+0x110) [0xb15984]
.diag() [0x8a4495]
.diag(_ex_process_lang+0x405d) [0x8a1d09]
.diag(ex_lang_handler+0x303d) [0x893157]
.diag(srv__exechandler+0xf8) [0xd6bdb4]
.diag(srv__runclient+0x585) [0xd6b8d4]
.diag(srv__connhandle+0x308) [0xd8146c]
.diag(srv__start_function+0x2fa) [0xd71c35]
/lib64/libpthread.so.0() [0x32f7207a51]
/lib64/libc.so.6(clone+0x6d) [0x32f6ee89ad]
*****End of stack trace.****
Internal error. Attempting to produce a core file.
'Replication Server/16.0/EBF 27617 SP03 PL03 rs160sp03pl03/Linux AMD64/Linux 2.6.32.59-0.19-default x86_64/2214/DEBUG64/Tue Dec 19 19:04:30 2017'


Read more...

Environment

  • SAP Replication Agent, option for IBM DB2 version 15.0 SP08
  • SAP Replication Server (SRS) version 15.7.1 and 16.0

Product

SAP Replication Agent 15.0, option for IBM DB2 ; SAP Replication Server 15.7 ; SAP Replication Server 16.0

Keywords

RADB2, QUALIFY, owner, RepServer, DB2, schema, invalid, syntax, stack , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , BC-SYB-REP-DB2MF , Replication Agent for DB2 MF , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.