Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: ora-1555, order by, x, kyte

Re: ora-1555, order by, x, kyte

From: Niall Litchfield <n-litchfield_at_audit-commission.gov.uk>
Date: Tue, 6 Apr 2004 10:26:36 +0100
Message-ID: <407277cc$0$3306$ed9e5944@reading.news.pipex.net>


"Paul" <pkelley_at_coat.com> wrote in message news:473377b4.0404051228.68ac9624_at_posting.google.com...
> Alrighty, then,...
>
> In late February 2004, "X" posted some notes from metalink re using
> "order by" to dodge ora-1555. He was lambasted in this group.

I can't see this discussion on Google, is there a link to it?

>
> Here's something from asktom.oracle.com re snapshot too old:
>
> " Hi
>
> In the note you provided in point 6 of solutions of case 1 it
> states this:
>
> 6. Ensure that the outer select does not revisit the same block
> at different times during the processing. This can be achieved by :
>
> - Using a full table scan rather than an index lookup
> - Introducing a dummy sort so that we retrieve all the data, sort
> it and then sequentially visit these data blocks.
>
> How can a sort avoid this error?
>
> Followup:
>
> Umm, by RETRIEVING all of the data (before the first row is
> returned -- before a commit happens) "
>
> It looks as if the "Introducing a dummy sort..." snippet was from a
> Metalink note that Kyte included verbatim in his initial followup.
>
> Comments are welcome.

This one I did find, unfortunately I can't tell if the situations are the same in the two cases. Providing some actual information might help.

cheers

-- 
Niall Litchfield
Oracle DBA
Audit Commission UK
Received on Tue Apr 06 2004 - 04:26:36 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US