Re: Oracle 11.2: Cursor Mutex S wait event and too many (2^30) child cursors
- From: Tanel Poder <tanel@xxxxxxxxxx>
- To: Dion Cho <ukja.dion@xxxxxxxxx>
- Date: Thu, 5 Aug 2010 08:15:59 +0800
In 11g, they have built a whole new diagnostics infrastructure, trace the
whole kernel, trace only when certain conditions are met, etc...
Typing ORADEBUG DOC in the sqlplus command prompt is a good starting
point...
http://tech.e2sn.com/oracle/troubleshooting/oradebug-doc
Tanel.
> This means that Oracle 11g now has a totally redesigned trace
> functionality!
>
> ================================
> Dion Cho - Oracle Performance Storyteller
>
> http://dioncho.wordpress.com
> ================================
>
>
> 2010/8/4 Martin Klier <usn@xxxxxxxxx>
>
>> Hi listers,
>>
>> not at least with help from this list (Tanel and others) I was able to
>> sort out a nasty situation with Oracle 11gR2's child cursors. Details
>> are here:
>>
>>
>> http://www.usn-it.de/index.php/2010/08/04/oracle112-mutex-s-too-many-child-cursors/
>>
>> Summary: If you use JDBC and set numeric values with setInteger or
>> setNumber or setNull alternately, you can get excessive numbers of child
>> cursors for your DML statement.
>>
>> Solution: Use setNull.NUMBER or setNull.INTEGER or whatever your
>> datatype is.
>>
>>
Other related posts:
