Query optimizer tells me to build an access path that already exists

[rick.baird@xxxxxxxxxxxxxxx]

hey all,

here's a puzzler.

I've got a rather complicated opnqryf join, that has selection criteria for
both files, one of which is on a %sst of an alpha field.  It's a dog,
mostly because the files are really large.

I ran the thing under debug to see what the query optimizer tells me, and
lo and behold, it told me to build indexs over the files.

problem is, the index it told me to build over one of them is EXACTLY the
primary key of the physical.

now, why would it want me to do that?

any  would be appreciated...

Rick