How can I reset the silent State of the DB2 tablespace? This is a problem that many people have mentioned. The following describes how to reset the silent State of the DB2 tablespace for your reference.
Correct Method to reset the silent State of the DB2 tablespace:
The cause is that the reset operation is incorrect. The RESET option of the silent command takes effect only when executed by the user who previously issued the silent command. Even if another RESET is successfully executed, the silent State set by the original user cannot be removed. Therefore, the correct steps to remove the silent State of the DB2 tablespace are as follows:
A) users looking for silent tablespace:
With the reports generated by the db2dart tool, we can query the users who issued the QUIESCE command. The procedure is as follows:
B) stop a DB2 instance:
Db2stop force
C) generate the DB2DART report:
Db2dart <database alias>/DTSF
D) Find the user who sends the silent command from the report:
According to the command execution result prompt, find the report file generated by DB2DART and open the file. For silent tablespace, you can find similar information in the file:
- Information for Tablespace ID: 2
- -------------------------------------
-
- Tablespace name: USERSPACE1
- Table space flags (HEX): 0101
- Table space type: System Managed Space (SMS)
- Page size: 4096
- Extent size: 32
- Prefetch size: 32
- Version: 9
- Tablespace state: 2
- Number of quiescers: 1
-
- 1) Userid of quiescer: DB2INST1
- Quiesce state: 2
- Tbspace ID of quiesced object: 2
- Table ID of quiesced object: 3
- EDU ID: 0
- Agent ID: 0
- ......
-
So that the earliest user who sent the silent command is DB2INST1.
E) Perform the reset operation with the correct user logon:
Run the reset command after logging on to the DB2INST1 User:
Db2 quiesce tablespaces for table db2inst1. staff reset
Connect to the database after the command is successful
F) Verify the tablespace status:
- db2 list tablespaces
-
- ......
- Tablespace ID = 2
- Name = USERSPACE1
- Type = System managed space
- Contents = Any data
- State = 0x0000
- Detailed explanation:
- Normal
- ......
-
The preceding output indicates that the reset silent command is successfully executed, and the tablespace status is normal. All Tables in the table can be accessed normally. Now, the operation to remove the DB2 tablespace silent status and restore the tablespace status to normal is completed.
Silent state of the DB2 tablespace
How to Set garbled characters in the DB2 code page
Implementation of DB2 string connection
DB2 update statements for records in the same table
How to expand the tablespace and Field Length in db2