SAP Knowledge Base Article - Preview

2494421 - Failed to assert 'name[0] != 0' at 11395, 'generic/prs/packer.c'. - replication issue to MQ - SAP REP

Symptom

  1. Tried rebooting all components – Replication Server, EAServer and Repconnectors.
    • ‘sysadmin log_first_tran’ but nothing written to the exceptions log.
    • ‘dump queue’ and ‘dump tran’ report the message:
      Failed to assert 'name[0] != 0' at 11395, 'generic/prs/packer.c'
  2. Zapped two transactions which clears the transaction but the next gets stuck.
  3. The interesting thing is that we see only two commands in each of these transactions which should be
    Begin tran
    Work to be done
    Commit
  4. Does the repconnector work the same way as normal ASE replication? 

    56 Awaiting Message     140 XXX_repcon2.mq                                    0           0          15          15           0           0           0 st:O,cmds:2,qid:17881:45:2                              0           0            0             0
    58 Awaiting Message     141 XXX_repcon6.mq                                    0           0          17          17           0           0           0 st:O,cmds:2,qid:2084:33:44                              0           0            0             0
  5. We are seeing the following messages in the EAServer –

[RUNTIME]: 2017-06-23 08:06:08,259 [INFO] [REPRA.RepraConnectionImpl]: Successfully started connection XXX_repcon1.
[XXX_repcon2]: 2017-06-23 08:06:12,372 [ERROR] [REP.DataServer]: No Rep Subscription.
[RUNTIME]: 2017-06-23 08:06:13,314 [INFO] [REPRA.RepraConnectionImpl]: Successfully started connection XXX_repcon2.
[XXX_repcon3]: 2017-06-23 08:06:16,371 [ERROR] [REP.DataServer]: No Rep Subscription.
[RUNTIME]: 2017-06-23 08:06:17,339 [INFO] [REPRA.RepraConnectionImpl]: Successfully started connection XXX_repcon3.
[XXX_repcon4]: 2017-06-23 08:06:20,696 [ERROR] [REP.DataServer]: No Rep Subscription.
[RUNTIME]: 2017-06-23 08:06:21,663 [INFO] [REPRA.RepraConnectionImpl]: Successfully started connection XXX_repcon4.
[RUNTIME]: 2017-06-23 08:06:25,405 [INFO] [REPRA.RepraConnectionImpl]: Successfully started connection XXX_repcon5.
[XXX_repcon6]: 2017-06-23 08:06:28,950 [ERROR] [REP.DataServer]: No Rep Subscription.
[RUNTIME]: 2017-06-23 08:06:29,905 [INFO] [REPRA.RepraConnectionImpl]: Successfully started connection XXX_repcon6.
[XXX_repcon2]: 2017-06-23 08:35:02,670 [ERROR] [REP.DSISession]: A message has been dropped silently by ReplicateDB.operation.    

  1. Why doesn’t the ‘log_first_tran’, ‘dump_queue’ or ‘dump tran’ work?  We see the same issue with replicating to Oracle which means we are flying blind when it comes to problematic transactions.

Read more...

Environment

SAP Replication Server

Product

SAP Replication Server 15.7 ; SAP Replication Server 16.0 ; Sybase Replication Server 15.5

Keywords

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 ONE Support launchpad (Login required).

Search for additional results

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