Microsoft ISA Server Restrictions Cause ORA-28500 And MySQL S1000 Errors Using DG4ODBC Or HSODBC
(Doc ID 748584.1)
Last updated on MAY 11, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.2 [Release 10.2 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
A select from SQLPLUS using HSODBC or DG4ODBC to MySQL on a remote server returns the following errors -
Select * from table_name@DG4ODBC;
ORA-28500: connection from ORACLE to a non-Oracle system returned this message::
[Generic Connectivity Using ODBC][MySQL][ODBC 5.1 Driver]Can't connect to MySQL
server on '99.9.999.99' (10060) (SQL State: S1000; SQL Code: 2003)
ORA-02063: preceding 2 lines from DG4ODBC
ORA-28500: connection from ORACLE to a non-Oracle system returned this message::
[Generic Connectivity Using ODBC][MySQL][ODBC 5.1 Driver]Can't connect to MySQL
server on '99.9.999.99' (10060) (SQL State: S1000; SQL Code: 2003)
ORA-02063: preceding 2 lines from DG4ODBC
A connection to the MySQL database from the Windows ODBC Administrator panel using the system DSN or using an ODBC test utility works successfully.
A gateway debug trace shows the following -
(0) hoalgon (7): ; hoalgon Entered. name = test.
(0) errors.h (2112): ; [MySQL][ODBC 5.1 Driver]Can't connect to MySQL server on '99.9.999.99' (10060) (SQL State: S1000; SQL Code: 2003)
(0) DRV_InitTdp: errors.h (2112): ; [MySQL][ODBC 5.1 Driver]Can't connect to MySQL server on '99.9.999.99' (10060) (SQL State: S1000; SQL Code: 2003)
(0) errors.h (2112): ; [MySQL][ODBC 5.1 Driver]Can't connect to MySQL server on '99.9.999.99' (10060) (SQL State: S1000; SQL Code: 2003)
(0) DRV_InitTdp: errors.h (2112): ; [MySQL][ODBC 5.1 Driver]Can't connect to MySQL server on '99.9.999.99' (10060) (SQL State: S1000; SQL Code: 2003)
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |