Home » RDBMS Server » Server Administration » Extent allocaiton error
Extent allocaiton error [message #128701] Wed, 20 July 2005 03:53 Go to next message
vivekmenon_k
Messages: 9
Registered: March 2005
Location: India
Junior Member
I have a tablespace whose total/ free size are as follows

Total Size 2300mb
Used Size 1605mb
Free size 695 mb

this particular tablepsace contains just one table whose
extent sizes are as follows.

initail_extent-> 314572800
next_extent-> 104857600
max_extent-> 2147483645

As can be seen, even with such high value for max_extent and sufficent space left in tablespace,disk
my table in this tablespace is giving me an

ORA-1653 Unable to extend table TBADM.CUM_TRAN by 12800 in tablespace test.



1.Why is this happening/What is the reason?
2.How can this be avoided.
3.Is there an site from were Oracle extent allocation internal mechanism can be learned.

Thanks & Regards

Vivek
Re: Extent allocaiton error [message #128708 is a reply to message #128701] Wed, 20 July 2005 04:34 Go to previous messageGo to next message
girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)
Senior Member
HI

You are probably encountering tablespace fragmentation issue. Pls coalesce your tablespace & then see, if you still encounter this error.
eg: alter tablespace <tbs_name> coalesce;

Also, you must be using DMT (Directory managed tablespaces). Use LMTs (Locallay managed tablespaces) instead to avoid this fragmentation issue.


Regds
Girish
Re: Extent allocaiton error [message #128710 is a reply to message #128708] Wed, 20 July 2005 04:37 Go to previous messageGo to next message
vivekmenon_k
Messages: 9
Registered: March 2005
Location: India
Junior Member
How to check for database/tablespace fragmentation?

I tried coalescing, but it didn't help.It's a locally managed tablespace.

Re: Extent allocaiton error [message #128714 is a reply to message #128710] Wed, 20 July 2005 04:57 Go to previous messageGo to next message
girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)
Senior Member
HI

What type of extent management have to applied?
Is it Autoallocate or of uniform size? Also if uniform size, then what is the size that you have specified for it.

Regds
Girish
Re: Extent allocaiton error [message #128735 is a reply to message #128714] Wed, 20 July 2005 06:24 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
No information on oracle version/Operating system and scenario ( this errror was coming during this operation)..etc.

With the wealth of information provided, lets keep guessing.

Make sure you have autoextend on the concerned datafile(s).
Always use an uniform extent size (LMT or DMT)

[Updated on: Wed, 20 July 2005 06:39]

Report message to a moderator

Re: Extent allocaiton error [message #128738 is a reply to message #128735] Wed, 20 July 2005 06:37 Go to previous messageGo to next message
girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)
Senior Member
Hi Mahesh

Sorry... really forgot to ask....

Regds
Girish
Re: Extent allocaiton error [message #128870 is a reply to message #128708] Thu, 21 July 2005 00:37 Go to previous messageGo to next message
vivekmenon_k
Messages: 9
Registered: March 2005
Location: India
Junior Member
Its a locally managed tablespace with uniform extent size
Re: Extent allocaiton error [message #128981 is a reply to message #128701] Thu, 21 July 2005 07:52 Go to previous messageGo to next message
smartin
Messages: 1803
Registered: March 2005
Location: Jacksonville, Florida
Senior Member
Please show us a session of your activity. Everything you do starting from querying dba_tablespaces and data files and providing starting information, to a select * from v$version, and then running a sample of something that causes the error.
Re: Extent allocaiton error [message #128999 is a reply to message #128701] Thu, 21 July 2005 08:20 Go to previous message
Sanjay Bajracharya
Messages: 279
Registered: October 2001
Location: Florida
Senior Member
You free size is 650MB and your table next_extent size is 100MB.

What happened is oracle could not find a single continues segment of 100MB that's why you got the error. Don't get fooled with the TOTAL FREE size.

Solution :
1. Add more space Cool
or
2. decrease the next_extent size for the table. Razz

You max extent is set to UNILIMITED and this is fine.

-
Sanjay

[Updated on: Thu, 21 July 2005 08:20]

Report message to a moderator

Previous Topic: ORA-00600: internal error code, arguments: [17182]
Next Topic: DBW0: terminating instance due to error 1092
Goto Forum:
  


Current Time: Fri Jan 10 07:50:47 CST 2025