Last updated on JANUARY 21, 2009
Applies to:Oracle Server - Enterprise Edition - Version: 184.108.40.206 to 10.1.0.4
This problem can occur on any platform.
Bad data results when querying an IOT table using its secondary index AND the table is on a tablespace that was imported from 9.2.0.x through a transportable tablespace.
The table has NO unused columns, NO long raw, NO user datatype.
No issues when querying the IOT table WITHOUT using an index.
No issues when querying the IOT table using its primary key index.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms