First part of this blog can be found here:
*SAP SLT (Trigger Based) Replication Made Easy – part 1: Planning,
Second part of this
series is coverering Post-Installation activities – applying SAP corrections,
creating connection between source system and SAP HANA database, adjusting
security and data provisioning.
Note: This blog was written before the release of special SLT SP05 for SAP HANA. I was considering postponing release date of this blog to have updated information but decided not to do so. During SAP TechEd I cannot test new SLT version and update would take at least two weeks. (And this blog was already postponed several times.)
activation of service iuuc_replication_config and how to add it to the
favorites menu is well described in SAP guide.
Review SAP note
1605140 – SAP HANA 1.0: Central Note – SAP LT Replication Server for
corrections that need to be implemented.
references to the special support SLT package SP04 as it has been replaced by regular
Following SAP notes have
to be implemented via SNOTE:
1607754: Corrections for DMIS 2010_1_700 SP4
Especially the second SAP
note is very important as it fixes a lot of bugs.
Additional SLT corrections
You should consider importing following corrections:
0.1. SAP Note 1612292
– HANA LTR – corrections for DMIS 2010 SP4 072011
0.2. SAP Note 1614355
– HANA LTR – corrections for DMIS 2010 SP4 072611
0.3. SAP Note 1614775
– HANA replication: system problems not correctly handled
0.4. SAP Note 1619759
– HANA LTR corrections cluster table & delete of logging tab
0.5. SAP Note 1623278
– HANA LTR – corrections for DMIS 2010 11-08-22
0.6. SAP Note 1625136
– SAP LT Replicator – Structure changes, Spool & Synonym
0.7. SAP Note 1641061
– HANA LTR – corrections for DMIS 2010 SP4 11/10/13
0.8. SAP Note 1644239
– Correction for SLT Replicator for HANA 1.0 Generation error
Not all SAP notes are
currently planned to be part of SP05. Therefore some of them should be
implemented even in case you have SP05.
You will encounter
warnings during implementation of SAP Note 1619759. Reason is that this note
and SAP Note 1614355 are containing same adjustments. Four blocks were already
implemented by the first note and one block cannot be found due to adjustment
made by SAP note 1614355 (which is prerequisite note). This is an error in the note definition and after deeper analysis it is apparent that it can be safely ignored. Problematic correction
is just adding empty line. Enable checkbox to include IUUC_CREATE_COBJS_IF_TBL_ENTRY
report into implementation and confirm.
SLT configuration does
not need to be done in production client (in case that SLT is installed into
source system). SLT is always reading data using RFC destination therefore it
can be configured in different client (for example 000).
WebDynpro application IUUC_REPLICATION_CONFIG you need to create new schema.
Each replicated SAP
system must have its own schema in HANA (SLT will automatically create this
schema as part of connection definition therefore it must not exist in HANA
system beforehand). All replicated objects will be stored only in this schema.
It is recommended to
use SLT schemas only for objects replicated from corresponding SAP systems – no
additional objects should be created there (see the security blog for more
In our case we will
use schema name DATA_SLT_IDD800.
In order to create SLT
connection between source system and HANA you need to provide corresponding
information (details are explained in SAP guide).
Number of replay jobs
amount of replay jobs do not forget to make sure that you have enough
background work processes.
For each configured
SAP system you should have at least (6+n) background work
processes where n is amount of replay jobs (jobs used by SLT will be
explained in subsequent blogs).
Database connection to HANA
Be sure to provide
only hostname without port specified.
Provided user must be
user SYSTEM. Any other entry will lead to generic error “Error when creating
Click “Save” or “Save
and Close” and do not perform any actions until initial replication is finished
Provisioning – first steps
Procedure how to
launch Data Provisioning is explained is SAP guide.
Reliability of Data Provisioning screen information
SAP HANA does not have
ability to connect to SLT system nor to source system. All information you are
presented in this screen is taken from local tables stored in HANA database that
are regularly updated by SLT system.
This also means that
all actions done from Data Provisioning screen are not sent to SLT system but
are stored locally until SLT system will retrieve them.
5.4.2 Waiting for the end of initial
SLT replication is
working in cycles. Initial replication needs several cycles to perform all
required actions (which can take up to 10 minutes). I strongly recommend to
wait until initial replication is finished otherwise you risk breaking SLT
You can detect that
initial replication is finished by refreshing Data Provisioning screen and
waiting for both technical tables (DD02L and DD02T) to be in status In Process.
*Do not attempt to perform any actions to “fix”
status of these tables – SLT is most probably working well but takes some time.*
Note: If the initial
replication is taking more than 15 minutes then you probably have problem and
you need to troubleshootthe SLT.
You can validate
successful replication by clicking button Replicate. You should see list of
security to allow access for other users
Prerequisite for this
chapter is understanding security concept as explained in my previous blogs:
*SAP HANA – Security
Concept and Data Architecture (part 1)*
*SAP HANA – Security
Concept and Data Architecture (part 2)*
5.5.1 Allowing other users to see replicated
GRANT SELECT ON SCHEMA DATA_SLT_IDD800 TO SYSREPO WITH GRANT OPTION7.) Restart the replication in SLT</p>
<p>Release the monitoring
job that you created before (IUUC_MONITOR_<schema>) – use option Immediate.</p>
<p>8.) Check the system log for errors
5.5.2 Allowing other users to manage
By default only user
that was used for creation of connection definition is allowed to control
replication (user SYSTEM). All other users will see following error: