Silent status of three DB2 tables

The silent State of the three DB2 tables is described in detail below. The DB2 database can use the QUIESCE command to silent the table space where the table is located, hoping to help you learn the silent State of the DB2 table.

For DB2 databases, you can use the QUIESCE command to silent the table space. The basic syntax of the command is:

Db2 quiesce tablespaces for table <> <silent status>

DB2 table silent states are 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.

Troubleshooting of DB2 database detachment

How to detach a DB2 database

How to manually Uninstall a DB2 database

Five situations in which DB2 deletes duplicate records

Nine common DB2 commands