Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SMS TableSpace - Reorg not releasing space.

9 views
Skip to first unread message

Patrick Finnegan

unread,
Jun 30, 2008, 12:44:17 PM6/30/08
to

Running DB2 9.1 on Redhat Linux 4.1.

Storage management indicates that the pages stored in a file based SMS
container occupy 7 gig of the total space allocated which is 50gig. I
wrote a script to reorg and runstat all the tables in the tablespace
but the reorgs are not releasing space to the file system. Is there
anything that would cause this?

Mark A

unread,
Jun 30, 2008, 6:02:14 PM6/30/08
to
"Patrick Finnegan" <finnegan...@gmail.com> wrote in message
news:ea223638-743d-48f0...@d1g2000hsg.googlegroups.com...

You are probably mistaken. What makes you think storage is not being
released?

Keep in mind that a table can actually get larger after a reorg, since DB2
will recreate the percent free on each page (default is 10%). This percent
free may have been used during inserts.


peter

unread,
Jun 30, 2008, 11:35:13 PM6/30/08
to
On Jul 1, 8:02 am, "Mark A" <nob...@nowhere.com> wrote:
> "Patrick Finnegan" <finnegan.patr...@gmail.com> wrote in message

Depending on the order of reorg one or more tables may have pages at
still at a high page number. That is, the first tables re-orged may
not have found free space at a low level. You may have to re-org
again.

When the tablespace becomes large there is another issue with the free
space map as this has to be generated every x number of pages (forget
the number). It may have generated this free space map therefore
cannot reduce the size below this point. Again from memory, the
solution is to add and drop containers.

0 new messages