Failed to reset the silent State of the DB2 tablespace

Errors may occur when you reset the silent State of the DB2 tablespace. The following describes an example of a failure to reset the silent State of the DB2 tablespace for your reference.

A frequent failed reset operation:

Because of the existence of locking caused by silent operations, when performing some operations on such DB2 tablespace, an error message such as sql00005n or SQL0290N may occur, prompting that the tablespace is inaccessible. Take the DB2INST1. STAFF table in the table space of DB2INST1. USERSPAC1 as an example:

A) silent tablespace indicates the intention to update status:

Db2 quiesce tablespaces for table db2inst1. staff intent to update

B) the attempt to delete the table will fail:

Db2 delete from db2inst1. staff
DB21034E The command was processed as an SQL statement because it was not
Valid Command Line Processor command. During SQL processing it returned:
SQL0290N Table space access is not allowed. SQLSTATE = 55039

If:

Db2 list tablespaces

Run the following command TO check the DB2 tablespace status:

......
Tablespace ID = 2
Name = USERSPACE1
Type = System managed space
Contents = Any data
State = 0x0002
Detailed explanation:
Quiesced: UPDATE
......

To remove this silent State, you can use the "RESET" option in the silent command to restore the DB2 tablespace to the normal state 0x0000) to achieve normal access to tables in the table space.

If you try to use any DB2 user, run the following command to remove the silent State of the Multi-DB2 tablespace:

Db2 quiesce tablespaces for table db2inst1. staff reset
DB20000I The quiesce tablespaces command completed successfully.

We can see that the command has been successfully completed, but when we try the DELETE operation again, we still encounter the same SQL0290N error, that is, the tablespace cannot be accessed. Querying the table space status indicates that it is still in the silent State of the original intention update. Why does the preceding command successfully reset the silent State, but does not actually remove the silent State of the tablespace?

Silent status of three DB2 tables

Troubleshooting of DB2 database detachment

How to detach a DB2 database

How to manually Uninstall a DB2 database

DB2 table management statements