Re: Wait Event “cursor: pin s” in Oracle Applications

From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Mon, 24 Dec 2018 15:39:27 -0500
Message-ID: <0c06330d-5eac-4c19-15a6-16d30a1c5026_at_gmail.com>

That is pretty much expected with latch waits. Latch waits are "active waits", the waits burning CPU. However, if the instance is set in multi-threaded mode, the latch waits are much cheaper and the impact to the CPU pool much lower. However, the average wait is longer.

Regards

On 12/21/18 8:33 PM, Tanel Poder wrote:
> I exchanged a couple of emails with Kumar offline, these sessions were
> burning CPU, not waiting.
>
> --
> Thanks,
> Tanel.
>

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Dec 24 2018 - 21:39:27 CET

This message: [ Message body ]
Next message: Rakesh Ra: "Re: Huge plain inserts response time bad with db file sequential read wait event."
Previous message: Mladen Gogala: "Re: ALTER DATABASE ARCHIVELOG COMPRESS ENABLE"
In reply to: Tanel Poder: "Re: Wait Event “cursor: pin s” in Oracle Applications"
In reply to Tanel Poder: "Re: Wait Event “cursor: pin s” in Oracle Applications"
Next in thread: Mladen Gogala: "Re: Wait Event “cursor: pin s” in Oracle Applications"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message