Log volume size

[Former Member]

Dear colleagues.

I have 2 log volumes, LOG001 & LOG002.  LOG001 is 4MB, 512000 pages. I created LOG002 recently when the log became full without checking the LOG_SEGMENT_SIZE parameter.  I made it 1MB, 128000 pages due to HD space constraint.  The LOG_SEGMENT_SIZE is 170666.

Every time I run a log backup, the database goes offline with the below message in knldiag.err

2013-02-26 07:16:14	21 ERR 11196 DBCRASH  vabort:Emergency Shutdown, Task: 57
2013-02-26 07:16:28	18 ERR 20011 MOVECODE VKB38:34
2013-02-26 07:16:28	18 ERR 20011 MOVECODE 2013-02-26 07:16:28 MOVECODE Error 20011
2013-02-26 07:16:28	18 ERR 20011 MOVECODE Bad parameter: limit source 8192 destination 8192, source [0X1689000]+1, destination [0X177B000]+8187, 8 bytes
2013-02-26 07:16:28	18 ERR 20009 FILLCODE VGG01:12
2013-02-26 07:16:28	18 ERR 20009 FILLCODE 2013-02-26 07:16:28 FILLCODE Error 20009
2013-02-26 07:16:28	18 ERR 20009 FILLCODE Bad parameter: limit 8192, [0X177B000]+8195, -2 bytes 254
2013-02-26 07:16:30	0 ERR 12006 DBCRASH  Kernel exited without core and exit status 0x200
2013-02-26 07:16:30	0 ERR 12010 DBCRASH  Kernel exited exit code 2

However, the database can be set to online.

How do I resolve this log backup problem.

Thanks.

[former_member229109]

Hello,

-> What is the version of your database?

-> Info: 512000 pages < 8KB pro page > => 4GB

            128000 pages                          => 1GB

-> Adding the log volume will not solve the LOGFULL issue. You need to create the complete databackup, then log backup. As of 7.4 database version could be done in admin status.

If you are SAP customer =>

see SAP note : 869267 FAQ: SAP MaxDB log area

-> During the high loading to the database in parallel and slow i/o write at OS with small log area LOGFULL could occur. Use DB analyzer to find the bottleneck in the database & check that you use the fast disks for autosave logs. If you are SAP customer => create the SAP message.

-> For the issue with restart database please check the OS ulimits in the KnlMsg or knldiag.

   If you are SAP customer => review SAP note 628131.

   Be sure thar x_server restarted with recommended OS parameters settings, if you connected to the database remotely,  the OS user < you restarted the database using dbmcli tool at DB server > has the recommended ulimits.

Regards, Natalia Khlopina

[former_member188883]

Hi Rizza,

The automatic log backup starts to work if log_segment_size log pages were written to the log. In the

default case this is after 1/3 used logsize and then only this 1/3 logsize is backedup.

The size of the log segment depends on the size of the individual log volumes and must not be greater than the sum of all log volumes.A full log causes the database to stop.

I feel you should create some more space in the log area and then run the backup.

Regards,

Deepak Kori