Skip to Content
avatar image
Former Member

SLT Does not replicate all documents

Dear SAP LT Gurus,

We are using SLT in the following configuration: SAP ECC being replicated to a SQL Server Database 2008 (no in memory then).

We are facing so many issues with this configuration that it is better to filter the real blocking ones....

My problem is very simple: we have started to synchronize only 2016 Fiscal Year for BSEG table in SLT. The number of SHOWN replicated records was online with the number of records in BSEG table but we did not check in the first time the target table. After some days, we found out that we were missing a lot of records! Not all of the BSEG records were replicated! And this everyday! Everyday some records are replicated and some not....

After 1 week we were missing 750 000 documents (documents not ITEMS!!!!)! And the health check of the table is a real Christmas tree!

Checks for table BSEG started (mass transfer ID 006)

Table BSEG not found in the control table DMC_MT_TABLES

Source table for BSEG is

Last action is W-Resume (Wakeup) Replication, status is E-Error/ Aborted; "Is Last" = No (from 31.01.2016 00:19:55)

Current action is ; status is

Log table /1CADMC/00000989 created in sender system for table BSEG, and has 9 records

The following triggers are defined for table BSEG:

Trigger BSEG; status is 2-Activated

Latency for table BSEG is 71,10s (average of last 24 hours)

No access plan found for table

Migration object =Z__006;Defined? = No, Generated? = No (X = Yes, blank = No)

System status indicates issues with the load process for table BSEG

Checks  for table BSEG finished (mass transfer ID 006)

The troubleshooting activity has detected critical issues

And the cherry on the cake: we are not able to properly delete the data in the logging table (see other post without any answer) even if we correctly stop the replication process.

Can anybody help?? This is really critical right now for us and we would like to avoid a new initial replication.

Thanks.

Cyril.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Feb 25, 2016 at 09:08 AM

    Ok, found out why: it seems that the filters you set in the configuration is kept during the further replication. So my fault!

    I thought the filters were set only for the Initial load but in fact not.

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 08, 2016 at 08:09 PM

    BSEG is one of the largest table and is cluster table of RFBLG., these type of tables need tobe replicated with special settings in LTRS tcode in SLT system.

    you can refer How to improve the initial load especially the section "Which Process Should You Use To Load Large Tables?"

    or you can also enable "replication logging" but this will consume some space on SLT system.

    note:- make sure all the relevant DMIS notes are applied on SLT server for respective patch level.

    Regards

    Kishore

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Kishore,

      we followed this how to already. We applied it to all the tables we could.

      The initial load is not the problem, but the delta replication is. Not all records get synchronized and this is a real mess.

      We replicated much larger tables without encountering this kind of problem (1.8 billiard of records and everything ran smoothly).

      Can it be that we should not filter the initial load out? I mean, in order to speed up the process and deliver data as quick as possible, I filtered the extraction with a subset of data.

      Thanks.

      Cyril.