Database Reference
In-Depth Information
Full Blocks ............................ 153,076
Total Blocks............................ 166,400
Total Bytes............................. 1,363,148,800
Total MBytes............................ 1,300
Unused Blocks........................... 0
Unused Bytes............................ 0
Last Used Ext FileId.................... 5
Last Used Ext BlockId................... 153,728
Last Used Block......................... 12,800
PL/SQL procedure successfully completed.
EODA@ORA12CR1> exec show_space('AUTOALLOCATE_TEST' );
Unformatted Blocks ..................... 0
FS1 Blocks (0-25) ...................... 0
FS2 Blocks (25-50) ..................... 0
FS3 Blocks (50-75) ..................... 0
FS4 Blocks (75-100)..................... 0
Full Blocks ............................ 153,076
Total Blocks............................ 153,696
Total Bytes............................. 1,259,077,632
Total MBytes............................ 1,200
Unused Blocks........................... 0
Unused Bytes............................ 0
Last Used Ext FileId.................... 6
Last Used Ext BlockId................... 147,584
Last Used Block......................... 6,240
PL/SQL procedure successfully completed.
■
Note
the
SHOW_SPACE
procedure is described in the “Setting up Your environment” section at the beginning of
this topic.
Notice that the autoallocated table shows 1,200MB used space vs. 1,300MB used for the uniform extent table.
This is all due to the extent trimming that
did not
take place. If we look at
UNIFORM_TEST
, we see this clearly:
EODA@ORA12CR1> select segment_name, extent_id, blocks
2 from user_extents where segment_name = 'UNIFORM_TEST';
SEGMENT_NAME EXTENT_ID BLOCKS
-------------------- ---------- ----------
UNIFORM_TEST 0 12800
UNIFORM_TEST 1 12800
UNIFORM_TEST 2 12800
UNIFORM_TEST 3 12800
UNIFORM_TEST 4 12800
UNIFORM_TEST 5 12800
UNIFORM_TEST 6 12800
UNIFORM_TEST 7 12800
UNIFORM_TEST 8 12800
UNIFORM_TEST 9 12800
