Documente Academic
Documente Profesional
Documente Cultură
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 ?
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).
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.
9.What is Latency ?
It is the length of time to replicate data (a table entry) from the source system to the
target system.
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.
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
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.
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 ?
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
20.What happens if the replication is suspended for a long period of time or system outage
of SLT or HANA system ?
22.Will the table size in SAP HANA database and in the source system the same ?
If the table size in HANA database exceeds 2 billion records, split the table by using
portioning features by using “Advanced replication settings” (transaction
IUUC_REPL_CONT, tab page IUUC_REPL_TABSTG).
25.Are there any special considerations if the source system is non-SAP system ?
27.How can you ensure that data is consistent in source system and HANA system ?
Since any changes in the source system is tracked in dedicated logging tables, the
replication status for each changed data record is transparent. A entry of logging table is
deleted after a 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, this is automatically covered by the RFC connection used for data replication from the
SAP source system.
The short answer is: it's a mystery. SAP has changed them around a lot and now they
call it SAP HANA Appliance, SAP HANA Database and SAP HANA Studio. Applications
built on HANA will be marked "powered by SAP HANA". Probably they will change it all
again.
Quite a few so far - it can only replicate certain data, from certain databases, in certain
formats, using the Sybase Replication Server. Batch loading is done using SAP
BusinessObjects Data Services 4.0 and is optimised only for SAP BusinessObjects BI 4.0
reporting.
These are all the same thing, and 1.0 SP03 is touted to be the final name for what should
go into RampUp (beta) in Q4 2011. This will allow any SAP NetWeaver BW 7.3 Data
Warehouse to be migrated into a HANA appliance. HANA 1.0 SP03 specifically also
accelerates BW calculations and planning, which means you get even more performance
gains.
HANA is the name for the current BI appliance (HANA 1.0) and the BW Data
Warehouse appliance (HANA 1.0 SP03). Both of these use the SAP IMDB Database
Technology (SAP HANA Database) as their underlying RDBMS. Expect SAP to start to
differentiate this more clearly as they start to position the technology for use cases other
than Analytics.
34. If I can run Net Weaver BW on IMDB/HANA, why can't I run the Business
Suite/ERP 6.0?
Simply because it's not mature enough yet to support business critical applications.
From a technology perspective, it is already possible to run the Business Suite on IMDB
and SAP has trialled moving some large databases into IMDB already.
The best thing that HANA brings to the table is the ability to aggregate large data
volumes in near real-time - and to have the data updated in near real-time. SAP's demos
show hundreds of billions of records of data being aggregated in a matter of seconds. SAP
has built a set of Analytics Apps on top of HANA and this are set to be great point use cases
to get customers up and running quickly.
There are some current issues around HANA when delivering ad-hoc analytics,
especially when using the SAP Business Objects Webi tool. Essentially the problem is that
you can ask computationally very difficult questions with Webi, which can cause very long
response times with HANA. SAP will need to build optimization for both Webi and HANA
to reduce the computational complexity of these questions, but they're not there yet.
What's more, it's worth noting that HANA 1.0 is not a Data Warehouse and it is more of
a Data Mart - that is, suited to point applications where there is a clear use case.
SAP hasn't entirely confirmed HANA licensing costs but the hardware is somewhere
around $1-200k per TB. Add to this licensing cost which are still being made on a per-
customer basis.
Regular RDBMS technologies put the information on spinning plates of iron (hard disks)
from which the information is retrieved. HANA stores information in electronic memory,
which is some 50x faster (depending on how you calculate). HANA stores a copy on
magnetic disk, in case of power failure or the like. In addition, most SAP systems have the
database on one system and a calculation engine on another, and they pass information
between them. With HANA, this all happens within the same machine.
It's the elephant in the room, but once the Business Suite runs on IMDB, Oracle won't be
needed any more by SAP customers who purchase HANA. This doesn't affect anything in
the short term because those people buying HANA today will still need an Oracle ERP
system.
40. What is this about 10:1 compression with HANA compared to Oracle?
A typical uncompressed Oracle or Microsoft SQL Server database, when put into
HANA, will be 10x smaller than before and this is due to the way that HANA stores
information in a compressed format. Note that most databases are now compressed and
these numbers may not fit your scenario, and to add to this you need 2x the RAM as your
database, plus room for growth. HANA sizing is still a dark art.
41. You mean I have to buy a HANA only 2.5x smaller than my big Oracle RDBMS?
What about archiving and data ageing?
Yes, in some instances you may have to buy a HANA appliance that is only 2.5x smaller
than it would be under Oracle. And data ageing isn't part of the 1.0 release, but SAP is
certainly working on it pretty hard. Let's hope they release something faster than you need
to buy a bigger HANA appliance!
This is the interesting thing - no one knows yet, and few analysts seem to have cottoned
on that the wider market opportunity might be huge. Think not just SAP applications but
any third party that requires ultra-high speed. Think not just an appliance but a
development platform. Time will tell.
Talk to your hardware vendor - all of the major vendors e.g. HP, IBM, Dell, have HANA
offerings now. Technically HANA will run on any Intel x64 based system from your laptop
through to the big 40-core, 2TB RAM servers. It is however only supported on a small
number of big rack-mount servers like the Dell R910 and HP DL980.
It's unclear but probably because the blades don't yet offer the same performance.
HANA is optimized for the Intel X7560 CPU and will run fastest on this. And for instance,
the Dell M910 blade can only run 2x X7650 CPUs and 512 GB RAM in this configuration,
which probably explains the limitations. What's certain is that HANA will eventually run
on blades - it's born to run on blade technology!
Yes, but only in the labs so far. There are no public plans to compete against
IBM/HP/Dell in this space, but it may make sense for SAP to enter the appliance market,
especially in the context of Data Centres and even more so in the context of the SAP
Business by Design cloud offering, which will run on IMDB.
This varies from vendor to vendor but it is shared network attached storage (NAS). Both
regular magnetic disks and SSD storage can be used for the backup of the database (HANA
runs in memory remember, so disk storage is just for backup, and later, for data ageing).
Note that you require 2x storage that you have RAM, which is 2x the database size - i.e.
storage size = 4x database size. In most cases there is additional ultra-high speed SSD
storage for log files.
3. Technical FAQ
If you use Sybase Replication Server (SRS) for near real-time data then you need to
watch out for licensing still (SAP have license deals pending). If you run DB2 then you're
fine but with Oracle and Microsoft SQL Server there are some license challenges if you buy
your license through SAP, because you may have a limited license that does not allow
extraction. Talk to SAP for further information on this.
48. What source databases does HANA support for batch loads?
If you use SAP Business Objects Data Services 4.0 for bulk loads then pretty much
anything. BO-DS is a very flexible Extract, Transform & Load tool that supports many
databases - check out the specs for more details.
SRS has additional restrictions which are worth bearing on mind. It can only replicate
Unicode data and does not support IBM DB2 compressed tables.