Hi Team,

We are facing a critical issue where our Db2 pureScale database instance is unresponsive and failing a query  with the error.

[57011][-1218] There are no pages currently available in bufferpool "2".. SQLCODE=-1218, SQLSTATE=57011, DRIVER=4.33.31

Problem Summary:

• All queries are failing with SQLCODE=-1218 (There are no pages currently available in bufferpool)..

• A full database deactivate/reactivate cycle did not resolve the issue; the error returns immediately.

• We have turned on Self Tuning Memory Management 

------------------------------
jaison chipuka
------------------------------

Hi!
Sharing DBM CFG, DB CFG for DB <dbname> would be a good starting point - as well as Db2level.

Did you look into possible resolutions for SQLCODE -1218:

1. increase the bufferpool size

2. decrease the maximum number of database agents and/or connections

3. decrease the maximum degree of parallelism

4. decrease the prefetch size for table spaces that are in this bufferpool

5. move some table spaces into other bufferpools.

------------------------------
Jan Nelken
Db2 (LUW) DBA
HCLTech
Katowice or Krakow
+48 783 109 863
------------------------------

Hi,

1) What's the output of the following command on your server (amend the mydb to your database name)?
db2pd -db mydb -buf 2

2) Have you tried to set some initial value to this BP like below, if it's too small (the instance restart is needed)?
db2set DB2_OVERRIDE_BPF=2,10000

------------------------------
Mark Barinstein
------------------------------

Hi,

we typically encounter such issue in PureScale if one or more members were restarted by the cluster manager and it fails to remove the old shared memory segments. This then prevents successfully startup of bufferpools since not enough shared memory is available.

The best way arround this is to stop the instance, run "ipclean" to remove the old segments and restart.

Best regards

-- Steffen.

------------------------------
Steffen Herold
------------------------------

Seems, that it's not an ordinal issue with not started main bufferpool, when the bufferpool id is more than 4k (which identifies a fixed size tiny one). Here the bufferpool id is "2" (if it's not a typo), which corresponds to some main one...

------------------------------
Mark Barinstein
------------------------------

Original Message:
Sent: Tue August 05, 2025 02:41 AM
From: Steffen Herold
Subject: BUFFER POOL ISSUE ON A DB2 PURESCALE ENVIRONMENT

Hi,

we typically encounter such issue in PureScale if one or more members were restarted by the cluster manager and it fails to remove the old shared memory segments. This then prevents successfully startup of bufferpools since not enough shared memory is available.

The best way arround this is to stop the instance, run "ipclean" to remove the old segments and restart.

Best regards

-- Steffen.

------------------------------
Steffen Herold
------------------------------