Extent unlimited

Hi all,
I am getting
ORA-1653: unable to extend table HRI.HRI_CS_SUPH by 5 in tablespace HRID
ORA-1653: unable to extend table ENI.MLOG$_ENI_OLTP_ITEM_STAR by 130 in tablespace ENID
workaround to do " resize / add the datafiles as per metalink suggestion".
I have around 400+ tbs and don't know the number of tbs who are not set as maxextents unlimited.
Please suggest some query to find table + Index name who are not set as unlimited.
Thanks in ADV

dba1 wrote:
Hi all,
I am getting
ORA-1653: unable to extend table HRI.HRI_CS_SUPH by 5 in tablespace HRID
ORA-1653: unable to extend table ENI.MLOG$_ENI_OLTP_ITEM_STAR by 130 in tablespace ENID
workaround to do " resize / add the datafiles as per metalink suggestion".
I have around 400+ tbs and don't know the number of tbs who are not set as maxextents unlimited.
Please suggest some query to find table + Index name who are not set as unlimited.
Thanks in ADVHi, dba1.
Why do you think you have insufficient number of extents?
The error which you hit, is mostly due to insufficient space in tablespace.
bash-2.05$ oerr ora 1653
01653, 00000, "unable to extend table %s.%s by %s in tablespace %s"
// *Cause: Failed to allocate an extent for table segment in tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.Regards,
Teymur Hajiyev
Oracle 10g Certified Master
http://teymur-hajiyev.blogspot.com
http://dba.az

Similar Messages

ORA-01581: attempt to use rollback segment (5) new extent (67) which is being allocat

While importing a table, I got the following errors. Basically, the server couldn't extend the rollback segment. I checked the disk space, tablespace extents (unlimited), and segment extents (unlimited), but I couldn't find a reason that the segment couldn't be extended.
What else do I have to check?

As I understand it, you can not explicitly set the size for the undo segments in automatic undo management mode. From the Concepts guide:
"In automatic undo management mode, the system controls exclusively the assignment of transactions to undo segments, and controls space allocation for undo segments."
It looks like we are also using the default storage options that are set when the UNDO tablespace was created. Here is the DDL used to create this tablespace:
CREATE SMALLFILE UNDO TABLESPACE "UNDOTBS" DATAFILE '/alpha/oradata/prod01/undotbs01.dbf' SIZE 750M REUSE AUTOEXTEND ON NEXT 25600K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs03.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 51200K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs04.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 104K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs02.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 25600K MAXSIZE 2000M

ORA-01659: unable to allocate MINEXTENTS beyond 13 in tablespace TBSP1

Hi,
I am getting crazy on how to solve this error. :(
I still have 4Gb space in my TBSP1, what does "13" in the keyword "beyond" stands for? is it in bytes or blocks? which parameter can I see this number 13? Is it in tablespace/datafiles storage params or is it in create table parameter?
Thanks

Possible solutions:
**On the command prompt**
1.Make sure data file is not filled up and auto extend is on.
2.Try to add a data file or alter existing data file with auto extend capability and max extents unlimited.
alter database datafile '/..../fiilename.dbf' autoextend on maxsize unlimited;
3.Try de-fragmentation of tablespace that caused the problem.
alter tablespace TBSP1 coalesce;
**If you have TOAD, here is the best possible solution**
1. Go to database icon, click schema browser, set your schema as SYSTEM or SYS, then look for tablespaces tab below.
2. Click on the tablespaces tab, look for the tablespace that caused the problem,click the tablespace.
3. Click Basic Info tab, beneath that find extent management.
4. Click on auto allocate extent sizes.
5. Click OK button.
That`s it Problem is resolved.
-Regards
Rah

How to increase rollback segment

hi,
I am using oracle8i in solaris
I got a situation to increase rollback segment but i dont know how to do so?
can any one help me in solving this..........
I also want to know wat is the maximum max_extents size we can keep.....
This is my rollback segments
SQL> select segment_name, max_extents,TABLESPACE_NAME FROM dba_rollback_segs;
SEGMENT_NAME MAX_EXTENTS TABLESPACE_NAME
SYSTEM 121 SYSTEM
RBS 121 SYSTEM
RBS1 121 RBS
RBS2 121 RBS
RBS3 121 RBS
RBS4 121 RBS
RBS99 32765 RBS1
7 rows selected.
With Regards
Boo

If you have metalink access, there are really couple of good notes on how to tune and create optimal rollback segments.
Rollback Segment Configuration Tips Doc ID: Note:69464.1
Regarding the size of the rollback segment, it is depends on the nature of the application and the transaction size, whether short transaction or lenghty transactions.
If oltp with very small transaction, create rollback segment with very small value and make minextents 20, so that you dont need to have recursive call to create extents initially.
ORA-01628: max # extents (121) reached for rollback segment RBS1Make the extent unlimited.
ALTER ROLLBACK SEGMENT RBS1
STORAGE ( MAXEXTENTS UNLIMITED)
2) how many rollback segment can we hav?1 rollback segment = 4 concurrent transactions.
Now you decide, how many concurrent transaction do you have.
.3) what is the maximum extent size we can set?I would recommend to set the extent size according to nature of your application.
<<1) if there is more than one rollback segment in that, i want to know which one is active how to know this....... where to check this.........
SELECT r.name "RB NAME ", p.pid "ORACLE PID",
p.spid "SYSTEM PID ", NVL (p.username, 'NO TRANSACTION') "OS USER",
p.terminal
FROM v$lock l, v$process p, v$rollname r, v$session s
WHERE l.sid = s.sid(+)
AND s.paddr = p.addr
AND TRUNC (l.id1(+)/65536) = r.usn
AND l.type(+) = 'TX'
AND l.lmode(+) = 6
ORDER BY r.name;
Jaffar

Need inputs on the pros and cons of setting unlimited extents

Hi,
We are planning to set unlimited extents on all the DB tables inorder to avoid the frequent alerts and errors we get for TOO MANY EXTENTS. Now we are manually doing the changes in SE14.
But we hava a proposal of setting unlimited extents for all tables which we think will solve the issue.
Kindly provide our valuable feedback on this. Is it advisable or not?
SAP Version : 4.6C
Oracle : 10.2
OS - AIX UNIX
Thanks
Anupama

Hmm.. when I enter "TOO_MANY_EXTENTS" into the search box in the upper right corner of this forum I get back this:
SAP Note 435290 Description of BRCONNECT 6.10 DB check conditions
And in there I find:
"16. TOO_MANY_EXTENTS (formerly MANY_EXTENTS)
This condition checks whether there are tables or indices for which the number of allocated extents exceeds the specified threshold value. As a default, all tables and indexes are checked against the same threshold value. However, you can define different threshold values for individual segments or tablespaces by specifying their names in the OBJECT field of the DBCHECKORA table (transaction DB17).
Possible checking operands, threshold values, value units:
16a.     >, >=         <number>        P
More than <number> % of the maximum number of extents was already allocated.
16b.     >, >=         <number>        <none>
More than <number> extents were already allocated
16c.     <, <=        <number>        P
Fewer than <number> % of the maximum number of extents can still be allocated.
16b.     <, <=         <number>        <none>
Fewer than <number> extents can still be allocated.
Note: The check condition TOO_MANY_EXTENTS has only an informative role for locally managed tablespaces (LMTS), where the max extents attribute is set to UNLIMITED and the next extents size is determined automatically by Oracle. As a result, the number of extents is no longer a critical factor for LMTS."
Given that you've performed a proper notes search yourself before posting this question I really wonder, why you did not find this information...
So, to finally answer your question: just put the MAXEXTENTS value to UNLIMITED or reorganize the tables/indexes into a locally managed tablespace.
And please start reading the DBA documenation for SAP on Oracle!
regards,
Lars

Change max entents of DR$TEXT_INDEX$I table to UNLIMITED

I am using Oracle 11.2.0.2. I have a context index whose DR$TEXT_INDEX$I tables is giving ORA-01631: max # extents (200) reached in table DR$TEXT_INDEX$I .
What is the easiest way to change DR$TEXT_INDEX$I value to unlimited. The table is under dictionary base tablespace.
Thanks for you help.

I changed storage preference of the index and recreated the index.

Max # extents Error

When I execute this query in Oracle 8i Database.
SQL> create table MTL_MATERIAL_TRANSACTIONS_bak as select * from MTL_MATERIAL_TRANSACTIONS;
create table MTL_MATERIAL_TRANSACTIONS_bak as select * from MTL_MATERIAL_TRANSACTIONS
ERROR at line 1:
ORA-01630: max # extents (505) reached in temp segment in tablespace APPLSYSD
then Shall I use the following command Without shutting down the database. Is there any other solutions.
Please reply.
alter tablespace APPLSYSD default storage (maxextents unlimited);
OR
alter tablespace APPLSYSD storage (maxextents unlimited);

Hi user13098327,
Please read below thread;
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:956629961318

ORA-25150: ALTERING of extent parameters not permitted

hello all,
I am getting this error with my rman catalog db.
ORA-01653: unable to extend table RMAN.ROUT by 128 in tablespace USERS
USERS is locally managed , now how can i extend to unlimited as I can't with command
alter table rman.rout storage(maxextents unlimited)
I did increase size of tblsp but extents?
thx

Hi,
I request to search in forums, since you can find the solutions by your self with out any help.
Check the space from "dba_free_space" with respect to tablespace.
Add a New data file or Resize the data file
- Pavan Kumar N

ORA-01693-Max extents reached in lobsegment

Hi
getting this error in our alert log file
ORA-01693-Max extents <> reached in lobsegment <name>
Can any tell me how to increase (alter) logsegment
Thanks
Bhanu

alter table <table> modify lob (<lobcolumn>) (storage (maxextents unlimited))
will work

ORA-01631: max # extents (121) reached!!!

Please review the following DML and error in response of that command:
insert into dtcn (area_code, cons_code, dcdat) values(12,12,sysdate);
ERROR at line 1:
ORA-01631: max # extents (121) reached in table MNBSYS.DTCN
There are only two such tables DTCN and DTCN_HISTORY in which we are unable to insert any record because of above error. Following are some reference information of these tables:
PCT_FREE: 10, PCT_USED: 40 INITIAL_EXTENT: 5242880,
NEXT_EXTENT: 10240, MIN_EXTENTS: 1, MAX_EXTENTS: 121,
PCT_INCREASE: 0, FREELIST: 1, TABLESPACE_NAME: MNB_DATA,
DBUSERNAME: MNBSYS
It may also be noted that the above statistics are exactly same for number of tables but we are facing the problem with only these two tables. Kindly advise what could be the problem and how can I overcome this...
Thanks in anticipation...
Zia Shareef

Hi,
This error comes when table reach to his max extents,here table extend upto 121 extents that is his max value so now you have to increase the value of maxextents.
by
SQL> alter table <table_name> storage(maxextents unlimited);
**also set the value of nextextent parameter because currently its define by very low value of 10240
Kuljeet

System maximum max extents....

Hi,
I need a clarification about the System maximum max extents...
The oracle doc "Error messages" about The error code and message "ORA-01631: max # extents (string) reached in table string.string" points out as action:
"If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params"
Which is the system maximum max. extents...??? Is this of database block size???
Thanks you,
Sim

sgalaxy wrote:
Hi,
I need a clarification about the System maximum max extents...
The oracle doc "Error messages" about The error code and message "ORA-01631: max # extents (string) reached in table string.string" points out as action:
"If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params"
Which version of Oracle are you on ? I don't think maxextents has been a problem since 9i.
In the days when "unlimited extents" had not been introduced and the entire extent map had to fit in the segment header the size of a segment map entry dictated the number of extents that could be listed, so the block size made a big difference. The maximum roughly doubled as you doubled the size of the block. From memory - 2KB blocks gave 121 extents, 4KB gave 248, 8KB gave 505 and 16KB gave 1016 - I don't have any memory of a figure for 32KB blocks.
But from 9i (at least 9.2) Oracle ignores any maxextents setting you put into the table storage clause and uses "unlimited".
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
"For every expert there is an equal and opposite expert"
Arthur C. Clarke

ORA-01630: max # extents (2) reached in temp segment in tablespace USERS

Hi all,
I got the error when I created CLUSTER
ORA-01630: max # extents (2) reached in temp segment in tablespace USERS
CREATE CLUSTER trial_cluster (trialno NUMBER(5,0))
PCTUSED 80
PCTFREE 5
TABLESPACE users
STORAGE (INITIAL 250K NEXT 50K
MINEXTENTS 1 MAXEXTENTS 2
PCTINCREASE 0)
HASH IS trialno HASHKEYS 150;
And I increased maxextents to 20480
alter tablespace users default storage(MAXEXTENTS 20480)
same error happens.

Here is one example from Metalink note:
create tablespace dropme datafile 'dropme.dbf' size 200m
extent management dictionary
default storage (initial 100k next 100k maxextents unlimited pctincrease 0);
SQL> create index myind on mytab (object_name)
2 storage ( initial 16k next 16k maxextents 3 pctincrease 0)
3 tablespace dropme;
ERROR at line 1:
ORA-01630: max # extents (3) reached in temp segment in tablespace DROPME

MAX EXTENTS have reached

Hi Team,
We are getting ora-1632, max extents error's.. suggest ---what all can be done..
and in future how to avoid it...

Seems your index extent has reached its max limit, try and see if the issue resolves and always post full error instead of just error no.
ALTER INDEX <object_owner>.<index_name> STORAGE ( MAXEXTENTS UNLIMITED);
Edited by: Veeresh.S on Oct 22, 2012 6:53 PM

UNLIMITED TABLESPACE vs MAXEXTENTS...

Hi,
Let's assume that :
1)a db user has been granted the UNLIMITED TABLESPACE privilege....
2)all tables's extents he created have been full ....
3)the tables's maximum number of extents has been reached....
4)there is almost no other free tablespace empty..... so , it must be resized....
when a/some records in one table are going to be inserted.... what may happen....????
1) because of the maxextents number has been reached... so as there is no possibility another extent(s) to be added..., the records will not be inserted....????
2) because of the UNLIMITED TABLESPACE... the tablespace would be resized and as a result the records... will be inserted....????
In other words....which one is prevailing....
the UNLIMITED TABLESPACE.... or MAXEXTENTS .....????
Thanks... a lot
Sim

unlimited tablespace privilege means tablespace quotas do not apply and you can create objects in any tablespace, including SYSTEM.
Consequently, granting UNLIMITED TABLESPACE should be avoided, as it allows the grantee to create havoc in your database.
Setting maxextents is a thing of the past. Usually maxextents is unlimited.
You forgot however: datafiles have limits too
As to your questions:
If you did set quota for the owner of the table and the quota is used up, the statement will fail.
However, usually one sets quota unlimited on the tablespace(s) the owner has access to, and one sets the tables maxextents to unlimited.
In that case the statement will fail when the datafile and/or the disk is full.
Final note: as altering quotas is quite easy, you could have experimented, and one proper answer would have been 'did you try?'
Hth
Sybrand Bakker
Senior Oracle DBA

Db02 shown autoextend unlimited

hi
While import client in QAS server, it has given an error NO SPACE in PSAP <SID > table.So i added 20GB datafile with auto extend.Now its showing 'unlimited' in autoextend
Tablespace                       Size (kb)      Free (kb)      Used (%)   Tab/ind    Extents    AutoExt (kb)
PSAPP3Q                          114,155,520      2,979,456         97     76,339    141,821    Unlimited
When i import the request again system hangs.........
Regards,
Sam

Hi ,
   Before going ahead did you check following points.
1.Support pack level of both PRD & QUA system.These both must be equivalent.This means that repository in both the environment should be on same level.
2.While doing client export this will create three request something like KT,KX, KO .Have you followed the sequence of these while importing into QUA.
3.The most important is have you run update staistics before starting client copy.
   You can check the logs at OS level in folder /usr/sap/trans/tmp if there is some entries written that means your client copy still running & if there is no entry written in tmp folder from very long time then its suggested to stop transport then run update staistics & then you carry on with client impot.
Hope this will solve your issue.
Thanks..
Mohit

Extent unlimited

Similar Messages

Maybe you are looking for