Shulou(Shulou.com)05/31 Report--

What is the solution of db2's bufferpool underreporting error report? in view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

The DB2 database reports "DB2 Database Error: ERROR [57011] [IBM] [DB2/NT] SQL1218N There are no pages currently available in bufferpool" 4096 ". SQLSTATE=57011" when importing tables in bulk. Note that this error is obviously caused by a lack of bufferpool.

The solution is also very simple, can be fast graphic interface method, but also can be sentence parameter adjustment method.

I. graphic interface method

Log in to the control center of DB2 and find the buffer pool for the library.

Find the corresponding buffer pool on the right, click to change the corresponding buffer pool size, and take effect immediately.

Change the buffer pool size from 4096 to 32768, and select to change the buffer pool immediately, and click OK.

Second, the method of adjusting sentence parameters

Connect to the database

Modify bufferpool

Check the existing buffer pool in the current database

Db2= > select * from syscat.bufferpools

The results show that the system has a default bufferpool IBMDEFAULTBP with a size of 4K (1x 4096), which is obviously too small.

Directly modify the size of the IBMDEFAULTBP:

Db2 = > alter bufferpool IBMDEFAULTBP immediate size 10240

Now the size of bufferpool is 40m (102404096), which can meet the needs of current applications.

You can also modify the corresponding buffer pool size

Db2 = > alter bufferpool TRAINBUFF immediate size 32768

Now the size of bufferpool is 134m (102404096), which can meet the needs of current applications.

Restart the database manager

If the buffer size is set to-1, the number of pages in the buffer pool is determined by the database configuration parameter buffpage.

Note: the database configuration parameter buffpage works only for buffer pools whose buffer size is set to-1.

Add:

Also note that if you report "DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011", the problem is that the log file for the database is full.

The solution is different, need to increase the log file size, increase the number of log files, increase the number of auxiliary log files.

View configuration parameters command: db2 get db cfg for

Modify configuration parameters command:

Modify log file size: db2 update db cfg for using LOGFILSIZ 4096

Modify the number of primary log files: db2 update db cfg for using LOGPRIMARY 20

Modify the number of secondary log files: db2 update db cfg for using LOGSECOND 10

The sum of primary log and secondary log cannot be greater than 255

After modifying the log configuration, if the library is in use, you need to restart the database (db2stop force,db2start) and then connect to the library (db2 connect to). When connecting to the library, the data will take some time to allocate new logs and wait a while.

In fact, 57011 of the error may be that the machine does not have enough disk space. You can clean up the disk space and drop some useless instances.

The solution to the problem of db2's bufferpool underreporting is shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.