Your container output shows me that your tablespace is almost completely empty, so why are you worried about rebalancing? Rebalancing an empty db should take no time at all
Maybe your output is out of date, so it does not reflect the current state of the tablespace? Even if that is so, I would still make all containers the same size and take the hit for rebalancing. Do it off hours if you think it will be too intrusive - although I have never experienced a hugely significant slow down during a rebalance that cannot be lived with.
Another point: why are you creating different sized containers for the same tablespace in the first place? I guess that is why you wish to increase the last one - maybe to match the other 2?
As a general rule, containers should be of the same size at the start. Matter of fact a few versions of DB2 and AIX ago you had to make all containers exactly the same (for a single DMS tablespace). If you didn't, all containers would only fill to the size of the smallest container. This has since been fixed, but I still recommend making them all the same.
When you increase sizes in the future, make sure you increase all of them together and at the same amount. It just makes it easier to manage.
I am worried about rebalancing because 2 weeks back this tablespace was hitting almost 90%, so I had to add more pages and right after I added these pages DB2 started rebalancing right away (stupid feature of DB2 that you can't let the rebalancing happen at some other time) and the system could not handle it and so the instance crashed. We had lot of trouble because the instance would just not start up. So finally we had to restore the database and rollforward just before the rabalancing happened because according to the IBM support, rebalancing caused data corruption.
My output is actually upto date and you are right I want to increase the third container to make them all same size. I understand its not a good idea to have different sizes of conatiners under one tablespace, but this has not been designed by me, all i can do is find ways to improve things and that is when i seek help from gurus at this forum as I have started working on DB2 few months back and I am still exploring lot of stuff about Db2.
whenever i want to add more space to a tablespace I always increase all the containers at one go. this is the command that I use:
alter tablespace LADATA16k extend (all 1000)
But i am sure this command does not get rid of the rebalancing.
One more thing I would like to add. You said that the containers are almost completely empty after looking at the output that I sent.
How did you get to know this?
Please correct me if I am wrong the "list tablespace containers for 3 show detail" command only shows the total pages and Useable pages, the output does not talk about the used pages at all.
Sorry Anks, my mistake. I mistook the "useable" pages as free. My bad.
You can also run -
db2 list tablespaces show detail
and it will show the used and free pages for all tablspaces, but not for each individual container.
Here is something you may be able to do though: try a redirected restore. This method is usually used to restore a database into another instance (typically on another machine), but can be used to add or subtract containers.
Search through the recent threads from the last month or so. I did a quick write up on how to do a redirect if you have a full offline backup