According to my experience with simple Java-based applications and ORACLE, it
is very easy to exceed that limit of 50 open cursors, so we always set it to a
minimum of 500 after an ORACLE installation. I have this advice from an ORACLE
DBA book where they write that you should always increase the value
significantly.
So I would say that you should increase that parameter in any case, but also
put an eye on the quality of your data-fetching code.
Regards,
Hans-Dieter Cordes
-----Original Message-----
From: Jean-Christophe Pazzaglia
[mailto:[EMAIL PROTECTED]
Sent: Dienstag, 2. August 2005 11:52
To: [email protected]
Subject: Re: RE : ORA-01000: maximum open cursors exceeded
... and send the DB engine to the cleaner ....
closing the query => close the cursor and free some memory
is probably a better solution indeed ...
however IMHO you should think twice to run 1000's queries
in parallel, or even sequentially if it is not necessary,
(you are each time paying a huge overhead ... network, query opt, ....)
and you should probably consider to change the way you populate your
xml from the db ...
and except for the last entence it is not xml related ....
so I apologise :)
jc
>Hello Celinio,
>
>I have some ORACLE background, and here is what I would say:
>
> - every SQL statement you run against an ORACLE server
> opens a database cursor implicitly
> - there is an "OPEN_CURSORS" parameter in the "init.ora"
> file that the server uses for its own initialsation;
> the default value is 50
> - the "OPEN_CURSORS" parameter defines the maximum of open
> cursors a given user can have in parallel
> - to avoid the given ORACLE error message, you should
> ask your ORACLE admin to change the "OPEN_CURSORS"
> value in the "init.ora" file (the file name may be
> different in your environment!) to a much higher
> value, let us say 1000 or so; or ask the admin
> for his/her experiences
>
>I hope this will help you with your ORACLE problem.
>
>Regards,
> Hans-Dieter Cordes
>
>-----Original Message-----
>From: Celinio Fernandes [mailto:[EMAIL PROTECTED]
>Sent: Dienstag, 2. August 2005 11:15
>To: [email protected]
>Subject: RE : ORA-01000: maximum open cursors exceeded
>
>
>I got my answer, I need to use:
> instruction.close();
>
>
>Still, does anyone know a proper way to do it with Xmlbeans ?
>Thanks
>
>To : [email protected]
>Object : ORA-01000: maximum open cursors exceeded
>
>
>Hi,
>
>I would like to make sure this error has nothing to do with XMLbeans. I
>am executing a SELECT query each time I have a father tag, to get
>information about him, passing the son and daughter as arguments to the
>SELECT query. There are like 1000 fathers, and the maximum open cursors
>in Oracle is limited to 50.
>
></grandfather>
> <father>
> <son>aaa</son>
> <daughter>bbb</daughter>
> </father>
> <father>
> <son>ccc</son>
> <daughter>ddd</daughter>
> </father>
> <father>
> <son>eee</son>
> <daughter>fff</daughter>
> </father>
> etc ...
><grandfather>
>
>So, before digging into the JDBC stuff, i would like to make sure: Does
>Xmlbeans handle queries differently ? I mean I do not open any cursor
>when I execute a SELECT query. So where do these open cursors come from
>?
>
>Also, if you know another way to do it, please let me know.
>
>Thanks for your feedback.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
Jean-Christophe Pazzaglia, PhD <[EMAIL PROTECTED]>
Corporate communications
Tel: (+33) 4-93-00-26-78
PGP Key available : http://www.eurecom.fr/~pazzagli/publickey.pgp
--
Institut Eurécom - Office 029
http://www.eurecom.fr/
2229 Route des Crêtes
BP 193
06904 Sophia Antipolis, France
Fax: (+33) 4-93-00-26-27
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
