Tablespace Offline

[newsg...@rick_austin.net]

We have a customer that has a proplem where the default temporary
tablespace (TEMPSPACE1) is offline with a state of (0x4000). I've
found plenty of information on how to deal with a tablespace that is
in some type of pending state but not for offline. I intend to
recommend that they create a new temporary tablespace and then
eventually drop the TEMPSPACE1 tablespace. Is there a better approach?

Here is the LIST TABLESPACE output for this tablespace:
Tablespace ID = 1
Name = TEMPSPACE1
Type = System managed space
Contents = System Temporary data
State = 0x4000
Detailed explanation:
Offline

Here is information on this from db2diag.log:
2003-06-12-12.36.21.617000 Instance:DB2 Node:000
PID:1600(db2syscs.exe) TID:488 Appid:C0A80140.550A.030612135048
buffer_pool_services sqlbGetSysTempDatapool Probe:20
Database:CPPARMS

A useable temporary tablespace of pagesize 4096 was not found.

Diagnostic information:

Tablespace ID: 1
Pool flags: 0x00000111
Pool state: 0x00004000
Latch error: 0x00000000

2003-06-12-12.36.21.695000 Instance:DB2 Node:000
PID:1600(db2syscs.exe) TID:488 Appid:C0A80140.550A.030612135048
buffer_pool_services sqlbGetSysTempDatapool Probe:20
Database:CPPARMS

Requested page size: 4096
Number of system temporary tablespaces: 1
Last used system temporary tablespace: 1

0300 0000 0200 0000 0100 0000 0000 0000 ................
0000 0000 0080 0000 0000 0000 0000 0000 .....€..........
0100 0000 0100 0000 0000 0000 0000 0000 ................
0000 0000 60d8 b504 ....`ص.

[PM (pm3iinc-nospam)]

State = Offline and not accessible
alter tablespace switch online
http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/v8infoce
nter.d2w/report?target=mainFrame&fn=t0008953.htm
http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/v8infoce
nter.d2w/report?target=mainFrame&fn=c0005964.htm

You should also verify the underlying containers / list tablespace
containers for x show detail.
Verify them for hardware problems, etc.

List history may show somethig about tablespace recent operations.

PM

<newsgroups@rick_austin.net> a écrit dans le message de news:
7uqjevcb7q614ikqg...@4ax.com...

> 0000 0000 0080 0000 0000 0000 0000 0000 .....?..........

> 0100 0000 0100 0000 0000 0000 0000 0000 ................

> 0000 0000 60d8 b504 ....`ص.
>
>

[Rick Austin]

Thanks for that information. I asked the customer to execute the
following statement on that tablespace:

ALTER TABLESPACE TEMPSPACE1 SWITCH ONLINE

Interestlingly enough the status of the table is now different. It
came back that the tablespace is read only:

SQL0970N The system attempted to write to a read-only file.
SQLSTATE=55009

That is very different than the original tablespace state of 0x4000.

All I know to do at this point is to create a new temporary tablespace
and then drop the existing.