Storage Management: Prior to 9i , Tablespaces were Dictionary Managed, from 9i tablespaces are Locally managed.

All the Tablespaces can be created of the same size. In Dictionary Managed Tablespace, extent management information is stored in data dictionary tables. allocation and de allocation of storage of a space of objects are manipulating in data dictionary tables. In Locally Managed tablespaces, extent management information is stored in the header of the tablespace in the form of bitmap. In locally managed tablespaces, every time data has to be inserted in the tablespace, it will check the tablespace itself. Extent size is equal in locally managed. Storage Parameters: 1. Initial 2. next 3. PCTIncrease : will get increase on next extent. Always based on next extent. Based on the Hard disk, the size of the tablespace will get increased when Autoextend is On. Turning Autoextend On is not recommended for all the tablespaces as tablespace keeps on increasing for the next extent, so space in the file system keeps on increasing. In production environment, check the extent management of the tablespace and the allocation of extent Auto On/Off. To Check the free space in the tablespace: View: • DBA_Tablespaces • DBA_Free_Space Tablespace Management: • • • It is the highest component of the logical storage unit. Tablespace can have n number of datafiles and these datafiles must belong to one particular tablespace. Every table should belongs to the tablespace.

There are 3 ways to add space into tablespace: 1. By adding datafiles(alter tablespace)

By resizing datafiles (alter database) 3. By increasing the the size of tablespace. old value+new value.2. BYTES_FREE from V$TEMP_SPACE_HEADER. Datafile should contain no data or 900mb should be free space. To resize the datafile. . while shrinking the size of the datafile. To see the free space in tablespacec: select TABLESPACE_NAME. BYTES_USED.

Sign up to vote on this title
UsefulNot useful