Known Issues for Replication Agent

Known issues and workarounds for Replication Agent.

Replication Agent Issues
CR# Description
689941 RepAgent for SAP ASE handles some of the normalization errors from SAP Replication Server as warnings, which may result in data loss.

Workaround: Upgrade to SAP Replication Server 15.7 and later.

  • If you are using a version of SAP ASE earlier than 15.7, the RepAgent log may show incorrect normalization errors. For example:
    Column unknown.unknown status 'always_replicate' in replication definition does not match database status 'replicate_if_changed'.  Use 'alter replication definition' to set 'replicate_if_changed' status, at least until existing transactions have been processed.  (Refer to Troubleshooting Guide for recovery procedures.)
    See the accurate error information in the SAP Replication Server log. For example:
     E2011/11/16 09:17:11. ERROR #32057 REP AGENT(ost_replnxb9_32.pdb1) - /nrm/nrm.c(4175) 
           The value given for 'blurbs.copy' cannot be translated from datatype 'text_status' to the required datatype 'varchar'.
  • If you are using a version of SAP ASE later than 15.7, the RepAgent log shows the correct error information. For example, the RepAgent log shows:
    00:0002:00000:00018:2011/11/16 09:17:11.71 server  RepAgent(4): Received the following error message from the Replication Server: Msg 32057. The value given for 'blurbs.copy' cannot be translated from datatype 'text_status' to the required datatype 'varchar'.