SAP Knowledge Base Article - Preview

2459847 - Change rs_ticket_history in HANA to timestamp- SRS


  • Replication setup from ASE (SAP Adaptive Server Enterprise) to HANA (A2H) or Oracle to HANA (O2H) using SAP Replication Server (SRS)
  • Can't monitor latency because rs_ticket_history is created with datetime columns as varchar(128) instead of HANA longdate.
  •  Here is an example:
    • CREATE TABLE  rs_ticket_history (cnt numeric(8,0),h1 varchar(10),h2 varchar(10),h3 varchar(10),h4 varchar(50),pdb varchar(30),prs varchar(30),rrs varchar(30),rdb varchar(30),pdb_t  varchar(128),
      exec_t varchar(128),dist_t  varchar(128),rsi_t varchar(128),dsi_t varchar(128),rdb_t  timestamp ,exec_b numeric(22,0),rsi_b numeric(22,0),dsi_tnx  numeric(22,0),dsi_cmd  numeric(22,0),ticket  varchar(1024))")



  • SAP Replication Server (SRS) 15.7.1
  • SAP Replication Server Heterogeneous Edition (RSHE) 15.7.1


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


rs_ticket, HANA timestamp, CR 790269, 790269 , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , BC-SYB-REP-HET , Replication Server Heterogeneous Edition (RSHE) , Product Enhancement

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.