Riyaj, The key is the "instance X" option. Oracle documentation is not clear on this. The only thing I find at this time is in 8i OPS Admin Guide: http://download-west.oracle.com/docs/cd/A87860_01/doc/paraserv.817/a76970/partfrls.htm "Unused space you have allocated to an instance using the ALLOCATE EXTENT command cannot be deallocated. This is because it exists below the high water mark." I have a test done with a non-ASSM tablespace: http://yong321.freeshell.org/oranotes/Dbms_Space.txt It may not apply if you use ASSM. Yong Huang --- Riyaj Shamsudeen <riyaj.shamsudeen@xxxxxxxxx> wrote: > Yong > I must be missing something here. Just to clarify, are you saying that > allocating an extent add space under HWM? Do you have any reference or test > case? > > >> alter table theBLOBtable modify lob (theBLOBcolumn) (allocate extent > (instance 1)); > >> Remember to include the "instance 1" so space is added below HWM, even if > you're not using RAC (ignore documentation's caution: only use it on RAC). > > Thanks > Riyaj Shamsudeen > The Pythian Group > orainternals.wordpress.com > > On Sun, Apr 20, 2008 at 8:58 PM, Ravi Gaur <ravigaur1@xxxxxxxxx> wrote: > > > Yong, we already applied the patch 6376915 in Sep 07. We also use ASSM > > still there are HW enqueue waits. I think the only other thing to try out > > would be to preallocate extents to the LOB tables. Let me know if you've > any > > other ideas. > > > > Thank you. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ -- //www.freelists.org/webpage/oracle-l