Full Index Scan in Execution Plan With Access and Double or Float as Primary Key
Last updated on JULY 05, 2017
Applies to:Oracle ODBC Driver - Version 10.1.0.2 and later
Microsoft Windows (32-bit)
***Checked for relevance on 06-Sep-2015***
When using Microsoft Access with a complex query using a Doubles or a Float datatype as a Primary Key resulted in a full index scan.
EXPLAIN PLAN shows a full scan occurring
1. INDEX UNIQUE SCAN WC_JSPP_PK (cr=3 pr=0 pw=0 time=72 us)(object id 90392)
2. INDEX UNIQUE SCAN WC_JSPP_PK (cr=3 pr=0 pw=0 time=60 us)(object id 90392)
3. INDEX FAST FULL SCAN WC_JSPP_PK (cr=78721 pr=0 pw=0 time=77430422 us)(object id 90392)
Same problem does not appear initially using SQL*Plus with same query, in a simple VB script, or using the Microsoft ODBC Driver for Oracle.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms