Re: unable to create INITIAL extent

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