bad execution plan

2002-04-30 Thread JOE TESTA
AIX, oracle 8.1.7.2, all 3 tables compute statistics, first_rows optimizer_mode a simple 3 table join, joined on the appropriate columns, works fine. add a fixed constant to the mix and poof, 2 merge-join cartesian. Here is first query w/o the fixed value: select T1.EVENT# c1,

Re: bad execution plan

2002-04-30 Thread Jonathan Lewis
I'd guess the optimizer is applying transitivity to use your constant against all three tables at the optimise stage, and something about the specific value is fooling it. What are the low_value and high_value columns in user_tab_columns for the three columns in the WHERE clause ? Is EV000154