Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
before truncating that table i checked the size using segment then i checked that result in toad too.
Same 4.7GB it shows,So i confirmed and then proceed to trucate.
now that table occupies
1886051 (present rec-count)rec within two weeks.
may be b'cos of this it might have shown this result.
bore..,
by using dba_data_files & dba_extents we can find how much one can resize the datafile(by giving block size).
So for resizing i joined these two tables and found the size(that can be resized).
dba_free_space gives you overall Freespace in that tablespace.
but from that one cannot resize the datafile because it may contain data.
Bore you know better than me.
if u need i will post that query how to find space in datafile that can be resized.without finding that how much can be resized in each datafile.If any tries to resize it shows error stating that
file contains used data beyond requested resize value..
Last edited by ams-jamali; 05-30-2007 at 05:57 AM.
Bookmarks