[Info-ingres] Re: Weird Optimizer Error
- From: martin.bowes@xxxxxxxxxxxxx
- Date: Wed, 17 May 2006 12:52:02 +0100
Hi Dudes,
The saga continues....
For those with a long memory, Dec 22 2005 in fact, I've had an
installation that is plagued by E_OP0393 errors.
Since then, I've gone so far as to convert the installation from an SQL-
92 compliant box to a standard Ingres Installation. II2.6 patch 11481.
And the problem has just resurfaced....
I've now managed to use trace point sc924 to identify the query causing
the problem and it is a very simple single table select. However,
everytime I repeat the query, the error does not surface. I've even
recovered the database to the time of the error onto another host and
ran the query there - still no luck.
The table in question is a 2million row btree non unique keyed on 2
fields. The query sets specific values for these key items.
ie.SELECT npart, part, txt FROM blobsim WHERE cid=2701 AND
trid=1011 AND fieldname='b_auxvar' ORDER BY part\g
cid and trid are the key of the table. They are both integer non-nullable
fields.
The table has an isam secondary index that reverses this key, don't ask
me why. I've since dropped this index.
The stats are built on the table without error.
I've set query auditing on for the user who executes the application that
gives these errors.
Anyone got any ideas what else I can do?
Marty
--
Random Duckman Quote #110:
Charles/Mambo: Dad hasnt got lucky since he convinced a blind
Seinfeld obsessed groupie he was Jason Alexander in a Duck suit.
.
- Follow-Ups:
- Re: Weird Optimizer Error
- From: izena
- Re: Weird Optimizer Error
- Prev by Date: Re: NULLs in Ingres
- Next by Date: Re: Weird Optimizer Error
- Previous by thread: NULLs in Ingres
- Next by thread: Re: Weird Optimizer Error
- Index(es):
Relevant Pages
|