The SAP Replication Server (SRS) is a sophisticated Data Movement technology that will deliver transactional data across business boundaries, in real-time. SRS supports a variety of data sources and targets including Oracle and SAP HANA as shown in Figure 1.

scn_oracle_to_HANA_license_keys.png

Figure 1

As part of the configuration and setup of the Oracle to HANA replication environment a key step is to install the licenses that will enable the replication path from source to target. Three license keys are required to enable replication, they are:

  1. License key for the Source Oracle (installed with the Replication Agent for Oracle)
  2. License key for the Replication Server (installed in SRS)
  3. License key for the Target HANA connectivity (installed in SRS)

NOTE: A connector called the Express Connect for HANA (ECH) is built into SRS for connectivity to the target HANA. These license keys will have to be generated from SAP Service Market Place (SMP).

A Fictitious Example of these three License Keys is presented below (<HOSTID> is where the actual MAC address will be and <HOSTNAME> is where the actual hostname will be).

Source Oracle: (User can choose the Replication Option for Oracle in the License Key generation process, to generate this key for the Replication Agent for Oracle)

# Sybase Software Asset Management License File. CP License for SAP Sybase

# Replication Server Option, version for Oracle

PACKAGE REP_ORACLE SYBASE COMPONENTS=”RAO_SERVER DC_ORACLE \

     REP_EC_ORA” OPTIONS=SUITE SUPERSEDE ISSUED=29-nov-2015 \

     SIGN2=”1EF8 E77D 1888 5988 4807 E41B 729C 4A10 74C3 1F44 0C1A \

     55C4 2148 CD89 C7E7 0D33 CC8B 2E5F F021 46BB E2C7 478A BBC1 \

     8133 547C 9B9C 8A8E 2D80 3B7B 83D2″

# License for <HOSTID> <HOSTNAME>

INCREMENT REP_ORACLE SYBASE 2017.04300 30-apr-2017 uncounted \

     VENDOR_STRING=PE=EE;LT=CP HOSTID=<HOSTID> \

     ISSUER=”CO=Sybase, Inc.;V=15.0;MP=548;CP=1;EGO=” \

     ISSUED=29-nov-2015 NOTICE=”SAP Internal License Key” \

     SN=1-1843-OW212799 TS_OK SIGN2=”11BF 4520 0F36 510B B299 0BC0 \

     72CD 86D0 BFFE 4B35 0F66 6988 B8F9 5E22 33F6 15D0 3D0D 55F4 \

     9448 4916 ECE3 89BF 19C8 4ED9 F6D0 0CF7 7C5A 397B 0435 1E03″

Replication Server: (User can choose the Replication Server in the License Key generation process, to generate this key for the Replication Server)

# Sybase Software Asset Management License File. CP License for SAP Sybase

# Replication server

PACKAGE REP_EE SYBASE COMPONENTS=”REP_SERVER REP_ASE” OPTIONS=SUITE \

     SUPERSEDE ISSUED=01-dec-2015 SIGN2=”1A30 250A E979 0D09 B9CD \

     6A59 0233 8CF9 89EB 9FD2 13E1 34C6 D07F F820 C85C 1909 56FF \

     25AC D27C 7E17 21F1 F1FE A949 3822 CA60 611A 7849 AE62 0A69 \

     CDAB”

# License for <HOSTID> <HOSTNAME>

INCREMENT REP_EE SYBASE 2017.04300 30-apr-2017 uncounted \

     VENDOR_STRING=PE=EE;LT=CP HOSTID=<HOSTID> \

     ISSUER=”CO=Sybase, Inc.;V=15.0;MP=548;CP=1;EGO=” \

     ISSUED=01-dec-2015 NOTICE=”SAP Internal License Key” \

     SN=1-1837-OW212968 TS_OK SIGN2=”01ED 88CB 63F5 3CF5 8014 03A4 \

     C909 E737 9B87 4B38 04F7 A9BE 7FEC 145A D81F 0059 0DB8 97A1 \

     E7A5 3BE8 6CF4 C120 5D2E F468 8F2C B192 3299 56E4 2E5A 1E29″

Target HANA: (User can choose the Replication Option for HANA in the License Key generation process, to generate this key for the ECH connector. REP_EC_HANA is the enablement for the target via Express Connect)

# Sybase Software Asset Management License File. CP License for SAP Sybase

# Replication Server Option for SAP HANA

PACKAGE REP_HANA SYBASE COMPONENTS=”REP_EC_HANA RAH_SERVER” \

     OPTIONS=SUITE SUPERSEDE ISSUED=29-nov-2015 SIGN2=”1C0C 8349 \

     1C3C 6AC3 AD3A 0F96 C7CD 7B52 32D9 AA8C 49D6 AD75 0C98 6EFA \

     A733 1777 E91B 4F2A EF89 2732 6C1F 7A96 823B 9CE6 C664 2F8D \

     D903 D260 1E30 2732″

# License for <HOSTID> <HOSTNAME>

INCREMENT REP_HANA SYBASE 2017.04300 30-apr-2017 uncounted \

     VENDOR_STRING=PE=EE;LT=CP HOSTID=<HOSTID> \

     ISSUER=”CO=Sybase, Inc.;V=15.0;MP=548;CP=1;EGO=” \

     ISSUED=29-nov-2015 NOTICE=”SAP Internal License Key” \

     SN=1-1502-OW212800 TS_OK SIGN2=”156C 8C86 921D 85D9 EEE1 AAFE \

     0B69 0A13 13EF B973 4868 3412 8696 72A8 5781 0F41 7494 8FA2 \

     078B 742D B0A1 26CB 240F 60D0 0796 E2FB E0B5 83B7 E369 5D6C”

Resources

Replication to HANA:

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00783.1571200/doc/html/har1388650004754.html

http://scn.sap.com/community/services/blog/2013/06/16/replicating-data-to-hana-using-sap-sybase-replication-server

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01974.1571110/doc/html/bde1355001071038.html

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00783.1571202/doc/html/jer1353984593397.html

https://www.youtube.com/watch?v=EDEDKvk_ZCY

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Nicholas Chang

    Hi Arun Sitaraman


    I’ve went thru SRS materials and would like to clarify points below which are unclear to me:


    i) SRS support warm db standby, site-to-site replication. Thus, it means we can replicate the entire supported primary databases (oracle, db2 udb, msssql, ase) to SAP HANA?


    ii) 15.7.1 SP200 – Replication Agent support HANA2HANA replication, therefore can whole primary HANA DB replicate to secondary HANA DB instead of just schema replication? Or is it only possible to achieve by replicate every schema in primary HANA (eg: SAPSID, SYS, SYSTEM, _SYS* and etc) to target HANA?


    Thanks,

    Nicholas Chang

    (0) 
    1. Arun Sitaraman Post author

      Hi Nicholas,

      The SAP Replication Server supports warm standby configuration between two ASE or two Oracle databases (providing a link to the Administration Guide below).

      SyBooks Online

      For ASE warm standby configuration please read:

      http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01251.1571200/doc/html/nro1268213411114.html

      For Oracle warm standby configuration please read:

      http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc36924.1571100/doc/pdf/rshetrep.pdf

      Best,

      Arun

      (0) 
      1. Nicholas Chang

        Hi Arun,

        Thanks for the highlight. I’m confused with the info on the link provided as well as the info in SRS Q4/2015 roadmap.

        Do you mean SRS only support warm standby for “oracle” and “ase” as this moment? How about HANA?

        Also, as for site to site replication, i assume as we can perform FULL DB replication (supported source) to HANA, as migration purpose?

        Apart from that, we can also replicate FULL DB (all tables within its schema) via replication agent from HANA2HANA?

        Thanks,

        Nicholas Chang

        (0) 
        1. Arun Sitaraman Post author

          Hi Nicholas,

          Today, warm standby support is available for ASE and Oracle only. We do not have warm standby (site) support for HANA to HANA via Replication Agent for Oracle (RAH is different from Replication Server).

          Replication Server HANA2HANA implementation is best for data offloading for reporting. SLT is a better fit for HANA2HANA use cases, and especially for Business Suite.

          Best,

          Arun

          (0) 
          1. Nicholas Chang

            Hi Arun,

            Thanks for the clarification. However, as far as i understand, SLT ony support table replication and not site-2-site migration? Correct me if i’m wrong.

            Unless you talk about system replication. But sadly, system replication is not work between power8 machine to x86 yet.

            Thanks,

            Nicholas Chang

            (0) 

Leave a Reply