Re: Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors

From: Jared Still <jkstill@xxxxxxxxx>
To: usn@xxxxxxxxx
Date: Wed, 4 Aug 2010 11:02:40 -0700

On Wed, Aug 4, 2010 at 6:06 AM, Martin Klier <usn@xxxxxxxxx> wrote:

> Solution: Use setNull.NUMBER or setNull.INTEGER or whatever your
> datatype is.
>
>
Thanks Martin.  We have a Java app, and will be checking for that before
any upgraded to 11g.


Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com

References:
- Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors
  - From: Martin Klier

Other related posts:

» Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors- Martin Klier
» RE: Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors- Michael Dinh
» RE: Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors- Goulet, Richard
» Re: Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors - Jared Still
» Re: Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors- Martin Klier
» Re: Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors- Dion Cho
» Re: Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors- Tanel Poder
» Re: Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors- Glenn Santa Cruz