on 12-04-2014 12:11 PM
Hello Experts,
I am facing one issue where huge number of unprocessed logging table records were found in SLT system for one table. I have check all setting and error logs but not found any evidence that causing the unprocessed records. In HANA system also it shows in replicated status. Could you please suggest me something other than to replicate same table again, as that option is not possible at this moment.
Hi Nilesh,
Just start/stop the master Job in LTRC & check once.
Regards,
Joydeep.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nilesh,
As you are saying that the table is already in replication status, and it seems you want to get rid of old unprocessed logging records, you can try below option -
tcode- iuuc_remote
expert functions-
Delete obsolete log tab entries.
Let us know if it worked for you or not.
Regards,
Saritha K
Hello,
since I am again facing this issue and since I havent found any problems in the source system (logging table is active, last change is from January), nor in SLT nor in HANA, I would like to ask for help again. What else needs to be checked or repaired to resume the replication again? I dont want to start the initial load since last time it took almost 3 days (due to the conversion process of SAP long texts to readable HANA format).
Also OSS messages has been created, so far no response from SAP
Thanks in advance for any input.
Br, Jan
Hi,
the fix: implementation of the Note 2003256 - SLT (2011 SP5, SP6 & SP7) - Inconsistencies MSSQL, DB2, DB4, DB6 and then LTRC > Processing Steps -> Delete Generated Runtime Object. Replication of affected table was then resumed without initial load.
Hi Nilesh,
Check your source system and increase the dialog workprocess, more dialog jobs are required in source system to reduce the load.
Regards,
V Srinivasan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nilesh,
What are the performance impacts on the SAP ECC system when multiple large SAP tables like BSEG are replicated at the same time? Is there a guideline for a specific volume or kind of tables?
There is no explicit guideline since aspects as server performance as well as change rate of the tables are also relevant. As a rule of thumb, one dedicated replication job per large table is recommended.
Regards,
V Srinivasan
Hi Srinivasan,
Thanks for your reply, but if you see the error screenshot, then come to know that unprocessed logging records were old dated. We are not facing any issue with initial load or replication, and not getting any error neither in HANA nor in SLT. Parallel replication is already applied in my case.
Regards,
Nilesh
Hi Saritha,
Thanks for your reply, I am on DMIS 2011_1_731 SP-7 and note mentioned by you is not relevant to my issue.
Regards,
Nilesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nilesh,
I had faced this issue earlier and my problem got resolved after applying correction note 1984947. It worked for my DMIS version which is 2011_1_731 SP level 06.
Not sure about your DMIS version. You can give it a try if its relevant for your case.
Better to apply all correction notes for your DMIS version.
Hope this helps..
Regards,
Saritha K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.