SMS TableSpace - Reorg not releasing space.

Question posted by: Patrick Finnegan (Guest) on June 30th, 2008 04:45 PM

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?

Would you like to answer this question?
Sign up for a free account, or Login (if you're already a member).

Mark A

Guest

n/a Posts

June 30th, 2008
10:05 PM
#2

Re: SMS TableSpace - Reorg not releasing space.

"Patrick Finnegan" <finnegan.patrick@gmail.comwrote in message
news:ea223638-743d-48f0-b590-b0f0b0413b4b@d1g2000hsg.googlegroups.com...

Quote:

Originally Posted by

>
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?

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.

Not the answer you were looking for? Post your question . . .
180,794 Experts ready to help you find a solution.
Sign up for a free account, or Login (if you're already a member).

Didn't find the answer you were looking for?
Post Your Question

Top Community Contributors