[Dspace-tech] ORA-01000: nUmero mAximo de cursores abiertos excedido

[Rodrigo Castro Artigas]

HI, I AM run process import and have the followind message:

java.sql.SQLException: ORA-01000: número máximo de cursores abiertos
excedido
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
at
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:21
6)
at
oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.
java:966)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
:1170)
at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedSta
tement.java:3339)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
ment.java:3423)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Delegating
PreparedStatement.java:101)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Delegating
PreparedStatement.java:101)
at
org.dspace.storage.rdbms.DatabaseManager.updateQuery(DatabaseManager.java:51
9)
at
org.dspace.storage.rdbms.DatabaseManager.updateQuery(DatabaseManager.java:53
9)
at org.dspace.browse.Browse.itemRemoved(Browse.java:439)
at org.dspace.content.Collection.delete(Collection.java:952)
at org.dspace.content.Community.removeCollection(Community.java:751)
at
org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.doDSPost(EditCommu
nitiesServlet.java:275)
at
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java
:147)
at
org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:105)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)

The solution with change configuration Dspace or Oracle??????????

Atte.,
Rodrigo

[Graham Triggs]

Hi,

Ensure that you have disable the prepared statement cache in your
dspace.cfg:

db.statementpool = false

G

> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> DSpace-tech mailing list
> DSpac...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
This email has been scanned by Postini.
For more information please visit http://www.postini.com

[Blanco, Jose]

Graham:

I notice that the default for db.statementpool is true, should we have this set to false. What is the danger in leaving it at true?

Thanks!
Jose

[Graham Triggs]

Simply put, if you are using an Oracle database, it simply doesn't work
(usefully).

Every PreparedStatement that is cached will have an open Connection
attached to it, which can't be re-used by the pool.

If you want to use statement pools with Oracle, then you'll need to
rewrite the DatabaseManager to use Oracle's own implicit connection
cache instead of dbcp (which is kind of on my to do list).

- although, if you can ensure that the PreparedStatement cache can never
be larger than the connection pool, then you presumably should be ok.

I'm not sure of the exact behaviour of the Postgres driver as I haven't
had cause to look into it - but this is an issue to be aware of with Oracle.

G

Blanco, Jose wrote:
> Graham:
>
> I notice that the default for db.statementpool is true, should we have this set to false. What is the danger in leaving it at true?
>
> Thanks!
> Jose
>
> -----Original Message-----
> From: dspace-te...@lists.sourceforge.net [mailto:dspace-te...@lists.sourceforge.net] On Behalf Of Graham Triggs
> Sent: Tuesday, December 11, 2007 12:49 PM
> To: Rodrigo Castro Artigas
> Cc: dspac...@lists.sourceforge.net
> Subject: Re: [Dspace-tech] ORA-01000: nUmero mAximo de cursoresabiertos excedido
>
> Hi,
>
> Ensure that you have disable the prepared statement cache in your
> dspace.cfg:
>
> db.statementpool = false
>
> G
>
> On Tue, 2007-12-11 at 14:26 -0300, Rodrigo Castro Artigas wrote:
>
>> HI, I AM run process import and have the followind message:
>>

>> java.sql.SQLException: ORA-01000: número máximo de cursores abiertos

[marcelo.carius]

increase open_cursors on init<sid>.ora, if use oracle9i, oracle10g. Edit this
file and execute follow commands after save the file:



open_cursors=900 -- for example

SQL>shutdown;
SQL>startup pfile=<path>/ini<sid>.ora;
SQL>create spfile from pfile;

this command can modified only with restart database.




On Tue, 11 Dec 2007 13:02:46 -0500, Blanco, Jose wrote

> Graham:
>
> I notice that the default for db.statementpool is true, should we
> have this set to false. What is the danger in leaving it at true?
>
> Thanks!
> Jose
>
> -----Original Message-----
> From: dspace-te...@lists.sourceforge.net [mailto:dspace-tech-
> bou...@lists.sourceforge.net] On Behalf Of Graham Triggs Sent:
> Tuesday, December 11, 2007 12:49 PM To: Rodrigo Castro Artigas Cc:
> dspac...@lists.sourceforge.net Subject: Re: [Dspace-tech] ORA-
> 01000: nUmero mAximo de cursoresabiertos excedido
>
> Hi,
>
> Ensure that you have disable the prepared statement cache in your
> dspace.cfg:
>
> db.statementpool = false
>
> G
>
> On Tue, 2007-12-11 at 14:26 -0300, Rodrigo Castro Artigas wrote:
> > HI, I AM run process import and have the followind message:
> >

> > java.sql.SQLException: ORA-01000: número máximo de cursores abiertos

--
Open WebMail Project (http://openwebmail.org)