ORA-1631: max # extents 505 reached in table APPLSYS.WF_NOTIFICATION_IN

Platform: RHEL 4u5
Application: 11.5.10.2
Database: 10.2.0.4
2-node Installation as follows:
1 Node for DB and Concurrent
1 Node for Apps.
We anabled OWF Mailer services on 2nd Sept, and on 5th Sep we started receiving following error messages in our DB alert log contnuously:
ORA-1631: max # extents 505 reached in table APPLSYS.WF_NOTIFICATION_IN
So, we stopped the OWF Mailer servcies and Agent Listeners.
Got a metalink note 152475.1 but confused to alter the table definition as I am of the view that these Oracle Workflow related tables are Oracle Built-in Objects not the custom one.
So, will it be ok to increase the Maxextents for this table?

911748 wrote:
Hi Asif,
We have actually implemented it on Production now. We just tested the mailer configuration on TEST and when users give go ahead after they tested their scenarios we implemented the same on Production. Can I implement the extents increment activity on production?
Yes you can.
Thanks,
Hussein

Similar Messages

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

I have a problem, in creating a index with error ORA-01630: max # extents (505) reached in temp segment in tablespace.
can you any please help me on this , what could be the best steps can be taken to fix the issue.
I increased the TBS size (I have more than 6 Gb free space), verified the max extents and min extents but didn't get clear idea.
SQL> show user
USER is "APPS"
SQL> create index xyz.xygts_mtl_trx_source_idx on mtl_material_transactions(trx_source_line_id);
create index xyz.xygts_mtl_trx_source_idx on mtl_material_transactions(trx_source_line_id)
ERROR at line 1:
ORA-01630: max # extents (505) reached in temp segment in tablespace
XY_DATA
SQL> select BYTES/1024/1024 from dba_segments where SEGMENT_NAME='MTL_MATERIAL_TRANSACTIONS';
BYTES/1024/1024
10510
-- Verified the pctincrease value
SQL> select TABLESPACE_NAME,INITIAL_EXTENT,NEXT_EXTENT,MAX_EXTENTS,PCT_INCREASE from dba_tablespaces where TABLESPACE_NAME='XYZ_DATA';
TABLESPACE_NAME INITIAL_EXTENT NEXT_EXTENT MAX_EXTENTS
PCT_INCREASE
XYZ_DATA 40960 40960 505
0
Thanks,
Venkat

Pl see
How to Diagnose and Resolve ORA-1628, ORA-1630, ORA-1631, ORA-1632, ORA-1684 : max # of extents <num> reached in < OBJECT > [ID 1025581.6]
Overview Of ORA-01630 Max # Extents(%) reached in temp segment in tablespace % [ID 260944.1]
HTH
Srini

ORA-1631: max # extents 4096

Hi
I received below ORA error for one of my prod table, would like to in which scenario we get the below error and how to investigate why it has occured.
ORA-1631: max # extents 4096 reached in table.......
Regards

And what does this database error have in common with Oracle Object and Object Relational concepts, that are the subject matter of this forum?
Please select the appropriate forum to ask your questions - in this, find the Oracle Database > Database - General forum - and close your thread here.

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

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

ORA-1631: max # extents reached in table INFILES

Dear friends
kindly give me the answer weather I am correct/wrong?
Solution i have given is
Alter table <tablename>
storage(maxextents unlimited)
Srinivas

Before changing the table to allow an unlimited number of extents I would 1- verify that the table size is in line with its design usage and 2- that the program in question is not doing something stupid. If both of these are OK, and most of the time they will not be the problem, then you might also consider resizing the object since dictionary space management is in use.
HTH -- Mark D Powell --

ORA-01631: max # extents (4096)

Hi
I received below ORA error for one of my prod table, would like to in which scenario we get the below error and how to investigate why it has occured.
ORA-01631: max # extents (4096) reached in table DWHSE.F_APS_ORDERS
Regards

To hit a maximum extents error on a table you pretty much have to be using dictionary tablespace management. The maximum number of extents defaults based on the block size. If your Oracle version is 8.1 and up all your tablespaces should have been rebuilt as locally managed tablespaces using either auto-allocate or uniform extents. In the case where you have a newer version you should consider creating new tablespaces and moving the objects into them so you can take advantage of modern extent management features.
If you are running an older release then just take some time to review your object allocation layout to see if for space managment purposes you need to do any re-arranging or storage parameter modification. We used our own version of auto-allocate under 7.x where we had 4 different extent sizes for smaller objects where each size was an even multiple of the smaller sizes. For moderate size and large tables we had uniform extent sizes.
Good luck.
HTH -- Mark D Powell --

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

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

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

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

Max # extents exceeded

Hi,
I am having problems with the max # extents being exceeded.
I am creating a spatial index using the following script:
CREATE INDEX GIS.MYTABLE_SX ON
GIS.MYTABLE(GEOMETRY)
indextype is MDSYS.SPATIAL_INDEX
parameters ( 'SDO_LEVEL=6,
     SDO_NUMTILES = 8,
     SDO_COMMIT_INTERVAL = 1000,
     TABLESPACE = GISI,
     INITIAL = 131072,
     NEXT = 131072,
     PCTINCREASE = 0,
     MINEXTENTS = 1,
     MAXEXTENTS = 2147483645,
     BTREE_INITIAL = 512K,
     BTREE_NEXT = 512K,
     BTREE_PCTINCREASE = 0')
This in turn creates the table
MYTABLE_SX_HL6N8$
and
the indexes
MYTABLE_SX_HL6N8$_B1
(x4 - one for each field SDO_GROUPCODE, SDO_CODE, SDO_STATUS, SDO_ROWID)
and
MYTABLE_SX_HL6N8$_B2
(x1 one for SDO_ROWID)
using the following script:
DROP TABLE MYTABLE_SX_HL6N8$ CASCADE CONSTRAINTS ;
CREATE TABLE MYTABLE_SX_HL6N8$ (
SDO_GROUPCODE RAW (14),
SDO_ROWID ROWID,
SDO_CODE RAW (14),
SDO_STATUS VARCHAR2 (1))
TABLESPACE GISI
PCTFREE 10
PCTUSED 40
INITRANS 1
MAXTRANS 255
STORAGE (
INITIAL 131072
NEXT 131072
PCTINCREASE 0
MINEXTENTS 1
MAXEXTENTS 2147483645
FREELISTS 1 FREELIST GROUPS 1 )
NOCACHE;
CREATE INDEX MYTABLE_SX_HL6N8$_B1 ON
"GIS".MYTABLE_SX_HL6N8$(SDO_GROUPCODE, SDO_CODE, SDO_ROWID, SDO_STATUS)
TABLESPACE GISI PCTFREE 10 STORAGE(INITIAL 524288 NEXT 524288 PCTINCREASE 0 )
CREATE INDEX MYTABLE_SX_HL6N8$_B2 ON
"GIS".MYTABLE_SX_HL6N8$(SDO_ROWID)
TABLESPACE GISI PCTFREE 10 STORAGE(INITIAL 524288 NEXT 524288 PCTINCREASE 0 )
The problem is when you create a spatial index using the top script the max # extents do not get applied to
MYTABLE_SX_HL6N8$_B1
and
MYTABLE_SX_HL6N8$_B2
Instead these tables take on the default max # extents set on the tablespace.
How do I set the max # extents for indexes
MYTABLE_SX_HL6N8$_B1
and
MYTABLE_SX_HL6N8$_B2
to MAXEXTENTS 2147483645 for example. I am aware that this is not good practice but I would like to know if it is possible. Is it a spatial issue? I have tried to increase the size of
the BTREE_INITIAL and BTREE_NEXT to 512K from 128K but it still complains about max # extents (999) reached. A way round it is obviously to increase the default max # extents on the tablespace but that requires DBA intervention. I would like to know how one can do this programatically using the top script or something similar.
Thanks
Regards
Stephen

Hi Stephen,
A few thoughts:
Oracle has pretty much dropped hybrid indexing in terms of it being
a generically useful way to index data. As of 9.0.1.2 the suggestion
is to use R-tree indexes unless there is something about your
workload or data set that makes the use of R-trees bad.
If you don't use R-tree indexing, then stick with fixed indexing. The
original idea of hybrid indexing was to allow better approximations
of geometries without the index growing too large, but it turns out the
SQL index query within spatial took longer than anticipated.
In terms of setting up the spatial index, when creating a quadtree index
you can specify the btree_initial and btree_next in the parameters clause
of the create index statement, which allows you to adjust the btree indexing
parameters as you noted, but there is no way to set the max number of
extents (or in fact the tablespace used for the b-tree indexes).
When you need that control, you need to to have dba intervention to set the
default tablespace and parameters at the user level before creating the spatial
index. The parameters in the parameters clause can set up the index table
parameters, and the default parameters can be used for the btree indexes.
regards,
dan

Max number of dataspaces in table space

I am getting the error ORA-1686 max # files(1023)reached for tablespace SAPPR1 when trying to create a new dataspace.
The tablespace has 1023 2GB dataspaces in it. What is my best option for this tablespace?
Message was edited by:
user582335

Hmm...well, there are several options, with varying degrees of complexity and difficulty.
First, each file is 2GB. Though that was a common limit for datafile size in years gone by, any reasonably up-to-date O/S should be able to handle files of much larger sizes. So, you could begin by growing the size of the existing datafiles.
Second, you could move some objects out of that tablespace, freeing up some space there.
Third, you could move all the objects out, drop the tablespace, and re-create it with datafiles larger than 2GB.
Finally, if you're on 10g, and you're planning to rebuild the tablespace, you may want to investigate bigfile tablespaces.
-Mark

MAX EXTENTS for a table

Hello Guru's
I am working on oracle express 10 G on windows , This is my test machine. I am a beginner to oracle Dba activities,
Problem:
I want to restrict the size of a table (say max upto 400k)
My Approach:
1. I create a Tablepsace with uniform extent size (40K each)
2. I created a table in this tablespace with max extents 10 ( so that 40K * 10 = 400K)
SCOTT@xe>CREATE TABLESPACE TB
2   DATAFILE 'F:\Oracle\oradata\XE\TB.DBF' SIZE 100M
3   EXTENT MANAGEMENT LOCAL
4   UNIFORM SIZE 40K
5   ONLINE ;
Tablespace created.
SCOTT@xe>
SCOTT@xe>DROP USER G CASCADE ;
User dropped.
SCOTT@xe>CREATE USER G IDENTIFIED BY G DEFAULT TABLESPACE TB ;
User created.
SCOTT@xe>ALTER USER G QUOTA UNLIMITED ON TB;
User altered.
SCOTT@xe>GRANT CREATE SESSION , CREATE TABLE TO G;
Grant succeeded.
SCOTT@xe>CONNECT G/G@xe
Connected.
G@xe>CREATE TABLE t ( A number) TABLESPACE TB storage (minextents 1 maxextents 10);
Table created.
G@xe>SELECT SEGMENT_NAME, MIN_EXTENTS, MAX_EXTENTS , SEGMENT_TYPE, TABLESPACE_NAME, BLOCKS
2 FROM USER_SEGMENTS ;
SEGMENT_NAME                                                                      MIN_EXTENTS MAX_EXTENTS SEGMENT_TYPE       TABLESPACE_NAME                    BLOCKS
T                                                                                           1 2147483645 TABLE              TB                                      5
G@xe>Issue is:
I want the maximun extents that could be llocated to this table must be 10 , BUT from user_segments I could see MAX_EXTENTS = 2147483645 (default value).
When i pump data into this table MAX_EXTENTS exceeds 10 (i.e user Defined value)
I have no idea why this is the case;
Regards,

When creating a segment (Table/Index) in a Locally Managed Tablespace (created with "EXTENT MANAGEMENT LOCAL" and visible in DBA_TABLESPACES under EXTENT_MANAGEMENT), Oracle ignores the specification of MAXEXTENTS.
All segments in an LMT would default to MAXEXTENTS UNLIMITED (which really means 2 billion).
(DEFAULT STORAGE at the Tablespace level cannot be set if it is LOCAL AUTOALLOCATE or LOCAL UNIFORM)
See [The 10gR2 documentation on the STORAGE clause|http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/clauses009.htm#i997450]
In your 10gXE install you will not be able to create a DICTIONARY MANAGED Tablespace as the SYSTEM Tablespace itself is LOCALLY MANAGED.
If you want to limit the size of a table you could
a. Create a Tablespace with a set size for datafiles (ie, set AUTOEXTEND OFF for the datafiles)
b. Create the Table in that Tablespace
Edited by: Hemant K Chitale on Aug 18, 2009 3:31 PM

ORA-02070: Error when updating an informix table through orcl view using HS

Hello!
I faced the following problem:
I have a table in informix, and i want to reach this table through Oracle infromix gateway (Heterogenous Services). I succeeded to set up the gateway, and I created an Oracle view for my table in informix. It is working fine, I can query and modify data, except the following case: If I run the query (from SQL Developer) "UPDATE oracle_view SET float_field = '1.1' WHERE record_id = 1 AND float_field = '1.2'", I receive the following error:
"SQL Error: ORA-02070: database database_link does not support TO_NUMBER in this context.
*Cause: The remote database does not support the named capability in the context in which it is used.
*Action: Simplify the SQL statement."
If I modify the query as "UPDATE oracle_view SET float_field = '1.1' WHERE record_id = 1", it is running without any error messages. I found, that to_number is not supported by Oracle HS gateway, but I do not use explicitly the to_number Oracle function! But I must use the above version, because of concurrent users.
Does anybody have an idea how I could get rid of the implicit call of to_number?
Thanks, Gyula

user11229789 wrote:
Yes, float_field is a numeric-type field, which is a 8-byte FLOAT in informix. This field gets automatically FLOAT datatype in the Oracle view, and can not be modified. record_id is some integer unique id field.Well, as the float_field is numeric it makes sense that the SQL issued from Oracle treats it as numeric, so leaving out the quotes can only be the correct thing to do. If you introduce quotes then you are providing strings and the HS is having to do a convertion to numeric (hence where the TO_NUMBER would have been coming into the initial issue.
If I try the update query without '-s you suggested, like this: "UPDATE oracle_view SET float_field = 1.1 WHERE record_id = 1 AND float_field = 1.2" , i receive the following error message:
SQL Error: ORA-28534: "Heterogeneous Services preprocessing error"
*Cause: One of the things that the Heterogeneous Services can do is
to preprocess parts of SQL statements that contain implicit
coercions or calls to explicit coercion functions like TO_CHAR
TO_NUMBER or TO_DATE. For example, it could convert a call to
TO_DATE to a bind variable, pre-evaluate the TO_DATE function
call and pass the resulting value to the non-Oracle system as
the bind value. This behavior is controlled by some coercion
related capabilities. If the capabilities are set incorrectly,
the HS could encounter errors when it attempts to do the
preprocessing. If it does then this error will be signaled.
*Action: The capability table settings are controlled by the agent
vendor and can be modified by the DBA. Contact your DBA and
agent vendor and get the correct set of capabilities installed.I can't see why the HS would be trying to do any coercion of anything except to perhaps convert the parts of the where clause to bind variables and pass the actual values in. Does it work ok without the "AND float_field = 1.2" ? If so, I'm guessing there's some configuration issue of the HS required to get it to deal with the floats.... perhaps in the capability settings as the error message "action" indicates.

ORA-1631: max # extents 505 reached in table APPLSYS.WF_NOTIFICATION_IN

Similar Messages

Maybe you are looking for