Re: Wait Event “cursor: pin s” in Oracle Applications
Date: Fri, 21 Dec 2018 17:33:45 -0800
Message-ID: <CAMHX9JJRHxg81HKWjqsxcgr_zvDKy4GZagZRfjFc__ifuiW8kA_at_mail.gmail.com>
I exchanged a couple of emails with Kumar offline, these sessions were
burning CPU, not waiting.
--
Thanks,
Tanel.
On Thu, Dec 20, 2018 at 12:38 AM Andy Sayer <andysayer_at_gmail.com> wrote:
> Kumar, you missed my first question which was
> ‘What are the duration of these waits?’
> As Tanel suggested, it might just be that they happened instantaneously
> but have been left as the last wait event of the sessions because they are
> purely busy on CPU once they obtain the cursor pin.
>
> Hope this helps,
> Andy
>
> On Wed, 19 Dec 2018 at 11:21, Luis Santos <lsantos_at_pobox.com> wrote:
>
>> Mladen, you probably talking about the *_spin_count* parameter, which
>> defaults to 2000.
>>
>> *--*
>> *Att*
>>
>>
>> *Luis Santos*
>>
>
--
http://www.freelists.org/webpage/oracle-l
Received on Sat Dec 22 2018 - 02:33:45 CET