Transaction log grows after restart SAP J2EE Engine / Portal

[Former Member]

Dear experts,

We have one of our Enterprise Portals with SAP Netweaver 2004 (6.40, SP25) and Microsoft SQL server 2005.

Everytime we execute a restart of the SAP J2EE Engine, or just one of the three existing server nodes, the SQL Transaction log will grown to the maximum of the harddrive capacity.

This happends approximaly 1 or 1,5 hour after the SAP J2EE Enigine is up and running.

When the transactionlog is full, the recovery and eventually rollback process will start. This process will cause a major performance problem for the Portal users.

After the back-up of the transaction log and also a manually schrink action of the logfile in the SQL DB the situation will be normal again. This same problem happends after each restart.

Does anyone have any idea what is causing this gowing transaction log and how can we prenvent this?

Best regards,

Joost Weghorst

Edited by: J. Weghorst on Oct 11, 2011 11:52 AM

[Sriram2009 · Accepted solution]

Hi

If number of tractions are more in Sql server it will be increase the traction log. For this you have do the truncate after completion of daily Database backup. Check the SAP Note 44449

Kindly go thru the below links

http://support.microsoft.com/kb/873235

http://msdn.microsoft.com/en-us/library/aa174538%28v=sql.80%29.aspx

Regards

Sriram

[Former Member · Accepted solution]

Hi Sriram,

Thank for the provided information.

In our case it's a SAP Portal database which basicly always has the same size and will not have a large grow.

The initial size of the Transactionlog is 6GB, in a normall runtime envrionment the free space of this 6GB will be 99%.

When we restart the portal environment, after 1/1,5 hour of succesfull running time, the t-log file will grow in a few minutes from a very less size till the maximum of 9,5GB. This mean the transactionlog is full and the recoveryprocess from SQL server will start. When this proces is being executed the database will not be accesable till the recovery is succeded.

Our scheduled t-log back-up (each 30 minutes) will truncate the file content again to a mininum of space.

We are very curious to the cause and trigger that will let the transaction log grow from this very small size till the 9,5GB in this very short time (just minutes).

Any clue?

Thanks in advance.

Joost

[Former Member · Accepted solution]

Posted by mistake.

Edited by: DatabaseSAP on Oct 11, 2011 6:25 PM

[Former Member · Accepted solution]

Hi,

Yes exactly, i think that to find out this "proces" or "activity" it can lead us to the root cause of our problem.

It happends only after a restart of the J2EE engine. And the problem is only concentrating to the database of this J2EE engine (SAP Enterprise Portal)

Regard,

Joost