Wednesday, 7 February 2018

HANA Log Volume full

Tags


HANA DiskFullEvent on Log Volume

Symptom
You notice, that the log volume is full and the database does not accept any new requests.

Additionally, the trace of the service with the full log volume contains DiskFullEvent messages:

LoggerImpl.cpp(00095) : Logger notified of new DiskFull: DiskFullEvent[id= XXX, path= /hana/log/SID/mntXXXXX/hdbXXXXX/, state= NEW]

Reason and Prerequisites

The log volume is full and the database does not respond or start anymore.

Solution

Stop the database:

HDB stop

Change directory into folder mnt00001 of the log volume (Default: /usr/sap//global/hdb/log):

cd /usr/sap//global/hdb/log/mnt00001

You have to move one of the log volumes temporarily to another volume where enough space is available.
You should free at least 2 GB of space to ensure that the database has enough space to start. To find out the space consumption of each volume execute:

du -sh *

Move a volume which consumes at least 2 GB of space (e.g. hdb00003) to a volume with sufficient free space, e.g. to the data volume (Default: /usr/sap//global/hdb/data):

mv hdb00003 /usr/sap//global/hdb/data

Create a symbolic link to the new folder in the old location:

ln -s /usr/sap//global/hdb/data/hdb00003   /usr/sap//global/hdb/log/mnt00001/hdb00003

Start the database:

HDB start

Wait until log backups are performed.

Use the following SQL-Statement to clean up the log volume:(execute the query in tenant DB)

ALTER SYSTEM RECLAIM LOG;

Stop the database again and remove the symbolic link:

rm -f /usr/sap//global/hdb/log/mnt00001/hdb00003

Move the log volume back to its original location:

mv /usr/sap//global/hdb/data/hdb00003 /usr/sap//global/hdb/log/mnt00001

Start the database

HDB start

More Details Refer KBA 1679938


EmoticonEmoticon

Note: only a member of this blog may post a comment.