that means , Oracle manages the space requirements for that tablespace locally and eleiminates the burden on data dictionary , and its a good deal for performance, coz oracle doesnt need to write/update the dictionary.
'EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1024K'
In the above syntax .. extents will be allocated to the objects in 1MB each time a request is generated.
If your extent is too big, your tablespace get extended less frequently. But your disk may not be used efficiently because you have more unused space in your tablespace.
Originally posted by mrvajrala Since this is a LOCALLY Managed tablespace , you can not check the DBA_FREE_SPACE for the un used space.
....SNIP.....
That's not true, I think you've confused that with localy managed temporary tablespace! For other permanent localy managed tablespaces DBA_FREE_SPACE still works the same way as in the old days.
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Bookmarks