You are viewing a plain text version of this content. The canonical link for it is here.

Posted to ojb-user@db.apache.org by Mindy Pereira <Mi...@appiancorp.com> on 2004/08/02 18:35:39 UTC

Bizarre object update error

Have been running this application for several months now, and was told
someone was unable to update one of the beans. Checked the logs, and
found the following strange message. Does the error mean anything to
anyone?

org.apache.ojb.broker.PersistenceBrokerSQLException: ORA-04031: unable
to allocate 4096 b\
ytes of shared memory ("shared pool","unknown object","library
cache","oacdef info")


Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org

Re: Bizarre object update error

Posted by Thomas Dudziak <to...@first.fhg.de>.

Mindy Pereira wrote:

>Have been running this application for several months now, and was told
>someone was unable to update one of the beans. Checked the logs, and
>found the following strange message. Does the error mean anything to
>anyone?
>
>org.apache.ojb.broker.PersistenceBrokerSQLException: ORA-04031: unable
>to allocate 4096 b\
>ytes of shared memory ("shared pool","unknown object","library
>cache","oacdef info")
>  
>
This is a common Oracle error. See here for strategies:

http://otn.oracle.com/pub/articles/10gdba/week17_10gdba.html

Tom


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org