Ora-1000 max openCursor exceeded

Hi,
i have a question about the ora-1000.
My prog is a "C"-coded Programm. Which is connected to the
database. After few days the Ora-message ora-1000 will be shown
in the tracefile.
The Parameter Max open Cursor is meanwhile set 1000.
Knows anyone the Problem with 8.1.7 DB.
We have also the online-backup and the Journaling set on.
I tried to generate the same fault with a test prog but it was
not possible with test- Tables. I had the same effect only with
the Production Tables.
bestv regards

Make sure that u close all the cursors that u open in the
program. Most of the time that is the biggest culprit.
Ketan.

Similar Messages

ORA-01000 max cursors exceeded

After what I thought was fixing the problem, we are yet again hitting ORA-01000.
We have an application which was left running over Christmas and New Year but with no one using it.
We came back and the first time someone tried to do something we hit the ORA-01000 error.
Has anyone seen anything like this before?
I'm not ruling out a problem in our code somewhere but it seems odd that when the application is actually being used we have no problems but if we leave it to sit for a while it suddenly runs out of cursors!
Cheers
Alex

what is the application doing? Is any other application accessing the database? Are you using statement caching?

Max cursors exceeds problem(ORA-01000)

Hi
In my server open_cursors is set as 300 .We are developing a java application(using struts & Jboss web server) nearly 10 computers access the oracle 10g server through plsql procedures/functions ,frequently I am getting ORA-01000 -MAX CURSOR EXCEEDS errors,what should I do .please.....
by
s_bala

That means there is two cursor related parameters
                                        |
                                        |
                                        |
                                        |
                    |                                        |
1)Cached cursors                              2)Currently open cursor
1)Cached cursors     2)Currently open cursor
SQL> select o.sid,osuser,machine,count(*) num_curs
from v$open_cursor o,v$session s
WHERE user_name = 'ERP' and
o.sid = s.sid GROUP BY o.sid,osuser,machine
ORDER BY num_curs DESC;     SQL>select max(a.value) as highest_open_cur,
     p.value as max_open_cur
     from v$sesstat a, v$statname b, v$parameter p
     where a.statistic# = b.statistic#
     and b.name = 'opened cursors current'
     and p.name= 'open_cursors'group by p.value;
THIS IS THE RESULT I GOT
SID OSUSER MACHINE NUM_CURS
106 x 18
93 x 14
124 x 14
152 x 13
90 y y 11
121 z 8
132 a 8
118 b b 6
105 c 5
131 b 5
98 d d 4
95 x 3
147 y y 3
89 e 2
119 e 2     THIS IS THE RESULT I GOT
HIGHEST_OPEN_CUR MAX_OPEN_CUR
83 500
     -This is related to ORA-01000 -MAX CURSOR EXCEEDS
From the above what I understood is correct ???
F) How to clear 1)Cached cursors ? (or) how to reduce NUM_CURS (from the above left side table ).
G) will the 1)Cached cursors give any problems to our database.

Ora-0059: max no.of db_files exceeded

hi.
my db is in archivelog mode(24x7).
i tried to add data file to my tablespace
i got the following error
ora-oo59: max no of db_files exceeded.
plz tel me step by step how to change the db_files parameter
in what state
when i have to take backup of control file
then again how i have to open the database.
my current db_files value is 400 .
i need atleast 600.
thanks and regards
suresh

DB_FILES is a static parameter, and cannot be change online. Restarting the db is required.<br>
alter system set db_files=600 scope=spfile;
shutdown immediate
startup<br>
<br>
Nicolas.

ORA-22290: operation would exceed the maximum number of opened files or LOB

i am getting this error in a procedure.
ORA-22290: operation would exceed the maximum number of opened files or LOBs
22290, 00000, "operation would exceed the maximum number of opened files or LOBs"
// *Cause: The number of open files or LOBs has reached the maximum limit.
// *Action: Close some of the opened files or LOBs and retry the operation.
NAME TYPE VALUE
session_max_open_files integer 10
Procuedure:
CREATE OR REPLACE PROCEDURE WMSOWN."PROC_WMS_XML_READ"
P_EVENT_KEY IN VARCHAR2,
X_STATUS_MSG OUT VARCHAR2,
X_STATUS OUT NUMBER
)AS
l_parser dbms_xmlparser.Parser;
domdoc xmldom.DOMDocument;
nodelist XMLDOM.DOMNODELIST;
node XMLDOM.DOMNODE;
n_child XMLDOM.DOMNODE;
elements XMLDOM.DOMELEMENT;
name_node_map XMLDOM.DOMNAMEDNODEMAP;
parent_seg varchar2(4000);
tag_name_bkp varchar2(4000); -- LOOK OUT BRAD IS CODING AGAIN
chile_seg VARCHAR2(4000);
p_seg VARCHAR2(4000);
p_seg1 VARCHAR2(4000);
p_seg2 VARCHAR2(30);
p_int_name VARCHAR2(50);
col_value VARCHAR2(100):=NULL;
len1 NUMBER;
cnt NUMBER;
seg_id_bkp NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
sequence_bkp NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
prev_sequence NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
prev_seq_set VARCHAR2(3); --brad coding
parent_id number; ---brad coding
valid_seg NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
data_status VARCHAR2(10);
v_main_seg VARCHAR2(50);
v_seq_no NUMBER;
V_CLOBLOCATOR CLOB;
V_FILELOCATOR BFILE;
v_amount_to_load NUMBER;
dest_offset NUMBER := 1;
src_offset NUMBER := 1;
lang_context NUMBER := DBMS_LOB.DEFAULT_LANG_CTX;
warning NUMBER;
v_event_name USR_OUB_FILE_PROCESS_DETAILS.EVENT_NAME%TYPE;
v_file_name USR_OUB_FILE_PROCESS_DETAILS.FILE_NAME%TYPE;
DIRECTORY_PATH_INVALID EXCEPTION;
PRAGMA EXCEPTION_INIT(DIRECTORY_PATH_INVALID,-22285);
NO_PRIVILEGES EXCEPTION;
PRAGMA EXCEPTION_INIT(NO_PRIVILEGES,-22286);
INVALID_DIRECTORY EXCEPTION;
PRAGMA EXCEPTION_INIT(INVALID_DIRECTORY,-22287);
FILE_NOT_FOUND EXCEPTION;
PRAGMA EXCEPTION_INIT(FILE_NOT_FOUND,-22289);
P_DIRECTORY VARCHAR2(50) :='WMS_XML_DIR_OUB';
v_whid poldat_view.wh_id%type;
BEGIN
--NAME : PROC_WMS_XML_READ.PLS
--DESCRIPTION :
-- Procedure PROC_WMS_XML_READ search XML files from remote location.
-- Open,Parse and Read XML files. Store all XML values into tables.
-- Developed by Dharmesh Patidar(jw782)
-- History: New condition is added i.e. p_seg:=parent_seg to maintain PARENT and CHILD relationship
-- by Vishwanath Dubey(jl246) on 17-June-2011
-- BRAD_XML_DEBUG table removed for CLEANING Activity by DHARMESH PATIDAR(JW782) ON 29-JUNE-2011.
/*BLOCK FOR CAPTURING EVENT NAME BASED ON EVENT ID START*/
BEGIN
SELECT event_name,file_name,WAREHOUSE_ID
INTO v_event_name, v_file_name,v_whid
FROM usr_oub_file_process_details
WHERE event_id=p_event_key
AND process_flag='U';
EXCEPTION
WHEN NO_DATA_FOUND THEN
x_status_msg:=SQLCODE||':'||' Error while selecting event name and event id in Procedure PROC_WMS_XML_READ : Record is not available in USR_OUB_FILE_PROCESS_DETAILS table for event id '|| P_EVENT_KEY;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN TOO_MANY_ROWS THEN
x_status_msg:=SQLCODE||':'||' Error while selecting event name and event id in Procedure PROC_WMS_XML_READ : More than one Records found in USR_OUB_FILE_PROCESS_DETAILS table for event id '|| P_EVENT_KEY;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN VALUE_ERROR THEN
x_status_msg:=SQLCODE||':'||' Error while selecting event name and event id in Procedure PROC_WMS_XML_READ : Varibale length is small or data type mismatch while selecting event id and event name in USR_OUB_FILE_PROCESS_DETAILS table for event id '|| P_EVENT_KEY;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN OTHERS THEN
x_status_msg:=SQLCODE||':'||'Error in Procedure PROC_WMS_XML_READ while selecting event name and event id ';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END;
/*BLOCK FOR CAPTURING EVENT NAME BASED ON EVENT ID END*/
/*LOGIC TO READ XML FROM REMOTE LOCATION START*/
DBMS_LOB.CREATETEMPORARY(V_CLOBLOCATOR, TRUE);
V_FILELOCATOR := BFILENAME(P_DIRECTORY,V_FILE_NAME);
DBMS_LOB.OPEN(V_FILELOCATOR,DBMS_LOB.FILE_READONLY);
V_AMOUNT_TO_LOAD := DBMS_LOB.GETLENGTH(V_FILELOCATOR);
DBMS_LOB.LOADCLOBFROMFILE(V_CLOBLOCATOR,
V_FILELOCATOR ,
V_AMOUNT_TO_LOAD,
DEST_OFFSET,
SRC_OFFSET,
0,
LANG_CONTEXT,
WARNING);
dbms_lob.close(V_FILELOCATOR);
/*LOGIC TO READ XML FROM REMOTE LOCATION END*/
/*Temporary Code to help with debug Clear the table before populating it with new data*/
--delete table BRAD_XML_DEBUG;
cnt:=1;
seg_id_bkp:=0;
data_status:='N';
v_seq_no:=0;
prev_seq_set:='NO';
/*create new parser.*/
l_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(l_parser, replace(V_CLOBLOCATOR,'&','1x2x3x4x5'));
/*Parse the document and create a new DOM document.*/
domdoc :=dbms_xmlparser.getDocument(l_parser);
/* get all elements in the DOM*/
nodelist := XMLDOM.getElementsByTagName(DOMDoc, '*');
len1 := XMLDOM.getLength(nodelist);
/* loop through elements of the DOM */
FOR j in 1..len1-1 LOOP --MAIN LOOP START
BEGIN
/*below sql will fetch Node from table to travel xml data*/
BEGIN
SELECT int_name,tag_name
INTO p_int_name, p_seg1
FROM usr_wms_tag_det
WHERE int_name=v_event_name
AND seq_no =cnt;
EXCEPTION
--PLEASE DO NOT HANDLE ANY EXCEPTION APART MENTIONED BELOW
WHEN OTHERS THEN
NULL;
END;
IF cnt=1 THEN
v_main_seg:=p_seg1;
END IF;
EXCEPTION
--PLEASE DO NOT HANDLE ANY EXCEPTION APART MENTIONED BELOW
WHEN no_data_found THEN
null;
WHEN OTHERS THEN
x_status_msg:=SQLCODE||':'||'Error in Procedure PROC_WMS_XML_READ while selecting interface name and tag name'||sqlerrm;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END;
/*LOGICS TO READ XML START*/
node:=XMLDOM.item(nodelist, j);
elements:=XMLDOM.makeElement(node);
parent_seg:=(xmldom.getTagName(elements));
tag_name_bkp:=(xmldom.getTagName(elements));
name_node_map:=xmldom.getAttributes(node);
n_child:=xmldom.getFirstChild(node);
col_value:=xmldom.getNodeValue(n_child);
/*get the sequence number from the interface hierarchy table */
SELECT count(1)
INTO valid_seg
FROM usr_wms_tag_det
WHERE int_name=v_event_name
AND tag_name = tag_name_bkp;
if valid_seg>0 then
begin
SELECT seq_no
INTO sequence_bkp
FROM usr_wms_tag_det
WHERE int_name=v_event_name
AND tag_name = tag_name_bkp;
seg_id_bkp:=seg_id_bkp+1;
p_seg:=parent_seg;--Modified by Vishwanath Dubey dated 16-jun-2011
end;
end if;
if prev_seq_set = 'NO' then
begin
prev_sequence := sequence_bkp;
prev_seq_set := 'YES';
end;
end if;
if sequence_bkp < prev_sequence then --you just moved up level(s) in the message structure
begin
select max(seg_id)
into parent_id
from usr_wms_global_xml_det
where seg_sequence = sequence_bkp-1;
prev_sequence := sequence_bkp;
end;
end if;
if sequence_bkp > prev_sequence then --you just moved down a level in the message structure
parent_id := seg_id_bkp-1;
prev_sequence := sequence_bkp;
end if;
/*end getting the hierarchy table sequence */
/*LOGICS TO READ XML END */
IF (parent_seg =p_seg1) or (parent_seg=p_seg2) THEN
if parent_seg=v_main_seg then
v_seq_no:=v_seq_no+1;
end if;
BEGIN
/* INSERTING DATA LOGICS TO READ XML END */
INSERT INTO usr_wms_global_xml_det values(p_int_name,tag_name_bkp,parent_seg,seg_id_bkp,sequence_bkp,parent_id,'','','',J,v_seq_no,data_status,cnt);
EXCEPTION
WHEN OTHERS THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ while inserting records in USR_WMS_GLOBAL_XML_DET table for interface name and parent segment '||P_INT_NAME||','||PARENT_SEG;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END ;
p_seg:=parent_seg;
p_seg2:=P_SEG1;
cnt:=cnt+1;
ELSE
chile_seg:=parent_seg;
BEGIN
/* INSERTING DATA LOGICS TO READ XML END */
INSERT INTO usr_wms_global_xml_det values(p_int_name,tag_name_bkp,p_seg,seg_id_bkp,sequence_bkp,parent_id,'',chile_seg,replace(TRIM(Col_Value),'1x2x3x4x5','&'),J,v_seq_no,data_status,cnt);
EXCEPTION
WHEN OTHERS THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ while inserting records in USR_WMS_GLOBAL_XML_DET table for interface name and parent segment '||P_INT_NAME||','||PARENT_SEG;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END;
END IF;
END LOOP; --MAIN LOOP END
dbms_xmldom.freeDocument(DOMDoc);
x_status:=0;
EXCEPTION
WHEN DIRECTORY_PATH_INVALID THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ DIRECTORY PATH IS INVALID';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN FILE_NOT_FOUND THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ INVALID XML FILE NAME OR FILE DOES NOT EXISTS';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN NO_PRIVILEGES THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ Insufficient privileges on file or directory NAME- '||p_directory||' to perform FILEOPEN operation.';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN OTHERS THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ '|| SQLERRM;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
dbms_xmlparser.freeParser(l_parser);
dbms_xmldom.freeDocument(DOMDoc);
RETURN;
END PROC_WMS_XML_READ;
Edited by: user13427480 on Feb 8, 2013 7:08 PM

when you post sql statement use also similar threads :
ORA-22290: operation would exceed the maximum number of opened files or LOB
https://kr.forums.oracle.com/forums/thread.jspa?messageID=10842417

Using PreparedStatement and the Oracle Error ORA-1000

Hi,
I have a question about PreparedStatement objects that is not so simple to explain for me. What I would like to know is: if I use a PreparedStatement following traditional and generic steps:
1- PreparedStatement pStmt = Connection.prepareStatement(sQuery);
2- pStmt.setXXX(i,j);
n - pStmt.setXXX(i,j);
n+1 - ResultSet rs = pStmt.executeQuery();
n+2 - while(rs.next()){ ... retrive ResultSet data ... }
n+3 - rs.close()
n+4 - back to point number 2
and at the end (as you can see in the point numbered n+4), instead of closing the PreparedStatement pStmt using the close() method, I reuse the PreparedStatement pStmt comeing back to the point numebr 2 and setting again all its parameters with new values ... then ... what heppens in the Oracle database ? Has been the cursor (so the mamory area), associated to my PreparedStatement object pStmt, duplicated or is it the same ?
I know that Java allows you to do this kind of operations with PreparedStatement, and I know that in tha Java Documentation is explained to follow this strategy to optimize the execution time because in this way the same PreparedStatement is precompiled and prepared only once. But if I do a for loop following the steps explained before, after many iterations I have the error "ORA-1000: maximum open cursors exceeded". This error is the reason of my question. Does this error means that it's mandatory to close a PreparedStatement always, otherwise if you reuse it without closing it then the corresponding database cursor will be duplicated ? If it is so, then I think this is a contradiction with official java documentation ...
I'm using Oracle8i (version 8.1.7) and Oracle JDBC Thin Driver (Windows NT) for use with JDK 1.2.x. Moreover, in my database istance the parameter "maximum open cursor" is equal to 800 ...
Thank you very much for suggestions :-)

There is no need to close a prepared statement or its resultset for every iteration.
After the first iteration in a loop, all subsequent executions of it will close the previous resultset. By adding close() method, you are making one extra costly call to the DB for no reason.
Following is the sample code.I know what you are saying. In fact at the beginning I wrote my code in the same way of your sample (see the code of my first post at the begin of this page).
But doing so, after thousand iterations of the loop, I had "Oracle Error ORA-1000 : maximun open cursor exeeded" even if in my database istance the parameter "maximum open cursor" is equal to 8000.
At this moment in my code, for each iteration, I close the PreparedStatement and in this way I don't have anymore the error :-((
So it seems that only in theory we can reuse a preparedStatement without closing it. In fact if we see the oracle system table "$open_cursor" (as Konrad Pietzka suggest me) we can find that, for each interation,
at our line code "rs = pstmt.executeQuery();" correspond a new cursor in the database: this means that for each method "pstmt.executeQuery()" the database open a new cursor and do not use the previous one as it should.
I posted a question two months ago to search if someone had the same problem (it seems that Konrad Pietzka had the same situation) and was able to explain me what is the cause.
The only reason I found by myself for this problem, is that probably the Oracle JDBC Thin Driver for Windows NT/2000 has some bugs... but I'm not sure ...
Thank you very much for you time !!
bye :-))
Fidalma

ORA-22813: operand value exceeds system limits

hi all,
ORA-22813: operand value exceeds system limits
the above error occurs while calling a function. in 10g its working fine. after moving it to 11g v r facing the error. Plz help

KRIS wrote:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
PL/SQL Release 11.1.0.7.0 - Production
CORE 11.1.0.7.0 Production
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - ProductionIt seems that is a bug,refer
*Bug 8861467 - ORA-22813 / ORA-600 [12761] can occur in 11g [ID 8861467.8]*
To fixing problem you need apply 11.2.0.2 (Server Patch Set)

ORA-01536: space quota exceeded for tablespace 'SYSTEM'

Hi All,
Please help me to understand the below issue. I am trying to create a table as below. Connected as APPS user.
SQL>create table test_ts(id number) tablespace APPS_TS_TX_DATA
ORA-00604: error occurred at recursive SQL level 1
ORA-01536: space quota exceeded for tablespace 'SYSTEM'
ORA-06512: at line 2
Below are the details of the user
SQL>select * from user_ts_quotas
        where tablespace_name = 'APPS_TS_TX_DATA'
TABLESPACE_NAME     BYTES     MAX_BYTES     BLOCKS     MAX_BLOCKS
APPS_TS_TX_DATA     929038336     -1     113408     -1
SQL>select * from user_ts_quotas
        where tablespace_name = 'SYSTEM'
No Rows Returned.

Hi,
Thanks for the response. There is no QUOTA defined for SYSTEM user, so it is UNLIMITED, No?
Below are the details of "SYSTEM" tablespace. Is there any issue with this?
TABLESPACE_NAME           BLOCK_SIZE INITIAL_EXTENT       NEXT_EXTENT           MIN_EXTENTS            MAX_EXTENTS
SYSTEM                  8192               16384         16384                1                     505

ORA-1000 OCCI C++ urgent

Hello
I have a problem
I have an Environemnt in which I execute x times a stored PL/SQL procedure
Environment *env = Environment::createEnvironment();
          Connection *conn = env->createConnection(uzytkownik->zwroc_login(),uzytkownik->zwroc_haslo());
for (int x=0,x<10000;x++)
Statement *stmt = conn->createStatement();
          stmt->setSQL("begin execute_my_procedure;end;");
          stmt->executeQuery();
env->terminateConnection(conn);
Environment::terminateEnvironment(env);
I have an error ORA-1000
what to do??
when I in for loop create an environment , call my procedure and terminate environment everything works fine, but it's not effective becauese every time I connet to database and disconenct
please help
Marcin
[email protected]

In the loop, you need to terminate the statement and free the cursor on the server. Please add inside in the loop :-
conn->terminateStatement(stmt);
Ofcourse, if you are planning to execute the same SQL repeatedly, you can just execute the already created Statement and not create/prepare a new Statement.
Thanks,

Max Cursors Exceeded even with XSU 1.2

In one of the messages on this forum I read Steven Muench's comments stating that the max cursors exceeded problem for big result sets in XSQL has been addressed in XSU1.2
I have downloaded this software released in April 2000 but this version still gives me this error.
Has someone been able to find a solution/workaround to this.
Thanks

It might also be an issue with the HS_OPEn_CURSORS. By default the gateway allows only 50 open cursors to be opened at the foreign database. What happens when you set in the gateway init file HS_OPEN_CURSORS=200?
If it still fails, could you upload to a public file share a gateway trace level DEBUG (HS_FDS_TRACE_LEVEL=DEBUG)?
- Klaus

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

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

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

Cannot log into blend and has said max attempts exceeded, Link will not connect either

I downloaded the Blend software on my macbook pro and it would not log in with my Blackberry ID. After 5 attempts it locked me out.
I reset my Blackberry ID and tried again, but it will not let me even attempt to login and says max attempts exceeded. I uninstalled and reinstalled and still the same problem. Also Link will not let me connect. Any ideas please? looks like I am going over to Iphone if this continues and bin my Z30.

Jeff,
Thanks for the info on policy settings.
Let's see: I had 8.1.5 installed and I tried the update to 10g but only works from 8.1.7 or 9i, so then uninstalled and re-tried to do fresh install in a different home (OraHome10 vs OraHome8). That didn't go so well--it changed my 8i somehow so 8i would no longer work. Then I tried fresh install of 9i with a new starter DB--couldn't get into that DB. So uninstalled 9i, uninstalled 10g, uninstalled 8i, deleted every reference to Oracle on my computer, registry, etc., and re-tried 10g. I even went and bought a registry cleaning tool to zap things to make sure it was clean. It looked like it installed fine, provided me with starter DB but I just can't get into it. I'll let you know if the policy setting works.
I'm trying to look on the bright-side and say that we are learning a lot!
Dave

Ora-1000 max openCursor exceeded

Similar Messages

Maybe you are looking for