DB2 tablespace silent status

If the DB2 tablespace is in the silent State, some operations such as sql00005n or SQL0290N may cause the tablespace to be inaccessible due to the silent operation.

Take the DB2INST1. STAFF table in the table space of DB2INST1. USERSPAC1 as an example:

A) silent DB2 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 space 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 tablespace to normal state 0x0000) to achieve normal access to tables in the DB2 tablespace.

If you try to use any DB2 user, run the following command to remove the silent State of the 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.
 

Create a DB2 tablespace in windows

Take you to the DB2 Character Set and MySql Character Set

DB2 update statements for records in the same table

How to expand the tablespace and Field Length in db2

Introduction to DB2 datetime Data Types