When reorganizing a tablespace with data files using SAPDBA, an ORACLE error occurs when recreating the tablespace: Too little space in the file system although the SAPDBA space check showed sufficient space.
During the space check, SAPDBA does not only take into account the space available before the reorganization, but also the space released in each file system when old files are deleted.
If these files are also blocked by processes other than ORACLE, the database data files can be deleted in UNIX (not in NT) by SAPDBA, but the space in the file system cannot be released until the file pointers have been released by the blocking process.
When starting SAPDBA, note warnings of the type sqldba/svrmgr running, other SAPDBA running, file manager running,...
If SAPDBA is running and a memory space error has occurred:
Terminate all processes locking the data files, if necessary shut down the database and reopen it.
Then restart the reorganization with the SAPDBA "restart" option.
Additional key words
filesystem, freespace
No comments:
Post a Comment