IBM Support

How to determine the tables responsible for a phantom quiesce on a tablespace

Technote (FAQ)


How to work out which tables need to be specified to take a tablespace out of a quiesce state after the session responsible for the original quiesce has terminated and leaving no owner for the quiesce of the tablespace. This situation is known as a phantom quiesce on the tablespace.


The session responsible for the quiesce on the tablespace has been terminated and there is now no owner of the quiesce.


To find out which objects hold a quiesce on the tablespace a list tablespaces show detail can be run. Following is an example:

$ db2 list tablespaces show detail

Tablespaces for Current Database
Tablespace ID = 2
Type = Database managed space
Contents = All permanent data. Large table space.
State = 0x0001
Detailed explanation:
Quiesced: SHARE
Total pages = 4096
Useable pages = 4064
Used pages = 1824
Free pages = 2240
High water mark (pages) = 1824
Page size (bytes) = 8192
Extent size (pages) = 32
Prefetch size (pages) = 32
Number of containers = 1
Number of quiescers = 1
Quiescer 1:
Tablespace ID = 2
Object ID = 15

This tablespace has been placed in a quiesce share state by object 15, which equates to the table:

$ db2 select tabname from syscat.tables where tableid = 15 and tbspaceid = 2


1 record(s) selected.

so to remove the phantom quiesce the following command can be run:

$ db2 quiesce tablespaces for table staff reset
DB20000I The QUIESCE TABLESPACES command completed successfully.

Document information

More support for: DB2 for Linux, UNIX and Windows
Database Objects/Config - Tablespaces

Software version: 9.5, 9.7, 9.8, 10.1, 10.5

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Software edition: Advanced Enterprise Server, Enterprise Server, Workgroup Server

Reference #: 1655443

Modified date: 10 February 2014

Translate this page: