- Article Type: General
- Product: Aleph
- Product Version: 19.01
I see the suggestion in various Aleph documents to use util o/14/1 to check the space in our tablespaces, but it seems that the figures shown there are not correct. They seem too low, and tablespaces often appear in the "TABLESPACE_WITHOUT_FREE_SPACE" section but we never see any indication of a problem in the server logs or batch job logs.
If a tablespace has "AUTOEXTEND ON" specified for it, then Oracle will automatically create a new datafile when it runs out of space in the tablespace.
To see which datafiles have autoextend ON, you need to:
1. login to unix as the oracle user,
2. > sqlplus / as sysdba
3. SQL> select substr(file_name,1,50), AUTOEXTENSIBLE from dba_data_files;
If the tablespaces have AUTOEXTEND ON, then to determine whether there is sufficient space available, you must consider not only the freespace left in the tablespace as seen in util o/14/1, but the freespace (as seen in "df -k /xxxx") for the filesystem that the tablespace's datafiles reside on.
- Article last edited: 10/8/2013