Applications Systems
DPA fails to start and a database returns the error code ORA-01653
DPA fails to start, and an Oracle database returns the error code ORA-01653: ORA-01653: unable to extend table <SCHEMA_NAME>.<SEGMENT_NAME> by <nnnn> in tablespace <TABLESPACE_NAME> This article provides some remediation and troubleshooting steps.
First published date
Last published date
Overview
DPA fails to start, and an Oracle database returns the error code ORA-01653:
ORA-01653: unable to extend table <SCHEMA_NAME>.<SEGMENT_NAME> by <nnnn> in tablespace <TABLESPACE_NAME>
This article provides some remediation and troubleshooting steps.
Product section
Cause
- ORA-01653 indicates that Oracle could not extend the tablespace because there was not enough free contiguous space for Oracle to fit the next extent.
Resolution
The "by <nnnn>" (for example, "by 8192") in the error message indicates the number of blocks that Oracle tried to allocate but couldn't. To calculate the size of the extent, multiply the number of blocks with the block size. For example, if the block size is 8192 (8k), the extent size using the previous example would be 8192x8192, which is 67108864 bytes or 64 MB.
If the ALLOCATION_TYPE for the tablespace is AUTO (SYSTEM), the number of blocks that Oracle tries to allocate can vary.
To see the free space available for a particular tablespace, use the view DBA_FREE_SPACE. Within this view, each record represents one fragment of space. For more information, see DPA_FREE_SPACE (© 2018 Oracle, available at https://docs.oracle.com, obtained on March 7, 2018).
To add one or more files to the tablespace, use the ALTER TABLESPACE ADD DATAFILE statement. See Altering and Maintaining Tablespaces (© 2018 Oracle, available at https://docs.oracle.com, obtained on March 7, 2018).
For additional information, see ERROR:ORA-01653 (SCI29790) (© 2018 IBM, available at http://www-01.ibm.com, obtained on March 7, 2018).
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.