ORA-1654: unable to extend index SAP_U1 by 130 in tablespace IDXTB

Hi,

In error message

ORA-1654: unable to extend index SAP_U1 by 130 in tablespace IDXTB,

what does 130 means here, 130 bytes?

Thanks
ebi168Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

marianna6000Commented:
Hi,
are you using oracle 8i?

this is an out of space error- the system cannot get more extents for your index.
- check your temp tablespace using v$tempspace.maybe temp tablespace not big enough.you may need to increase it
- you may also want to check the size of your tablespace and increase this also
- check your system tablespace, and you may need to increase this also. if system tablespace is insufficient even if the object's tblespace is ok, will still not work.
- check MAX_EXTENTS or MAXEXTENTS (I think this depends on your version of oracle). This is the set maximum number of extents. you can change this parameter associated with your object.

hope that helps : )

Mari
0
muskware77Commented:
Hi,

130 is the number of blocks that Oracle is missing to extend your tablespace IDXTB.
Nothing to do with bytes. You may wish to extend your tablespace like this by adding for example a datafile:

ALTER TABLESPACE IDXTB
  ADD DATAFILE ....

Plse, see your doc for syntax specifics.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ebi168Author Commented:
Thanks for the information. One more question is that during data loading, oracle looks for one extent, then another,..., when it comes to the point it couldn't find another extent, it fails. By then it calculate and get that 130 blocks are missing. It is not like at the beginning of loading, it knows the problem and hauls. Am I right?
0
ebi168Author Commented:
In this case, are those data fit into the storage loaded into the table?
0
muskware77Commented:
Hi ebi168,
If i understand you correctly, you think Oracle despite the lack of space will
store the data in the available space and report an error with regard to the missing blocks. I'm afraid it doesn't work that way. I am confident Oracle will not add _any_ data in the table if space requirements are not met.

HTH.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.