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

  • From: Mladen Gogala <gogala.mladen@xxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Mon, 24 Dec 2018 15:39:27 -0500

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

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


Other related posts: