T h u r s d ay, 1 2 O c to b e r 2 0 1 7

SAP HANA Interview Questions and Answers

1.What are the different types of replication techniques?

1.ETL based replication using BODS
2.Trigger based replication using SLT
3.Extractor based data acquisition using DXC
4. SDI
2.What is SLT?
SLT stands for SAP Landscape Transformation which is a trigger based replication.
SLT replication server is the replication technology to pass data from source
system to the target system. The source can be either SAP or non-SAP. Target
system is SAP HANA system which contains HANA database.
3.Is it possible to load and replicate data from one source system to
multiple target database schemas of HANA system?
Yes. It is possible for up to 4.
4.Is it possible to specify the type of data load and replication?
Yes either in real time, or scheduled by time or by interval.
5.What is Configuration in SLT?
The information to create the connection between the source system, SLT
system, and the SAP HANA system is specified within the SLT system as a
Configuration. You can define a new configuration in Configuration & Monitoring
Dashboard (transaction LTR).
6.Is there any pre-requisite before creating the configuration and
replication?
For the SAP source systems DMIS add-on is installed in SLT replication server.
User for RFC connection has the role IUUC_REPL_REMOTE assigned but not DDIC.
For non-SAP source systems DMIS add-on is not required and grant a database
user sufficient authorization for data replication.
7.What is Configuration and Monitoring Dashboard?
It is an application that runs on SLT replication server to specify configuration
information (such as source system, target system, and relevant connections) so
that data can be replicated. It can also use it to monitor the replication status
(transaction LTR).
Status Yellow: It may occur due to triggers which are not yet created successfully.
Status Red: It may occur if master job is aborted (manually in transaction SM37).
8.What is advanced replication settings?
A transaction that runs on SLT replication server to specify advanced replication
settings like
Modifying target table structures,
Specifying performance optimization settings
Define transformation rules
9.What is Latency?
It is the length of time to replicate data (a table entry) from the source system to
the target system.
10.What is logging table?
A table in the source system that records any changes to a table that is being
replicated. This ensures that SLT replication server can replicate these changes
to the target system.
11.What are Transformation rules?
A rule specified in the Advanced Replication settings transaction for source tables
such that data is transformed during the replication process. Example you can
specify rule to
Convert fields
Fill empty fields
Skip records
12.What happens when you set-up a new configuration?
The database connection is automatically created along with GUID and Mass
transfer id (MT_ID).
A schema GUID ensures that configurations with the same schema name can be
created.
The Mass transfer ID is used in the naming of SLT jobs and the system can
uniquely identify a schema.
13.What factors influence the change/increase the number of jobs?
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 rule of thumb, one BDG job should be
used for each 10 tables in replication to achieve acceptable latency times.
14.When to change the number of Data Transfer jobs?
If the speed of the initial load/replication latency time is not satisfactory
If SLT replication server has more resources than initially available, we can
increase the number of data transfer and/or initial load jobs
After the completion of the initial load, we may want to reduce the number of
initial load jobs
15.What are the jobs involved in replication process?
1. Master Job (IUUC_MONITOR_<MT_ID>)
2. Master Controlling Job (IUUC_REPLIC_CNTR_<MT_ID>)
3. Data Load Job (DTL_MT_DATA_LOAD_<MT_ID>_<2digits>)
4.Migration Object Definition Job (IUUC_DEF_MIG_OBJ_<2digits>)
5.Access Plan Calculation Job (ACC_PLAN_CALC_<MT_ID>_<2digits>)
16.What is the relation between the number of data transfer jobs in the
configuration settings and the available BGD work processes?
Each job occupies 1 BGD work processes in SLT replication server. For each
configuration, the parameter Data Transfer Jobs restricts the maximum number
of data load job for each mass transfer ID (MT_ID).
A mass transfer ID requires at least 4 background jobs to be available:
One master job
One master controller job
At least one data load job
One additional job either for migration/access plan calculation/to change
configuration settings in “Configuration and Monitoring Dashboard”.
17.If you set the parameter “data transfer jobs” to 04 in a configuration
“SCHEMA1”, a mass transfer ID 001 is assigned. Then what jobs should
be in the system?
1 Master job (IUUC_MONITOR_SCHEMA1)
1 Master Controller job (IUUC_REPL_CNTR_001_0001)
At most 4 parallel jobs for MT_ID 001 (DTL_MT_DATA_LOAD_001_
01/~02/~03/~04)
Performance: If lots of tables are selected for load / replication at the same time,
it may happen that there are not enough background jobs available to start the
load procedure for all tables immediately. In this case you can increase the
number of initial load jobs, otherwise tables will be handled sequentially.
For tables with large volume of data, you can use the transaction “Advanced
Replication Settings (IUUC_REPL_CONT)” to further optimize the load and
replication procedure for dedicated tables.
18.What happens after the SLT replication is over?
The SLT replication server creates 1 user, 4 roles, 2 stored procedures and 8
tables.
1 User
1 Privilege
4 Roles
<REPLICATION SCHEMA>_DATA_PROV
<REPLICATION_SCHEMA>_POWER_USER
<REPLICATION_SCHEMA>_USER_ADMIN
<REPLICATION_SCHEMA>_SELECT
2 Stored procedures
RS_GRANT_ACCESS, RS_REVOKE_ACCESS
8 Tables
DD02L, DD02T, RS_LOG_FILES, RS_MESSAGES, RS_ORDER, RS_ORDER_EXT,
RS_SCHEMA_MAP, RS_STATUS
19.What are the different replication scenarios?
Load, Replicate, Stop, Suspend and Resume.
Before you select any application table, the initial load of the tables DD02L,
DD02T & DD08L must be completed as they contain the metadata information.
Load: Starts an initial load of replication data from the source system. The
procedure is a one-time event. After it is completed, further changes to the
source system database will not be replicated.
For the initial load procedure, neither database triggers nor logging tables are
created in the source system. Default settings use reading type 3 (DB_SETGET)
with up to 3 background jobs in parallel to load tables in parallel or subsequently
into the HANA system.
Replicate: Combines an initial load procedure and the subsequent replication
procedure (real time or scheduled).
Before the initial load procedure will start, database trigger and related logging
table are created for each table in the source system as well as in SLT replication
server.
Stop Replication: Stops any current load or replication process of a table.
The stop function will remove the database trigger and related logging tables
completely. Only use this function if you do want to continue a selected table
otherwise you must initially load the table again to ensure data consistency.
Suspend: Pauses a table from a running replication. The database trigger will not
be deleted from the source system. The recording of changes will continue and
related information is stored in the related logging tables in the source system.
If you suspend tables for a long time the size of logging tables may increase and
adjust the table space if required.
Resume: Restarts the application for a suspended table. The previous suspended
replication will be resumed (no new initial load required).
20.What happens if the replication is suspended for a long period of
time or system outage of SLT or HANA system?
The size of the logging tables increases.

CHINNA M at 22:15

Share

No comments:

Post a Comment

‹ Home

View web version

Powered by Blogger.