Purescale Automatic storage management

Problem

DB2 pureScale environment, only MANAGED BY AUTOMATIC STORAGE tablespaces. Here are the restrictions http://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5.0/com.ibm.db2… Neither 'REDUCE MAX' or 'LOWER HIGH WATER MARK' is supported in purescale environment Altering database containers is not supported in a DB2 pureScale environment. As a result, the following clauses are not supported with the ALTER TABLESPACE statement in a DB2 pureScale environment: * ADD * BEGIN NEW STRIPE SET * DROP * LOWER HIGH WATER MARK * LOWER HIGH WATER MARK STOP * REBALANCE * REDUCE * REDUCE + LOWER HIGH WATER MARK action * RESIZE * USING STOGROUP The way to work around that would be to use db2dart /LHWM with admin_table_move() and ALTER TABLESPACE REDUCE. *********** However sometimes problem may arise while extenting this automatic storage as follows Tablespace ID                        = 6 Name                                 = TS_ED_32K Type                                 = Database managed space Contents                             = All permanent data. Regular table space. State                                = 0x0000    Detailed explanation:      Normal Total pages                          = 16777216 Useable pages                        = 16776960 Used pages                           = 16776960 Free pages                           = 0 High water mark (pages)              = 16776960 Page size (bytes)                    = 4096 Extent size (pages)                  = 256 Prefetch size (pages)                = 1536 Number of containers                 = 1 Minimum recovery time                = 2016-06-28-10.58.45.000000 Here free pages are 0 ,and neither the above methods also work. The reason is ,even though its automatic storage is used in purescale, there is size restrictions for the given pagesize. Here is details in below link http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.lu… So as an example the above tablespace of 4k page has reached size to (16776960 X 4K) which is 63.999G and has reached the size restrictions for 4K page. Here the solution is to create a new tablespace with new pagesize and use admin_move_table to move data to new tablespaces.