Hi Ken, OraOop should be using the NO_INDEX hint, we'll get that fixed for the next release.
Until then you may be able to work around this issue with session initialization statements. Try ALTER SESSION SET optimizer_index_cost_adj=10000; to tell oracle to not use the index. You may need to experiment with this a little to find a value that will have the desired effect. Also check the OPTIMIZER_MODE on the database. If it is set to FIRST_ROWS that could explain why Oracle is trying to use the index. Add ALTER SESSION SET optimizer_mode='ALL_ROWS'; if this is the case. Let us know if the ALTER SESSION statements don't fix your issue, we can do a patch release if necessary. Regards, Peter Hall
