IDS Forum

LOGBUFF size

Posted By: FRANK
Date: Thursday, 26 May 2016, at 12:28 p.m.

Hi,

We set ,

LOGBUFF 256

Occasionally, I still see this sometimes,

58087a28 Y--P--- 4082303 saapmgr - 551cf760 0
1 0 0
580882e8 G-BPX-- 3671545 saapmgr - 526d0898 0
2 29 48411
58088ba8 Y--P--- 2478091 saapmgr - 55a96230 0
1 116 14986

So, a session is waiting for the log buffer .

The doc ( below) seems not to recommend to set it higher or .... .

What do you think or comments ?

Thanks
Frank

LOGBUFF configuration parameter

Use the LOGBUFF configuration parameter to specify the size in kilobytes
for the three logical-log buffers in shared memory.
onconfig.std value LOGBUFF 64 units Kilobytes values An integer in the
range of 32 - (32767 * pagesize / 1024), where pagesize is the default
system page size. The value must be evenly divisible by the default system
page size. If the value is not evenly divisible by the page size, the
database server rounds down the size to the nearest value that is evenly
divisible by the page size. takes effect After you edit your onconfig file
and restart the database server.
Usage

The three logical log buffers permit user threads to write to the active
buffer while one of the other buffers is being flushed to disk. If flushing
is not complete by the time the active buffer fills, the user thread begins
writing to the third buffer.

If the RTO_SERVER_RESTART configuration parameter is enabled, set the value
of the LOGBUFF configuration parameter to 256 kilobytes. If the value of
the LOGBUFF configuration parameter is less than 256 kilobytes, a warning
message displays when you restart the server.

Otherwise, set the value of the LOGBUFF configuration parameter to 32
kilobytes for standard workloads or 64 kilobytes for heavy workloads. The
database server uses the LOGBUFF parameter to set the size of internal
buffers that are used during recovery. If you set LOGBUFF too high, the
database server can run out of memory and shut down during recovery.

If you log user data in smart large objects, increase the size of the log
buffer to make the system more efficient. The database server logs only the
portion of a smart-large-object page that changed.

You can view information about the logical log buffers by running the onstat
-l command.
*Parent topic:* Database configuration parameters
<http://www.ibm.com/support/knowledgecenter/SSGU8G_12.1.0/com.ibm.adref.doc/ids_adr_0007.htm?lang=en-us>
*Related reference*:
onstat -l command: Print physical and logical log information
<http://www.ibm.com/support/knowledgecenter/SSGU8G_12.1.0/com.ibm.adref.doc/ids_adr_0598.htm?lang=en-us>

--001a11c1728c309b400533c148a4

Messages In This Thread

• LOGBUFF size
  FRANK -- Thursday, 26 May 2016, at 12:28 p.m.
  • Re: LOGBUFF size
    Fernando Nunes -- Thursday, 26 May 2016, at 1:27 p.m.
    • Re: LOGBUFF size
      FRANK -- Thursday, 26 May 2016, at 2:26 p.m.
      • Re: LOGBUFF size
        Fernando Nunes -- Thursday, 26 May 2016, at 3:18 p.m.
        • RE: LOGBUFF size
          Andrew Ford -- Thursday, 26 May 2016, at 3:30 p.m.
        • Re: LOGBUFF size
          FRANK -- Friday, 27 May 2016, at 10:34 a.m.
          • Re: LOGBUFF size
            Fernando Nunes -- Sunday, 29 May 2016, at 4:37 a.m.
          • Re: LOGBUFF size
            Fernando Nunes -- Wednesday, 3 August 2016, at 12:30 p.m.
  • Re: LOGBUFF size
    Art Kagel -- Thursday, 26 May 2016, at 4:19 p.m.
    • Re: LOGBUFF size
      FRANK -- Friday, 27 May 2016, at 10:51 a.m.
      • Re: LOGBUFF size
        Art Kagel -- Saturday, 28 May 2016, at 4:11 a.m.
        • Re: LOGBUFF size
          Madison Pruet -- Saturday, 28 May 2016, at 8:15 a.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.