NetWeaver 2004: The System is Suddenly Not Working Anymore?

If you can't log-in to your NW4 system - or everything is suddenly becoming pretty slow - you should check the space left in your system's LOG volume. If you don't have a graphical DBM GUI at hand, you can check this by running the following command as nw4adm:

dbmcli -u control,control -d NW4 -USQL c 'sql_execute select logsize - (usedlog) from serverdbstatistics'

The output is in 8 KB pages.

An easy way to avoid this problem, is to set "Log overwrite on", by executing the following command as nw4adm:

dbmcli -u control,control -d NW4 util_execute set log auto overwrite on

Please note: With this setting, the database will overwrite its logs circularly, so the database will be unable to recover, if the DATA volume crashed. When developing a lot with the TestDrive, doing a backup or increasing the LOG volume would be a better solution.