Troubleshooting
Problem
When /tmp path is not permitted to write/read/execute for instance users, "db2 list tablespaces" will show the 0x4000 in temp tablespaces. Even if you drop and recreate the temp tablespace it will be 0x4000 or "Offline and not accessible"
Symptom
When your /tmp path does not have permission for instance users,
you will see the result like as follows in "db2 list tablespaces"
-------------------------------------------
v97_07@woongc1:~> db2 list tablespaces
Tablespaces for Current Database
Tablespace ID = 0
Name = SYSCATSPACE
Type = Database managed space
Contents = All permanent data. Regular table space.
State = 0x0000
Detailed explanation:
Normal
Tablespace ID = 1
Name = TEMPSPACE1
Type = System managed space
Contents = System Temporary data
State = 0x4000
Detailed explanation:
Offline
Tablespace ID = 2
Name = USERSPACE1
Type = Database managed space
Contents = All permanent data. Large table space.
State = 0x0000
Detailed explanation:
Normal
Tablespace ID = 3
Name = SYSTOOLSPACE
Type = Database managed space
Contents = All permanent data. Large table space.
State = 0x0000
Detailed explanation:
Normal
Tablespace ID = 4
Name = SYSTOOLSTMPSPACE
Type = System managed space
Contents = User Temporary data
State = 0x4000
Detailed explanation:
Offline
-------------------------------------------
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
30 April 2025
UID
swg21999841