I am running this query
Both tables have a non-unique index on key1,2,3 in that order.
However the SQL processor is not using the table1 index, it's doing a Table Scan (over 6.3 million rows) instead.
Visual Explain, when I click on the Table Scan and look at "Information About the Plan Performed", I see:
Interestingly, TABLE1LB is the logical that provides the index it should be using.
The only thing of note, is that TABLE1LB is a DDS logical that specifies the keyword FIFO, which I have never seen before. The table has many other DDS logicals, but no actual SQL indexes (that I can find)
Can anyone tell me what "Indexes do not match" means, and/or why the SQL processor may not be ignoring the index provided by the TABLE1LB logical?
Code:
SELECT * FROM table1 a INNER JOIN table2 b ON a.key1 = b.key1 AND a.key2 = b.key2 AND a.key3 = b.key3
However the SQL processor is not using the table1 index, it's doing a Table Scan (over 6.3 million rows) instead.
Visual Explain, when I click on the Table Scan and look at "Information About the Plan Performed", I see:
Code:
Information About the Plan Performed Scrollable Yes Plan Name Table Scan Plan Step Type Logic Reason Code Indexes Do Not Match Plan Step Name Node_40 List of Indexes Optimized MYLIB/TABLE1LA 11, MYLIB/TABLE1LB 4
The only thing of note, is that TABLE1LB is a DDS logical that specifies the keyword FIFO, which I have never seen before. The table has many other DDS logicals, but no actual SQL indexes (that I can find)
Can anyone tell me what "Indexes do not match" means, and/or why the SQL processor may not be ignoring the index provided by the TABLE1LB logical?
Comment