I created an index in the exact order(18 Fields) called AD214X12.
The first time I submit the job it picks a different logical AD214L09 and performs miserably
Message . . . . : All access paths were considered for file AD214M01.
Cause . . . . . : The query optimizer considered all access paths built over
member AD214M01 of file AD214M01 in library EPLIB. The list below shows the
access paths considered....
User Profile
Collapse
-
Gxbuxton started a topic SQL Optimizer - Picks different Logicals/Index when same job run twice in a rowin DB2SQL Optimizer - Picks different Logicals/Index when same job run twice in a row
No activity results to display
Show More