The problem is that you still have objects in the tablespace using extents high up in the file. You can look into the tablespace with the following query to see what objects are using space: select * from dba_extents where tablespace_name='{tablespace_name}' order by block_id desc You can then move the offending objects to force them to use free extents elsewhere in the tablespace: Alter table {table_name} move {tablespace_name} Alter index {index_name} rebuild {tablespace_name} Tom -------------------------------------------------------- This transmission may contain confidential, proprietary, or privileged information which is intended solely for use by the individual or entity to whom it is addressed. If you are not the intended recipient, you are hereby notified that any disclosure, dissemination, copying or distribution of this transmission or its attachments is strictly prohibited. In addition, unauthorized access to this transmission may violate federal or State law, including the Electronic Communications Privacy Act of 1985. If you have received this transmission in error, please notify the sender immediately by return e-mail and delete the transmission and its attachments. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of dba1 mcc Sent: Thursday, May 17, 2007 10:54 AM To: oracle-l@xxxxxxxxxxxxx Subject: check high wate mark on tables?? we have ORACLE on version 9.2.0.8. after we truncate sever tables, we still can NOT shrink data file due to high water mark did not change. Does there has way to check which table after truncate high water mark no chage? Thanks. ________________________________________________________________________ ____________ Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/ -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l