Home/ Questions/Q 6244339
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T12:18:34+00:00

I am facing a wierd problem where the same query is returning different results.

  • 0

I am facing a wierd problem where the same query is returning different results.

My query is:

SELECT * FROM TX_HISTORY  WHERE acct = 7  AND ROWNUM

What is happening is that I know that for this account there are more than 100 records in tx_history. I want to get the first 100 records based on the processing date.
My data for this account is I have records from 2004 till 2011

The problem is sometimes it correctly shows the 100 records starting 2004 – but sometimes it shows me 100 records starting 2005

I read that this can be solved by:

SELECT * FROM (select * from TX_HISTORY  WHERE acct = 7  ORDER BY acct,processing_date)
where rownum

so in my earlier query is it that the:
1> My understanding is that the order by is being applied after the rownum <= 100 and the results returned by oracle are in a random order on which row num is filtering

Though what is not understood why the results would vary
Thanks,
~akila

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you do not specify any ordering (and in this case, as you already found out, you do not order the data being retrieved, you only sort afterwards), it is up to the database to return them in any order it sees fit.

    It could for example just start reading the rows in the order they are stored, which changes as the data gets updated. It also does not have to start from the top of the table, it could start with the blocks already in the buffer cache.

    Since you did not specify the order, the DB will choose (what it thinks to be) the least expensive way available to it at this particular moment.

    • 0