-
CAn anybody explain the output of this query to me? Can you explain what free_blk, free_m, big_chunk_k, num_chunk mean in the output?
At what point should the output be considered alarming? And what action should be taken to fix this problem
SELECT tablespace_name, sum ( blocks ) as free_blk , trunc ( sum ( bytes ) /
(1024*1024) ) as free_m
, max ( bytes ) / (1024) as big_chunk_k, count (*) as num_chunks
FROM dba_free_space
GROUP BY tablespace_name
6
SQL> /
TABLESPACE_NAME FREE_BLK FREE_M BIG_CHUNK_K NUM_CHUNKS
------------------------------ ---------- ---------- ----------- -------
DATATBS 1368832 5347 421900 104
DATAINDX 750965 2933 407440 21
RBS 109518 427 167596 262
SYSTEM 16866 65 67180 8
TEMP 60394 235 132396 54
[Edited by clinton on 01-16-2001 at 10:20 PM]
-
free_blk: No. of available freespace blocks
free_m: Available freespace in MB
big_chunk_k: Biggest available extent/chunk of freespace in KB
num_chunk: No. of available chunks/extents of freespace
Second Q is totally depends on your environment and your data growth pattern etc., and not a general Q to answer.
