Oracle has removed JDBC ODBC bridge driver support in Java 1.8 and it affects following connections apart from Generic ODBC.
3) Informix - ODBC
We will need to extend the JDBC - ODBC bridge driver approach defined by Emilian to all ODBC connections.
|
20 KB
@QA,
We want to ensure that the following ODBC connection type works for Microsoft Windows:
3) Informix - ODBC
We need to test under:
- windows 32-bit using 32-bit ADS.
- windows 64-bit using 64-bit ADS.
- windows 64-bit using 32-bit ADS.
Verified on windows 64-bit using 64-bit ADS, and windows 64-bit using 32-bit ADS.
However, could not verify on windows 32-bit using 32-bit ADS because our systems do not have 32- bit OS.
I came across an issue while testing on Oracle,it does not display schema's,and all the objects from the tree node,only few objects like Table,Synonym ,Views,Procedures and User Defined types objects are displayed.In order to install oracle odbc drivers. I downloaded and installed ODAC and then I made connection to ADS with oracle odbc drivers.
Kindly let me know weather the approach is correct.
Please refer image :Oracle_ODBC.png
I wilI change its status to verified after your response on my approach.
Verified on windows 64-bit using 64-bit ADS, and windows 64-bit using 32-bit ADS.
However, could not verify on windows 32-bit using 32-bit ADS because our systems do not have 32- bit OS.
I came across an issue while testing on Oracle,it does not display schema's,and all the objects from the tree node,only few objects like Table,Synonym ,Views,Procedures and User Defined types objects are displayed.In order to install oracle odbc drivers. I downloaded and installed ODAC and then I made connection to ADS with oracle odbc drivers.
Kindly let me know weather the approach is correct.
Please refer image :Oracle_ODBC.png
I wilI change its status to verified after your response on my approach.
I downloaded and installed ODAC and then I made connection to ADS with oracle odbc drivers.
This is most likely expected behavior b/c you're using the generic ODBC connection vs the native connection. You can try the same thing w/ v16 & verify that you get the same results.
I downloaded and installed ODAC and then I made connection to ADS with oracle odbc drivers.
This is most likely expected behavior b/c you're using the generic ODBC connection vs the native connection. You can try the same thing w/ v16 & verify that you get the same results.
>>You can try the same thing w/ v16 & verify that you get the same results.
We get the same result when we perform odbc-jdbc connection in V16 for oracle database.
>>You can try the same thing w/ v16 & verify that you get the same results.
We get the same result when we perform odbc-jdbc connection in V16 for oracle database.
Verified in ADS 17.0.0-dev-22
Verified on the following builds and operating system :
- windows 64-bit using 64-bit ADS.
- windows 64-bit using 32-bit ADS.
Not able to test and verify on windows 32-bit using 32-bit ADS as we do not have 32-bit operating systems.
Verified in ADS 17.0.0-dev-22
Verified on the following builds and operating system :
- windows 64-bit using 64-bit ADS.
- windows 64-bit using 32-bit ADS.
Not able to test and verify on windows 32-bit using 32-bit ADS as we do not have 32-bit operating systems.
Issue #13279 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build ADS 17.0.0-dev-22 |
No time estimate |
2 issue links |
relates to #14210
Issue #14210JDBC-ODBC is not working with java 1.8 |
relates to #13141
Issue #13141Integrate JDBC - ODBC Bridge Approach defined by Emilian |
@QA,
We want to ensure that the following ODBC connection type works for Microsoft Windows:
3) Informix - ODBC
We need to test under:
- windows 32-bit using 32-bit ADS.
- windows 64-bit using 64-bit ADS.
- windows 64-bit using 32-bit ADS.