Using DB2 Express-C 10.5.4 64bit on Win 7 Pro sp1 I have a 'LARGE' tablespace defined as follows:
CREATE LARGE TABLESPACE INDEXES_LONG IN DATABASE PARTITION GROUP IBMDEFAULTGROUP
PAGESIZE 4096 MANAGED BY AUTOMATIC STORAGE
USING STOGROUP SSD_INDEXES_LONG
INITIALSIZE 384 K
DATA TAG NONE
NO FILE SYSTEM CACHING
DROPPED TABLE RECOVERY ON;
This was recently changed to using automatic storage and moved to SSD containers by using the following command:
ALTER TABLESPACE INDEXES_LONG MANAGED BY AUTOMATIC STORAGE USING STOGROUP SSD_INDEXES_LONG;
The storage group is defined as :
CREATE STOGROUP SSD_INDEXES_LONG ON 'S:\DB2\CONTAINERS\TABLESPACES\SSD_INDEXES_LONG'
DEVICE READ RATE 500.000000
DATA TAG NONE;
Drive 'S' being a Samsung 830 256gb SSD. My problem however is that the old container was not automatically removed from the 'C' Drive nor has DB2 seemingly released it as it is still defined when querying 'SELECT * FROM TABLE(MON_GET_CONTAINER('',-2)) AS t'
I have tried to drop the offending container using the ALTER TABLESPACE command but now seeing as it is now defined as using automatic storage, the drop container command fails.
Anyone got any ideas as to how to get rid of the offending container ?? I have half a dozen or so tables defined using 'LONG IN INDEXES_LONG' in the table definition. I could leave it does not appear to be causing issues, it's just Messy ya know ?