Title: RE: Ora-1654 Unable to extend index on tablespace
Mitchell have you tried coalescing your tablespace? How big are your extents?
-Original Message-
From: Mitchell [SMTP:[EMAIL PROTECTED]]
Sent: Monday, June 25, 2001 5:28 PM
To: Multiple recipients of list ORACLE-L
Subject: Re
Title: RE: Ora-1654 Unable to extend index on tablespace
Hi DBAs
Whenever I have the ora-1654, I
will
1. alter index/table name deallocate unused
2. alter tablespace name coalescs;
3.runquerys to check dba_free_space and
dba_data_files
There are total 140 indexes on this tablespace
Mitchell,
I may well be wrong but check your db_block_size in v$parameter
eg
select name, value
from v$parameter
where name = 'db_block_size'
/
NAMEVALUE
db_block_size 4096
I think you have to multiply the reported figure by the blocksize to get the
extent size being
Title: RE: Ora-1654 Unable to extend index on tablespace
you
have 4K blocksize.
Check
your indexes. How often do they extend? how big are they? the NEXT
EXTENT size
may
not be appropriate. there is no pro forma way of knowing
hth
Hannibal
-Original
Message-From: Mitchell
You did not have enough contiguous space to build the extent.
-Original Message-
From: Mitchell [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 25, 2001 5:28 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: Ora-1654 Unable to extend index on tablespace
Dear DBAs
Could it be you don't have a contiguous segment at least 256? to satisfy the
request?
-Original Message-
Sent: Monday, June 25, 2001 4:28 PM
To: Multiple recipients of list ORACLE-L
Dear DBAs
I have a tablespace for index with 5 file with different size from
500mb - 2000 mb.
Mitchell wrote:
Dear DBAs
I have a tablespace for index with 5 file with different size from
500mb - 2000 mb.
Total tablespace size is 6g and used 5317mb abote 86.13% usage.
I got the error today.
ora-1654 unable to extend indx sechma.indexname by 256 in
Mitchll,
The index was trying to extend according to the next_extend parameter in
dba_segments for that object. From your message I can infer that the largest of
the available free space chunks in that tablespace was short 256 bytes. Try the
following query to tell you what is going on in
Check dba_free_space for the largest chunk available.
Also, note when it says temp segment, it has nothing to do with sorting or
temporary segments. This merely refers to the segment it is creating prior
to making it permanent segment.
Walking on water and developing software from a
