I think you got it wrongly interpreted.
SMS -
As you drop a table, the table is actually a file in the SMS drirectory
container and the file is erased and the space is immediately reclaimed
at the file system level.
DMS-
Since the container is either a file or a raw device, the space WITHIN
that file is immediately reclaimed and made available but only to the
objects that have been created using that tablespace.
Since the file system space is allocated at creat tablespace time and
remains fixed unless you alter tablespace, then the sdpace NOT reclaimed
at the file system level.
To reclaim DMS dropped tables space from the file system in a DMS
container, you will have to "play" with the High Water Mark of the
containers and with the alter tablespace option of reduce or drop.
HTH, Pierre.
Yasaswi Pulavarti wrote:
Hi Mark:
So it there a command to force DMS to reclaim space on the OS as well?
Or by very definition that space is preallocated to DMS tablespaces, I
can never reclaim OS space on filesystem or specifically in the
"container".
Thanks,
Yasaswi
-------------------------
m0****@yahoo.com (Mark) wrote in message news:<a5**************************@posting.google. com>...
ya*****@encfor.com (Yasaswi Pulavarti) wrote in message news:<aa**************************@posting.google. com>...
does a command like,
db2 drop table tabschema.tabname when run from the Aix prompt reclaim
the disk space? Are there any other options? How can we make sure the
disk space is reclaimed?
Thanks,
Yasaswi
Do you mean reclaim within the tablespace? or do you mean reclaim
within the file system?
If the tablespace is SMS you will reclaim space within the file
system.
If it is DMS it will reclaim space within the tablespace for other
tables/indexes to be created within the same tablespace, but it will
not reclaim space for the file system.
--
Pierre Saint-Jacques - Reply to: sescons at attglobal dot net
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.