Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2002
    Posts
    15

    Unanswered: Orphaned Tablespace container

    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
    AUTORESIZE YES
    INITIALSIZE 384 K
    MAXSIZE NONE
    EXTENTSIZE 16
    PREFETCHSIZE 16
    BUFFERPOOL INDEXES
    DATA TAG NONE
    OVERHEAD 0.075000
    TRANSFERRATE 0.030000
    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'
    OVERHEAD 0.075000
    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'

    INDEXES_LONG 39 C:\db2\containers\tablespaces\INDEXES_LONG 0 0 FILE_EXTENT_TAG 0 0 0 0 0 2 0 0 0 0 0 1 0 256000 255984 1 3124103852 499273166848 164723785728 0
    INDEXES_LONG 39 S:\DB2\CONTAINERS\TABLESPACES\SSD_INDEXES_LONG\DB2 \NODE0000\SQ4TEST\T0000039\C0000000.LRG 1 0 FILE_EXTENT_TAG 1 0 0 0 0 0 0 0 0 0 0 0 0 32 16 1 3894892 230504407040 93031698432 0 12288

    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 ?

    Thanks, Tim.

  2. #2
    Join Date
    Oct 2002
    Posts
    15
    Never mind, problem solved with a rebalance.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •