Hi,

I am having trouble with "quiesce tablespaces" command on db2. I ran this command for a table and it made the tablespace on which the table resides inactive as intended.
I used "QUIESCE TABLESPACES FOR schema.table_name EXCLUSIVE".
Then I ran "QUIESCE TABLESPACES FOR schema.table_name RESET" to make the tablespace available again.This command ran correctly but still, I can't access the tablespace. When I try to create a new table on that tablespace for example, it says "Tablespace access is not allowed".
I must say that I was connected with "db2admin" user when I ran both commands (on the same table).

See the link DB2 Universal Database for QUIESCE TABLESPACE info.


Thanks!

Disconnect. And run it again script with RESET

Did it already. Even restarted the server. I still have 2 processes running that can't be killed: "db2taskd" and "db2stmm". They are running on "*LOCAL.DB2.090318092915" and "*LOCAL.DB2.090318092916" O.S. App IDs.
Maybe it's something related to these processes.
What should I do?

What does "list tablespaces show detail" tell you about that tablespace?

PS. You should always indicate your platform and the DB2 version when you ask questions.

I use DB2 v9 on Windows XP SP2, sorry.

It shows:

Tablespace ID = 2
Name = USERSPACE1
Type = Database managed space
Contents = Long data only
State = 0x0004
Detailed explanation:
Quiesced: EXCLUSIVE
Total pages = 8192
Useable pages = 8160
Used pages = 0
Free pages = 0
High water mark (pages) = 0
Page size (bytes) = 4096
Extent size (pages) = 32
Prefetch size (pages) = 32
Number of containers = 1
Number of quiescers = 1
Quiescer 1:
Tablespace ID = 2
Object ID = 15

I don't know why it says it is still quiesced since I ran the "QUIESCE TABLESPACES FOR TABLE DB2ADMIN.CHAR_TYPES RESET" command, which runs successfully.

Strange. I can't this reproduced on my DB2 server. Everything allright, EXCLUSIVE and after RESET - Normal.

Try increasing DIAGLEVEL to 4 and check what comes up in db2diag.log when you attempt to reset the quiesced state.

And just a wild guess: if you ran the quiesce exclusive command for several tables, may be you should run quiesce reset for the same tables, not just one?