Hi everybody,
I faced one problem of SAP transaction log. My user run one big
program until the transaction log full even I change the transaction log to
SIMPLE in MS SQL server. When transaction log full, SAP system unable to
access, the only thing is to expand again the transaction log space. How to
make the program run success without effect the increase of transaction log
?
Thanks in advance.
Regards,
SK Lim
Hi Lim,DATA1, DATA2, DATA3) and your logLOG1). because basically the data is just 20Gmin in a small
I thought you have done the log shrinking twice every after the
upload? ok if you havn`t gone through it I can give you procedures to
do it properly,, basically shrinking is the key to successfully save
and maintain the production system,, I have some few questions before
we can start the event,, what is the size of your DATA
(
(
medium corporation. and logs usually runs at 40G or more.. Deleting
client will not reduce the size,,
If the log is already 3 times your data size then you really have to do
something about it before you even run out of space and affect your
current production system,, there are logs also that are related to TMS
and needs to be maintained these are two diffrent logs in SAP that are
critical and needs to be maintained properly,, just a reminder..
I need to know what partitionig did you make for the R3 system? so that
I can trace where and what log is consuming the space,, thanks.. I hope
we can solve this issue of you..
God bless.