In both the type of tablespaces- partition by growth and partition by range, one also specifies SEGSIZE parameter.
Now to put my question, suppose i want to create a partition by growth table, with MAXPARTITIONS 10, and SEGSIZE 64 and DSIZE 4Gb.
After creating my tablespace,table and indexes, i handover the table to application team. Now as we know that a segmented tablespace has a maximum limit of 64gb. Also in partitioned tablespace we give partition keys.Howver in partition by growth table, we do not give limit keys.
So now my doubt and question is that at what point DB2 will start creating the partitions? After the data has grown to 4Gb(DSSIZE Value) or after the maximum limit for the segmented tablespace is reached?
Then as data grows, and the partition 10 gets full, and one does alter for MAXPARTITION to set it to new higher value.Does this pose any recovery threat/concern as in case of improper ROTATE partitions?
As i've never used these new tablespace, so it will be really helpful, if i can get our esteemed members experience.
Please do share or point at any whitepaper or presentation related to this.