Great Queries by Select By Attributes doesn't work with ORACLE data, but works with fGDB and SQL Server.
Last Published: August 25, 2014No Product Found
Bug ID Number
NIM031527
Submitted
January 23, 2008
Last Modified
April 28, 2025
Applies to
No Product Found
Version found
9.2
Status
Known Limit
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
Additional Information
No Public Explanation
Workaround
Modify the where clause for your oracle case to use nested queries or joins...Joins would be the fastest - "or" and "in" clauses are normally much slower.Examples:select * from user.Parcels where (PARCEL_ID in (1...1000) orPARCEL_ID in (1001...2000) )=================(select ... from ... where PARCEL_ID in (1, 2, ... 1000) )UNION(select ... from ... where PARCEL_ID in (1001, 1002, ... 2000))...UNION(select ... from ... where PARCEL_ID in (N, N+1, ... M)=================You can use ArcObjects (IDatabaseConnectionInfo2.ConnectionDBMS Property) to determine the type of GDB connected to if needed.