Re: SKIP LOCKED on RAC

From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Mon, 22 Nov 2021 17:17:46 -0500
Message-ID: <310de16d-cf66-3dd0-c8a2-029ca0e9b83f_at_gmail.com>


On 11/22/21 15:52, Andy Klock wrote:
> Hi Mladen,
>
> "Mladen Gogala" <gogala.mladen_at_gmail.com> writes:
>
>> I know that SELECT FOR UPDATE SKIP LOCKED is not supported
>> across the RAC instances but I am unable to find any Oracle
>> documentation documenting that behavior. Can anybody help?
> I can understand leaning towards writing the application to avoid
> concurrent updates from different instances, but I wasn't aware
> that SELECT FOR UPDATE SKIP LOCKED wasn't supported.
>
> Andy K
>
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.

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Nov 22 2021 - 23:17:46 CET

Original text of this message