Free chunk available

Question

Hi all,
In my PROD so many times I found that the tatol size of a tablespace remains is fair enough but the largest chunks availabe is very less and becouse of that it happens that a transaction fails and gives error in alert log file like:
ORA-1654: unable to extend index APPS.RCV_RECEIVING_SUB_LED_N3 by 27310 in tablespace GLD
and as a workaround I need to resize it database / add datafile and issue resolved.
But before add/resize of datafile when I checked the datafile free space available and the largest chunk is found:
select TABLESPACE_NAME,
sum(BYTES/1024/1024) Total_free_space,
max(BYTES/1024/1024) largest_free_extent
from dba_free_space
where tablespace_name='GLD'
group by TABLESPACE_NAME;
TABLESPACE_NAME TOTAL_FREE_SPACE LARGEST_FREE_EXTENT
GLD 5516.0546875 9.765625
I thin 5516 MB of free space is fair enough for a tbs. but still I am getting error to this tbs.
can any body give any idea what wrong with this.
Thanks in ADV !

Answer 1

Hi,
I have done the same. There is a sql script running on contab and let me knwo through mail the status of the tbs (name, %use, total size, total free, largest chunk avai etc).
Now there is a tbs (still not gone in any error) whose size is :
TABLESPACE_NAME % used TOT_SIZE_MB TOT_FREE_MB PCT_FREE LARGEST_CHUNK CHUNKS_FREE
ENID 88.25 750 529.375 11.75 29.38 1
Now within 2 or 3 days this will go in error as discribed above and as a workabound I need to resize/add datafile. You can see there is good space free.
Now as per the logic if a record is bigger with this largest chunk availabe wiil go in error becoz it needs the big chunk to store in db block.
Becouse of this I need to know that is ther any way to increase this largest_chunk for this tbs to avoid the error in future.
Thanks
Edited by: user9141007 on 21 Dec, 2010 11:37 PM
Edited by: user9141007 on 21 Dec, 2010 11:38 PM