SAP Knowledge Base Article - Preview

2048822 - The sysadmin log_first_tran command doesn't always log the correct transaction - SRS

Symptom

The syadmin log_first_tran doesn't match the transaction the DSI is reporting the error on. Error example and output:

  • I. 2014/07/08 12:12:11. The DSI thread for database 'SERVER.dbname' is started.
  • E. 2014/07/08 12:12:11. ERROR #5150 DSI EXEC(113(1) SERVER.dbname) - /dsiexec.c(6163) Function 'rs_get_textptr' for 'tableA' returned multiple rows.
  • When the first tran gets logged, this is what is reported (table tableB NOT table tableA as reported by DSI error):

    rs_helpexception 129,v;

            Detailed Summary of Logged Transaction # 129      on 'REPSRVR'


    Origin Site                    Origin User     Org. Commit Date  #Cmds in Xact
    ------------------------------ --------------- ----------------- -------------
    SERVER.dbname                 user          Jul  8 2014  8:41             4

    Dest. Site                     Dest. User      Date Logged
    ------------------------------ --------------- -----------------
    SERVER.dbname                 dbname_maint   Jul  8 2014 11:42

    This transaction was logged by the 'sysadmin log_first_tran' command.


Read more...

Environment

SAP Replication Server (SRS) 15.6 ESD#3 and higher

Product

SAP Replication Server 15.7 ; SAP Sybase Replication Server 15.7, heterogeneous edition

Keywords

rs_helpexception , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Bug Filed

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.