Silent state of the DB2 tablespace

The DB2 tablespace is an important part of the DB2 database. The following describes the silent status of the DB2 tablespace for your reference.

The silent State of the DB2 tablespace:

For DB2 databases, the QUIESCE command can be used to silent the DB2 tablespace where the table is located. The basic syntax of the command is:

Db2 quiesce tablespaces for table <> <silent status>

The silent State of the DB2 tablespace is divided into the following three types:

SHARE ):
Place tables in the sharing mode. In this way, the transaction will attempt to request the intention to share the lock IS), the table requests the share Lock S), so all users, including yourself, can read but cannot change the table data.

Intent to update ):
Place the table in the update mode. In this way, the transaction will try to request the intention mutex lock IX) for the table space, and the table requests the update U) Lock. Therefore, you can update the table data only, other users can read but cannot update the data.

EXCLUSIVE ):
Make the table mutually exclusive. In this way, the transaction will try to request a super mutex lock Z for the table space and table), so you can only read or update the table data yourself.

If the table is already in a pause mode, you can change it to a more advanced and mutex mode. For example, if the table is already in the sharing mode, you can change it to the intention update or mutex mode. However, you cannot change the higher mode to the lower mode. The mutex level is higher than the intention update level, and the intention update level is higher than the sharing level.

Create a DB2 tablespace in windows

Implementation of DB2 string connection

DB2 update statements for records in the same table

How to expand the tablespace and Field Length in db2

DB2 strings in DB2 Databases