This content has been marked as final. Show 19 replies
A similar table works for my MySQL database connection. Just an idea that came into my mind. When you create a dummy table with a char column only, are you able to select from this column?
And what about select user from dual@<your database link name> - does this work?
The dual table does not exist in the MySQl database and commonly the gateway has to use an internal mechanism to get a result, does this work for you?
Getting following error :
Error starting at line 1 in command:
select * from "dual"@monolith3
Error at Command Line:1 Column:14
SQL Error: ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[MySQL][ODBC 5.2(w) Driver][mysqld-5.5.20-enterprise-commercial-advanced-log]No tables used
ORA-02063: preceding 2 lines from MONOLITH3
28500. 00000 - "connection from ORACLE to a non-Oracle system returned this message:"
*Cause: The cause is explained in the forwarded message.
*Action: See the non-Oracle system's documentation of the forwarded
Normally it should come back and report the user who's currently logged into the Oracle database:
SQL> select user from dual@MYSQL_DG4ODBC_EMGTW_1123_DB;
So there's definitely something wrong with the driver manager or the driver itself. As I never trust rpm's from unknown sources so I downloaded the tar file from MySQL directly - the file I'm using is from the tar file: mysql-connector-odbc-5.2.2-linux-glibc2.3-x86-64bit
Maybe you should also use the tar file - it contains the prebuilt libs and you only need to change the DRIVER parameter in the odbc.ini file pointing now to the new lib.
We have installed unixODBC-2.3.1 which is downloaded from
Also the mysql connector (mysql-connector-odbc-5.2.3-linux-glibc2.3-x86-64bit.tar.gz) downloaded from following location is installed
-bash-3.2$ odbcinst -j
SYSTEM DATA SOURCES: /usr/local/etc/odbc.ini
FILE DATA SOURCES..: /usr/local/etc/ODBCDataSources
USER DATA SOURCES..: /home/oracle/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8
But unfortunately still we get the same error.
Can you please provide me an ODBC trace when you use the new driver/driver manager with the gateway and try to select from your table?