 |
|
ORA-01658: unable to create INITIAL extent for segment in
tablespace string tips
Oracle Error Tips by Burleson Consulting
|
Oracle docs note this about ORA-01658:
ORA-01658: unable to create INITIAL
extent for segment in tablespace
string
Cause: Failed to find sufficient
contiguous space to allocate INITIAL
extent for segment being created.
Action: Use ALTER TABLESPACE ADD
DATAFILE to add additional space to
the tablespace or retry with a
smaller value for INITIAL
Oracle MOSC offers
information regarding the very
common ORA-01658 in conjunction with
RME-02124. The symptoms appear
to be a repository installation
stopping short with this message:
ORA-01658: unable to create INITIAL
extent for segment in tablespace <name>
ORA-01658: unable to create INITIAL extent for segment in tablespace <name>
RME-02124: Failed to execute SQL statement:
create table i$SDD_DSTDIT ( irid number not null
, ivid number not null
, ...
, USRX19 VARCHAR2(240)
)
Storage (initial 500K next 500K pctincrease 5)
Tablespace <tablespace_name>
(208 objects installed).
ORA-01658: unable to create INITIAL extent for segment in tablespace <name>
ORA-01658: unable to create INITIAL extent for segment in tablespace <name>
RME-02124: Failed to execute SQL statement:
create table i$SDD_COL ( irid number not null
, ivid number not null
, ...
, USRX19 VARCHAR2(240)
)
Storage (initial 1000K next 1000K pctincrease 5)
Tablespace <tablespace_name>
(169 objects installed).
This case of ORA-01658 concerns needing to make
the tablespace bigger, which can be done by either extending your file, or
adding another one. This is a good solution for ORA-01658 because
repository tables need to be meticulously created keeping the extents of the
table in mind. Here is a small scale:
- SMALL will create tables with initial
extents of 100Kb.
- MEDIUM will create tables with initial extents of 500Kb.
- LARGE will create tables with initial extents of 1000Kb.
Which can then be applied to the repository:
Repository Size | Estimated Number of
Elements
---------------------------+--------------------------------
SMALL | Up to 20,000
MEDIUM | Between 20,000 and 100,000
LARGE | More than 100,000
With all of this in mind, ORA-01658 can be
resolved with proper consideration of existing and new tablespaces.
Here is another example of ORA-01658 from
Oracle
Network Forums.
A user has encountered ORA-01658 despite
efforts to make disk quota unlimited, and using oracle managed file type as the
datafile.
In order to properly resolve ORA-01658, the
results of SQL statement, SELECT
* FROM DBA_TABLESPACES; can be
analyzed:
TABLESPACE_NAME TESTDB
BLOCK_SIZE 4096
INITIAL_EXTENT 65536
NEXT_EXTENT
MIN_EXTENTS 1
MAX_EXTENTS 2147483645
PCT_INCREASE
MIN_EXTLEN 65536
STATUS ONLINE
CONTENTS PERMANENT
LOGGING LOGGING
FORCE_LOGGING NO
EXTENT_MANAGEMENT LOCAL
ALLOCATION_TYPE SYSTEM
PLUGGED_IN NO
SEGMENT_SPACE_MANAGEMENT MANUAL
In this case, the user was advised to make
the value of NEXT_EXTENT and INITIAL_EXTENT the same to clear up ORA-01658.
|
