We have added search box. Key in SAP issue keyword to search

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

Re: [sap-dev] Commit control with SAP HANA and replication

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from ugandhy on Aug 1 at 4:22 PM

As I understand, you have 77500 data-records to update on a single HANA
database table.
Unless there are multiple tables being updated and it is happening through
standard SAP transactions, 8 days is seems extremely unusual.

Database update or rollback should not take so much time.

If you need further analysis, please provide more details of what tables
you are updating and please be more specific about the connectivity that
you have.


---------------Original Message---------------
From: RaccoonCity
Sent: Tuesday, August 01, 2017 4:09 PM
Subject: Commit control with SAP HANA and replication


I am a technician in an company that represents a replication software in the AS/400 plataform, I do not know nothing about SAP but this application is doing (that is normal) commit control to make sure of the integration of the data but that are lasting 8 days, yes 8 full days of commit operation and it is making the replication software wait for ever to apply this commit.

My question is ... is it normal to have an commit operation open 8 days? with more than 77500 operations to apply (or to commit or to roolback).

Thank you

Reply to this email to post your response.
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
© 2017 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
Mark as helpful
View this online
Ask a new question
In the Spotlight
Have a technical question? Need to find IT solutions? Ask your peers in the Toolbox for IT community.



Post a Comment

T r a n s l a t e to your language