Professional Documents
Culture Documents
Asap Hana Aq & Aa PDF
Asap Hana Aq & Aa PDF
2. What is SLT?
The full form of SLT is SAP Landscape Transformation which is nothing but a trigger based replication. It
is the replication technology to pass the data from the source system to the target system. Here the source
can be either SAP or non-SAP whereas the Target system is SAP HANA system which contains HANA
database.
3. Can we load and replicate data from one source system to multiple target database
schemas of HANA system?
Yes. It can be loaded and replicated for up to 4.
6. Is there any need of pre-requisite before creating the configuration and replication?
DMIS add-on is installed in SLT replication server for SAP source systems. The role
IUUC_REPL_REMOTE is assigned to the user for RFC connection but not DDIC. DMIS add-on is not
required and grants a database user sufficient authorization for data replication for a non-SAP source
system.
9 Define Latency?
Latency is the length of time to replicate data (a table entry) from the source system to the target system.
13. What are the factors that influence the change/increase the number of jobs?
The factors that influence the change or increase in the number of jobs are number of configurations
managed by the SLT replication server, number of tables to be loaded/ replicated for each configuration,
expected speed of initial load, expected replication latency time. As a thumb rule, one BDG job should be
used for each 10 tables in replication to achieve acceptable latency times.
16. State the relation between the number of data transfer jobs in the configuration
settings and the available BGD work processes?
In SLT replication server each job occupies 1 BGD work processes and for each configuration, the
parameter Data Transfer Jobs would restrict the maximum number of data load job for each mass
17. If the parameter set for “data transfer jobs” to 04 in a configuration “SCHEMA1”, a
mass transfer ID 001 is assigned. In such a case what jobs should be in the system?
The jobs should be 1 Master job (IUUC_MONITOR_SCHEMA1), 1 Master Controller job
(IUUC_REPL_CNTR_001_0001) and at most 4 parallel jobs for MT_ID 001
(DTL_MT_DATA_LOAD_001_ 01/~02/~03/~04)
If at the same time lots of tables are selected for load / replication, there could be a chance that there are
not enough background jobs available to start the load procedure for all tables immediately. In such a case
the number of initial load jobs can be increased, or else tables will be handled sequentially.
For tables with large volume of data the transaction “Advanced Replication Settings
(IUUC_REPL_CONT)” to further optimize the load and replication procedure for dedicated tables can be
used.
20. If the replication is suspended for a long period of time or system outage of SLT or
HANA system what would happen?
The size of the logging tables increases.
21. How can unnecessary logging information from being stored be avoided?
Unnecessary logging information storage can be avoided by pausing the replication which is by stopping
the schema-related jobs.
22. Are the table size in SAP HANA database and in the source system the same?
No they are not same as HANA database supports compression.
25. If the source system is non-SAP system, are there any special considerations?
The trigger-based replication concept is actually meant for SAP source systems. The main differences are
as below :
a) There would be a database connection between non-SAP source and SLT system instead of RFC.
b) Source must have primary key
c) Tables DD02L, DD02T which contains metadata are just initially loaded but not replicated.
d) The read modules resides on SLT system.
e) Tables with database specific formats may need transformation rules just before they are replicated.
27. How is it ensured that data is consistent in source system and HANA system?
Since any changes in the source system that occurs is tracked in the dedicated logging tables, the
replication status for each changed data record will be transparent. An entry of logging table is deleted
after an every successful commit statement from HANA database and this procedure ensures the data
consistency between source system and HANA system.
28. Does SLT for SAP HANA support data compression like SAP HANA database?
Yes SLT for SAP HANA supports data compression like SAP HANA database and this is automatically
covered by the RFC connection used for data replication from the SAP sour.
40. State the 10:1 compression with HANA when compared to Oracle?
When a typical uncompressed Oracle or Microsoft SQL Server database is put into HANA, it will be 10x
smaller than before and this is because of the way that HANA stores information in a compressed
format. Most databases are now compressed and these numbers may not fit every scenario, and to add to
this 2x the RAM as your database is needed including a plus room for growth. Sizing of HANA is still a
dark art.
49. For batch loads what source databases does HANA support?
If SAP BusinessObjects Data Services 4.0 is used for bulk loads then it would be the best. BO-DS is a very
flexible Extract, Transform & Load tool that can support many databases