Re: Logminer showing an update that could not have happened
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: cshapi@xxxxxxxxx
- Date: Sat, 7 Nov 2009 08:12:55 +0000
It's a pretty (in)famous bug. Definitely one to be aware of or make
the patch case. Incidentally Oracle keep an updated list of bugs,
including serious ones properly highlighted, on metalink
On 11/7/09, Chen Shapira <cshapi@xxxxxxxxx> wrote:
> Bingo!
> Yes, this DB id 10.2.0.2 and we have all the symptoms.
>
> I didn't even think of checking for this description in metalink
> because I was so sure these things can't happen. This is a huge
> security issue.
>
> Now I'm wondering how quickly management will react and whether we'll
> have an emergency change to patch this on Sunday :)
>
> Wow, I'm still shocked. Both by the bug and by how quickly you nailed it.
>
> Thanks a lot!!!!
>
> Chen
>
> On Fri, Nov 6, 2009 at 8:20 PM, Justin Cave (DDBC) <jcave@xxxxxxxxxxx>
> wrote:
>> What version of Oracle are you using? Any chance that you are being
>> affected by Bug 5458753 - SQL may execute in wrong schema (also discussed
>> in Doc ID 392673.1)? That affects 10.2.0.2-- I thought it was resolved in
>> 10.2.0.3.
>>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
Sent from my mobile device
Niall Litchfield
Oracle DBA
http://www.orawin.info
--
//www.freelists.org/webpage/oracle-l
Other related posts:
