Error: 1Error while replicating using SLT "Database object for DD08L is inconsistent:

(Primary index)"
In our project, we have installed SLT and when we tried to Replicate from ECC to SAP HANA,
we are getting the following error.
Database object for DD08L is inconsistent: (Primary index).

When i checked the application log I have this error message "Z_DD08L_023: Run 0000000058
aborted due to DUPLICATE KEY"
Same error is coming for other table DD02T, however for DD02L this error did come, but we
have deleted the Schema in HANA and when we re-ran the replication DD02l went thru with out
any problem.
I did look for OSS, but i could not find any helpful information.

Solution: Version of DMIS package for SLT and what version of HANA. This was supposed to
be resolved in DMIS 2011 SP05 as far as I know - I have hit and continue to hit this error
sometimes, below is how to resolve.
Note 1868061 - SLT (2011 SP04 / 2010 SP09) - Correction 15
Note 1874308 - SLT (2011 SP04 / 2010 SP09) - Correction 16
In LTRC, go to Data Transfer Monitor, highlight the table in question and hit the pencil/edit
button.

Change the "Transfer Behavior" from Array Insert to Array Modify and hit Save.
From here, you can either let the master job pick these up again and attempt reprocessing, or if
the master job is already stopped, this should be resolved on starting again.
Error: 2SLT Configuration Error Occurred when selecting from database
LTR configuration creates the user SLT in hana but doesn't seem to create schema-specific roles
SLT_DATA_PROV;
SLT_POWER_USER;
SLT_USER_ADMIN,
SLT_DATASELECT
Also getting this error in LTR Configuration
Error Occurred when selecting from database

Solution: Update HANA client on SLT server to the same version of HANA target system.

Update this HANA Client on SLT Server to the same version of HANA Target System

HANA client can be found on the HANA DVD which you can download from sap website.
Just run the install file for the OS you're running.
Error: 3SLT - problem with replication in HANA
Problem with SLT System.
Started replicate tables sometimes they are replicating, but sometimes not. Iu2019ve this same
situation with loading tables. Iu2019ve strange situation with other tables. When I start replicate
table, ie. MARA, my HANA see this table in my replication schema, but doesu2019t see in
u201CData Provisoringu201D. And also table in HANA is still empty.
For your information system SLT has:
SLES 11SP1
NW 7.0 EHP 2
Oracle 10.2.0.4
DMIS with SP 4
Kernel 100
SAP HANA is in Revision 17.
Iu2019ve also implemented SAPnotes into SLT system: 0001603754, 0001607754, 0001612292,
0001614355, 0001614775, 0001619759, 0001623278, 0001625136, 0001641061, 0001645517,
0001646787, 0001647648, 0001648783.

Solution: Here is usual quick solution that resolves most of the issues.
Stop the replication in SLT (login into client in which SLT was configured):
- make copy of job IUUC_MONITOR_<schema> (in our case
IUUC_MONITOR_DATA_SLT_IDD800)
- cancel active job IUUC_MONITOR_<schema>
- wait for the controller jobs IUUC_REPLIC_CNTR_xxx_yyyy (where xxx and yyyy are digits)
to be in released status (they must not be in active status)
Note: If you see only jobs IUUC_REPLIC_CNTR_xxx then you must wait until they finish their
execution (less than minute) and jobs IUUC_REPLIC_CNTR_xxx_yyyy will appear.
Note: You should see exactly two controller jobs. If you see more it means that more systems are
being controlled by this SLT. Be sure to work with correct jobs.
- delete controller jobs IUUC_REPLIC_CNTR_xxx_yyyy
- cancel one or more data load jobs DTL_MT_DATA_LOAD_xxx_yy (again be sure to cancel
correct jobs in case multiples systems are managed by this SLT)
Restart the replication in SLT
- Release the monitoring job that you created before (IUUC_MONITOR_<schema>) - use option
Immediate - this job will recreate other jobs
SAP SLT might get stuck sometimes and restarting the jobs usually helps. Also bear in mind that
replication is not happening instantly but takes time (give it around 10 minutes to fully process
before coming to decision that something is wrong).

Error: 4Error while replicating data from MSSQL to HANA

Created SLT configuration where the replication has to happen from MSSQL database for NW
BPM for 4 tables. I have also applied a transformation function to convert date columns in the
BPM tables to right desired format while replicating in HANA.

Now when I use the SAP HANA Data Provisioning Editor to replicate the data from these BPM
tables, I am getting following error :

Conv.obj. Z_BC_BPEM_EL_RDS_021: Calculation job in sender system could not be started

In the configuration I have used Job Options as No of data Transfers Job : 003 , Initial Load Jobs
: 002 , No of Calculations Job : 001

We are using SLT 2.0 and BASIS release 740.

Solution: There could be number of reasons for this issue. We need to first start filtering one by
one and take out the possibility. Please check the things in the following order.

1. As everyone mentioned, check if you have free available WPs. System is going to use
Background WP for running calculation job in the Source system. Normally Basis define
sufficient number of WPs but sometimes they are occupied. You can check using TCode SM50
( you need to do that on each host in a multi App server environment ).

2. Try increasing your calculation jobs in SLT using TCODE LTRC --> Administration Data -->
Change no of Jobs. Make sure you have enough free background WP in your SLT and Source
system.

Incase the above methods do not work, provide the following information.

1. Where exactly you see the error message. Are you able to add the table to Data provisioning
from LTRC.

2. Are you able to add any more tables an

Error: 5SLT LTR DB Connection error
Using LTR Transaction in our SLT Server which is our NW 731 system with DMIS add on 2011
at SP06.
While doing configuration with LTR Transaction we stuck at phase for "specifying target
system" in which we have to do the DB
Connection, after providing all necessary parameters we are unable to connect to our HDB, it
says,
" ! Error occurred when opening db connection"
In order to resolve this we have upgraded our Kernel to 721_EXT at 300 level along with DBSL
at 225, but it didn't helped.
Also we have HDB client installed in place.

Solution: Check transaction DBCO in SLT. If HDB is not there, specify its configuration

 Problem was solved by checking the whole configuration. The problem was with the DBSL
files.
Error: 6Slt replication error
Created a replication configuration and everything seems to work fine. But when trying to add
table CDHDR, an error occurred, see below:

Start of function - Access plan calculation 021 - on 25.04.2015 at 14:03:36

Access plan for CDHDR is being calculated (ID 00001, 8.000.000 blocks)
Z_CDHDR_021: Access plan could not be calculated, delimitation is not possible
Access plan calculation failed
End of function - Access plan calculation 021 - on 25.04.2015 at 14:03:42

Solution: This error always happens when the default delimitation field is not distinctive
enough.

By default, SLT uses the first field for delimitation. When we checked this table on the source
system, we found that first field of the table was CLIENT which is not very selective. Therefore
we changed and define another key field with high selectivity for delimitation.
You can define the field in LTRS->performance option as below:
Insert the selection parameter as another key field which has high selectivity for delimitation
Restart the replication of the affected table,it should work well after that 
Error: 7Table Replication Failed in SAP SLT...No Error log found
Replicating table VBUK using SAP SLT to HANA Database using transaction LTRC.
The data flow is like this SAP ECC -> SAP SLT -> HANA database.
But it fails to generate Triggers in source system (SAP ECC) and the replication ends in failure
status.
Try to find out if any frozen or old triggers are sitting in SAP ECE using transaction
IUUC_REMOTE, but could not find any existing triggers in ECC.
Also, there is no error log recorded in SAP SLT or SAP ECC system on why the replication
failed.
Here are system details for DMIS.
DMIS Info for Replication Server:
Release: 2011_1_731
Support Package Level : 0009
DMIS Info for Source System:
Release: 2011_1_700
Support Package Level : 0009

Solution:
Please proceed as below ;
You need to make sure that the user that is used for connecting via RFC have the required
authorization. this user is the user that goes to the ECC system via RFC connection and tries to
create the triggered and logging tables.
1. Login to ECC --> goto SM66 check which user id coming inRFC from SLT system.
2. Provide required authorization to the user mentioned in RFC.
Else
Restart the replication for a particular table... just to regenerate the error msg.
Go to SU53 and check authorization for the RFC user coming from SLT system.
Error: 8Error occurred when opening db connection
Installed an SAP Hana System(HANA 1.0 SPS5) with an SAP LT Replication server(DMIS
2011 SP2-3) and SAP source system(DMIS 2011 SP1-3).
The system hosting the SAP LT Replication Server is an SAP system with SAP NetWeaver 7.02
(Basis Support Package 11) ABAP stack using SAP Kernel 7.20 EXT(64BIT Unicode) and 
patch level is 400.
We have successfully connected SAP LT Replication server and SAP source system through
RFC.But whenever we create a new configuration schema for connecting SAP Hana System and
SAP LT Replication server: the dynpro dialog raises an error:
Error occurred when opening db connection
Verification of Schema failed due to connection issues

The RFC destinations working fine.

Solution: Upgrade kernel from 720 ext level 400 to 721 level 40.
Error: 9SLT Replication not replication tables after SPS09 Upgrade on HANA
 Upgraded HANA system from Rev 83 to SPS 09. After upgrade slt replication stopped working.
Tried creating a new configuration in SLT, below is the error while creating a new configuration.

Solution: 1. Checks DBCON, if the connection details are maintained if not maintain.

2. Run ADBC_TEST_CONNECTION in se38 and see if connection is successfull if not

see dev_w* files at OS level for errors.
Error: 10SLT Replication: Status - Scheduled for long time
Configured SLT .Our landscape ERP--SLT--HANA.
The configuration was success and could see DD* TABLES in SLT schema with Action
"Replicate”, Status "In process".
I have added one more table with  "REPLICATE"  option . The status of this table shows
"Scheduled" since long time (5 hrs) .

Solution: use "Stop Replication" option in Data Provisioning in HANA Studio

then in this case DB Triggers and Logging table are automatically deleted from the source
System and you have to perform initial load once again as delta recording was deactivated for a
certain time and changes might not be recorded.
So try REPLICATING the table again using Replicate Option in HANA Studio.
It is recommended that if you want to stop replication for some time Use SUSPEND option.