When you select a buffer pool from the contents pane and select Show Related for that object, the Show Related dialog lists any objects with first-level dependencies on that buffer pool. These objects can be: databases, indexes, and table spaces. You can view second-level dependencies by selecting Show Related for each object with a first-level dependency.
If you contract the size of an active virtual buffer pool, DB2 contracts the pool by marking active buffers as "to be deleted," which means they are not reusable to satisfy other page requests. However, the virtual storage might not be freed immediately. A system administrator can determine the status of the buffer pool by displaying the buffer pool (available from the Control Center).
If insufficient virtual storage is detected while expanding a virtual buffer pool or while creating or expanding a hiperpool, DB2 issues an error message, and the process terminates, leaving the virtual buffer pool or hiperpool with a smaller size than was requested.
Deleting an Active Buffer Pool- If you alter the buffer pool size (available from the Control Center) to delete an active buffer pool (by specifying 0 for virtual buffer pool size), DB2 issues a message to indicate that it is ready to explicitly delete this buffer pool. Once DB2 accepts the request to delete a buffer pool, the buffer pool is marked as"delete pending". All current access to the buffer pool is quiesced, later attempts to access table spaces and indexes fail resulting in an error message. Also, all open page sets that refer to the buffer pool are closed.