I've never seen this message before. My sql was creating a table.

DBD::Oracle::st execute failed: ORA-01658: unable to create INITIAL extent
for s
egment in tablespace CHG_AGENT_DATA (DBD ERROR: OCIStmtExecute) at blah,
blah, blah

Am I out of tablespace?

Mike

Michael Hill wrote:

> I've never seen this message before. My sql was creating a table.
>
> DBD::Oracle::st execute failed: ORA-01658: unable to create INITIAL extent
> for s
> egment in tablespace CHG_AGENT_DATA (DBD ERROR: OCIStmtExecute) at blah,
> blah, blah
>
> Am I out of tablespace?
>
> Mike
>
>

No, you initial extent is bigger than what you can handle.
So, well, actually - you are out of tablespace! The point is,
you probably have "enough" tablespace left; you're just trying
to allocate a huge chunk. Probably no need for it.

Versions of Oracle might help. This message used to be quite common
in the pre 9i days, with dictionary managed tablespaces, and an export
with import, using default parameters (compress=Y, which is a no-no!)

State the initial extent clause on your create table statement,
and check what your tablespace has got as initial - as you have
found out, even empty tables use a *lot* of space.

And change to locally managed tablespaces with reasonable storage
parameters (where reasonable would be something along the line of
"your largest object should not have thousands of extents"), and
stop worrying about extents.

--

Regards,
Frank van Bortel

"Michael Hill" <hillmw@charter.net> wrote in message news:<10p1pavm42chk36@corp.supernews.com>...
> I've never seen this message before. My sql was creating a table.
>
> DBD::Oracle::st execute failed: ORA-01658: unable to create INITIAL extent
> for s
> egment in tablespace CHG_AGENT_DATA (DBD ERROR: OCIStmtExecute) at blah,
> blah, blah
>
> Am I out of tablespace?
>
> Mike

Mike, you might be out of tablespace, but you could also just be
requesting a huge initial extent that is larger than any free extent
in the target tablespace.

You can query dba_free_space to see how much and in what size chunks
free space exists for a tablespace.

If the target database is version 8.l or higher locally managed
tablespaces with uniform extents are a wonderful thing for managing
(predicting) tablespace growth and eliminating the free space
fragmentation problem of dictionary managed tablespaces.

HTH -- Mark D Powell --

Michael Hill wrote:

> I've never seen this message before. My sql was creating a table.
>
> DBD::Oracle::st execute failed: ORA-01658: unable to create INITIAL extent
> for s
> egment in tablespace CHG_AGENT_DATA (DBD ERROR: OCIStmtExecute) at blah,
> blah, blah
>
> Am I out of tablespace?
>
> Mike

1. Version?
2. Operating system?
3. Available space in tablespace?
4. Available space on physical disk?

--
Daniel A. Morgan
University of Washington
damorgan@x.washington.edu
(replace 'x' with 'u' to respond)