Re: 11g. Incorrect results returned from query.
Date: Tue, 10 Jun 2008 05:29:00 -0700 (PDT)
On 31 May, 00:58, t..._at_panix.com (Dan Blum) wrote:
> Shakespeare <what..._at_xs4all.nl> wrote:
> > "Dan Blum" <t..._at_panix.com> schreef in bericht
> > > Ralph.in..._at_googlemail.com wrote:
> > >> Unfortunately we have attempted to re run our bulk load process (this
> > >> is a DW app) from the beginning and the queries are now showing the
> > >> correct results.
> > >> The first issue we encontered of this type (which I alluded to in my
> > >> first post)
> > >> is still repeatable...)
> > >> Here is the example of that one. I think that the two must be related.
> > > <snip>
> > > I may be missing something obvious, but the results for all three queries
> > > in this example looked correct to me - what is the problem?
> > > --
> > > _______________________________________________________________________
> > > Dan Blum t..._at_panix.com
> > > "I wouldn't have believed it myself if I hadn't just made it up."
> > There's a column missing when more than 4 values are returned fo a row.
> Ah, I was expecting something similar to the other issue, where it was
> rows that were missing. I thought this was just a SQL*Plus display issue.
> Dan Blum t..._at_panix.com
> "I wouldn't have believed it myself if I hadn't just made it up."- Hide quoted text -
> - Show quoted text -
Update: The problem is due to an 11g bug with table compression. We are in the process of producing a test case for OSS. The issue is extremely rare, in our case only effecting 6 rows out of 50 million, so producing a small test case is proving difficult. In the mean time we are not using compression.
Ralph Received on Tue Jun 10 2008 - 07:29:00 CDT