Skip locked is the foundation for Oracle Advanced Queues, these are
supported on RAC so I would be very surprised if the clause was not.
The docs
https://docs.oracle.com/database/121/ADQUE/aq_intro.htm#ADQUE2431
recommend having a different queue per instance (so instances don’t have
to communicate locks between themselves) but states that it does work.
Thanks,
Andy
On Mon, 22 Nov 2021 at 22:40, Andy Klock <andy@xxxxxxxxxxxxx> wrote:
Hi Mladen,
"Mladen Gogala" <gogala.mladen@xxxxxxxxx> writes:
I was told that by an Oracle Support engineer after working on a
SR for one of the customers. SKIP LOCKED was causing a nice
little ORA-00600 and the support guy told me that we really
shouldn't be using SKIP LOCKED across the RAC
instances. However, I cannot locate any support article stating
that explicitly. ORA-00600 is an Oracle bug, by definition. Now,
I would like to see that documented somewhere.
It's possible that there is some scenario with that version that
caused the bug to manifest. But in general, I can't think of a
reason why it wouldn't be supported.
This note:
ORA-600[13009] from SELECT FOR UPDATE in a RAC Database (Doc ID
2168419.1)
Seems to imply that SKIP LOCKED is what you would use specifically
on RAC if you couldn't fix the application to keep the updates to
stay on their side.
Andy K
--
//www.freelists.org/webpage/oracle-l
