BUG: Error When Using Table Aliases with Oracle ODBC Driver (186380)
The information in this article applies to:
- Microsoft ODBC for Oracle version 2.0 Build 2.73.7269
- Microsoft ODBC for Oracle version 2.0 Build 2.73.7283.01
- Microsoft ODBC for Oracle version 2.0 Build 2.73.7283.03
- Microsoft ODBC for Oracle version 2.5 Build 2.573.2927
- Microsoft Data Access Components 2.5
This article was previously published under Q186380 SYMPTOMS
When you try to use table aliases in SELECT statements with the Microsoft
Oracle ODBC driver and you are using the Keyset cursor type, you receive
the following error:
[Microsoft][ODBC driver for Oracle]Cannot use Keyset-driven cursor on
join, with union, intersect or minus or on read only result set"
CAUSE
When the driver re-writes the SQL statement to send to the Oracle server it
doesn't create the correct syntax.
Internally, Oracle returns the following error message:
ORA-00964: table name not in FROM list
In turn, The Microsoft Oracle ODBC driver maps that error message to the
message listed in the SYMPTOMS section of this article.
RESOLUTION
The solution depends on the nature of the application. If the application
needs to use Keyset cursors, it may not use table aliases. If the
application must use table aliases, the cursor type must be changed to
FORWARD-ONLY or STATIC.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. We are researching this bug and will post
new information here in the Microsoft Knowledge Base as it becomes
available.
Modification Type: | Major | Last Reviewed: | 12/3/2003 |
---|
Keywords: | kbBug kbDatabase kbDriver kbOracle kbpending KB186380 |
---|
|