IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

LIMITKEY col in SYSTABLEPART - Table Controlled Partitioning


IBM Mainframe Forums -> DB2
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
dinesh_deadman
Warnings : 1

New User


Joined: 10 Aug 2007
Posts: 32
Location: Chicago

PostPosted: Thu Jan 15, 2009 10:41 pm
Reply with quote

Hello:

I have just created or rather changed an Index Controlled Partitioning to Table Controlled Partitioning by dropping partitioning index. And I expected the limit keys to be as below.

Code:
---------+---------+---------+---------+---------+---------+---------+---------
TSNAME                    DBNAME                    LIMITKEY
---------+---------+---------+---------+---------+---------+---------+---------
TABLESPC                  DATABASE                   'FM '
TABLESPC                  DATABASE                   'ZZZ'


For, my CREATE INDEX statement was like this before I decided to drop, in order to change PARTIONING TO Table Controlled...

Code:
CREATE TYPE 2 UNIQUE INDEX TST.TESTINDX
       ON TST.TEST_TABLE

       (COL_FIRST                       ASC
       ,COL_SECOND                   ASC
   .
   .
   .
       ,COL_LAST                  ASC  )
       CLUSTER
  (PARTITION 1    ENDING AT ('FM ')
                  USING STOGROUP SYSDEFLT
                        PRIQTY 720
                        SECQTY 720
                        ERASE NO
                  FREEPAGE 0
                  PCTFREE 15
  ,PARTITION 2    ENDING AT ('ZZZ')
                  USING STOGROUP SYSDEFLT
                        PRIQTY 720
                        SECQTY 720
                        ERASE NO
                  FREEPAGE 0
   .
   .
   .


After dropping this INDEX I received a warning 20272 CODE (this is expected) saying the tablespace has been converted to Table-Controlled Partitioning instead of Index-Controlled Partitioning.

Now, I try to look at the limit keys in the catalog table here is what I see.

Code:
---------+---------+---------+---------+---------+---------+---------+---------
TSNAME                    DBNAME                    LIMITKEY
---------+---------+---------+---------+---------+---------+---------+---------
TABLESPC                  DATABASE                   'FM '
TABLESPC                  DATABASE                   MAXVALUE,MAXVALUE,M


Does anyone have an idea why is it MAXVALUE,MAXVALUE... instead of 'ZZZ'???

DB2 V8 NFM - z/OS

Please let me know if I owe you any more information.
Back to top
View user's profile Send private message
sushanth bobby

Senior Member


Joined: 29 Jul 2008
Posts: 1020
Location: India

PostPosted: Sat Jan 17, 2009 6:16 pm
Reply with quote

Dinesh,

From the manuals
Quote:
After the conversion to table-controlled partitioning, DB2 changes the existing high-limit key value for non-large table spaces to the highest value for the key. Beginning in Version 8, DB2 enforces the high-limit key value. By default, DB2 does not put the last partition of the table space into a REORG-pending (REORP) state


Sushanth
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> DB2

 


Similar Topics
Topic Forum Replies
No new posts Load new table with Old unload - DB2 DB2 6
No new posts Pulling a fixed number of records fro... DB2 2
No new posts Multiple table unload using INZUTILB DB2 2
No new posts Check data with Exception Table DB2 0
No new posts Dynamically pass table name to a sele... DB2 2
Search our Forums:

Back to Top