Re: Informix returning inconsistent resultset

Set the explain plan on. Rerun the query. Note which index the query is using. Force it to do a scan using optimizer hinting. select {+ full(ledgdet) } ... I think that is the correct syntax. If you get all 40 rows then drop and rebuild the index found earlier and then try the query again. If this fixes it then it was the index. If not then if might actually be an informix bug. Or a problem with the sql that is typed in. Try retyping the query or using the "od" command to find funny characters that may be affecting the execution of the query. bardavidh@yahoo.com (Hakan Bardavid) wrote in message news:<7db4101a.0408180557.669c493d@posting.google.com>... > The following simple query I have , is returning 38 rows , although > I know that it should return me 40 rows. > > select * from ledgdet where lindex in > (2279561,2245322,2279562,2245323, > 2242315, > 2242319,2244911,2244915, > 2256408 ,2256412 ,2279565, > 2242316,2242320,2244912, > 2244916, 2256409 ,2256413 ,2279566, > 2279563,2279564,2245324,2245325, > 2242317,2242318,2242321,2242322,2244913,2244914, > 2244917,2244918,2256410,2256411,2256414,2256415, > 2256417,2256418,2279563,2279564,2279567,2279568)> > It is not returning me the rows associated with lindexes > 2279563,2279564 > > if I execute the following query > select * from ledgdet where lindex in (2279563,2279564)> I am getting those two rows. > > > I am executing this query using dbaccess utility. In addition to that, > I already run oncheck on this table. It didn't report any errors. > > Does anyone have idea other than dropping and recreating indexes? > > Any help will be greatly appreciated. > Thanks in advance