If you have space available on your disks and the space is not highly fragmented then do following: Check if your initial extent is not being explicitly set in the storage clause of your index. You could be taking it from the default value of the tablespace in which you are creating your index. I have seen cases where the default initial extent for tablespaces are set to unreasonably higher number such as 100M or even more. The best is that you control your extents in the storage clause of your objects.

Gurmohan

-----Original Message-----
From: Krystian Zieja
[mailto:oracledba-ezmlmshield-x91726966.[Email address protected]
Sent: Friday, July 29, 2005 4:14 AM
To: LazyDBA Discussion
Subject: Re: Unable to allocate initial extent !!!


Please chceck if you have sufficient free space in tablespace in which you
try ti create an index

Best Regards
Krystian Zieja
> Hi, folks,
> Whenever I'm trying to create a index(segment) I am running into 'Unable
> to allocate Initial extent error?
>
> What could be the work around..
>
> Kind Regards,
> Venugopal R.
> Technical Architect (Database).
>
>
> --------
> website: http://www.LazyDBA.com
> Please don't reply to RTFM questions
> Oracle documentation is here: http://tahiti.oracle.com
> To unsubscribe: see http://www.lazydba.com/unsubscribe.html
> To subscribe: see http://www.lazydba.com
> By using this list you agree to these
> terms:http://www.lazydba.com/legal.html
>
>




--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these terms:http://www.lazydba.com/legal.html

Oracle LazyDBA home page