Commit work for clearing the buffer

[former_member599326]

Hi,

I came across a program which uses commit work for clearing the buffer. Program is reading archived file because of which DB update buffer becoming too big resulting in system performance slowdown.

My understanding was that commit work is used to commit the database changes.

Is it the correct usage of "commit work" for clearing the buffer ?

Regards,

[FredericGirod]

What I already seen, is people using commit work to reset the timeout counter. But, I don't understand the link with buffer

[former_member599326]

commit work is used for 2 purpose :-

1) FM "ARCHIVE_READ_OBJECT" posts a message (Job log) for every archived file read that DB update buffer can become too big resulting in system performance slowdown.

2) performance or memory issues

[Sandra_Rossi]

Which one of the buffers are you talking about? Difficult to discuss if you don't clarify 😉

Are you confusing BAPI_TRANSACTION_COMMIT and COMMIT WORK?

[former_member599326]

DB Update Buffer

[former_member599326]

my query is whether commit work is used to commit the database changes only or it is used to clear DB update Buffer also?

[former_member599326]

is it possible that DB update buffer gets full while archiving the data e.g. accounting documents ?

[Sandra_Rossi]

Your question is too much general, I don't understand what you are talking about. Please describe the exact symptoms, stop "beating around the bush" (Google translation of French "tourner autour du pot").