SQL20169W The buffer pool is not started

The DB2 message SQL20169W The buffer pool is not started appeared in response to a ALTER BUFFERPOOL statement db2 ALTER BUFFERPOOL ITMBUF8K IMMEDIATE size 250000 ---SQL20169W The buffer pool is not started. SQLSTATE=01654 To overcome this problem , disconnect all the applications connected to the database, and activate the database. There are a number of methods to disconnect all the applications , such as DB2 deactivate database Read More Database will come up with hidden buffer pools - DBA DB2 Querying Bufferpools DB2 - DBA DB2 DB2 SORTHEAP and pinned pages - DBA DB2 Read more →

DB2 - Collecting data for database performance problems

In DB2 database performance troubleshooting , one of the challenges is to collect the right amount and type of data to assist the DBA to get clues. In How to report a DB2 performance problem there are questions to think about – guiding you towards a general approach to reporting a performance problem This post lists the information required when you’re sending me DB2 performance related queries. It gives me enough data to gain an overview of the database. It doesn’t guarantee a solution , but covers the main data sets. Run the following from a DB2 command window db2look... Read more →

Database will come up with hidden buffer pools

Question: I get these buffer pool messages in the db2diag.log as sever status. How can I fix? Database will come up with hidden buffer pools Answer: When a server has insufficient addressable memory space left and the main buffer pools are to large the DB2 database will not start. As it won’t start , the DBA cannot connect to the database and change the buffer pool sizes. In that situation, the DB2 database will start with the pre-allocated four small buffer pools. Querying buffer pools - "SELECT * FROM SYSCAT.BUFFERPOOLS” will not allow you to view the hidden bufferpools. To... Read more →