Posted: Sun Nov 25, 2018 7:26 am
Sorry, wasn't sure why this was in the "MetaData" forum. This is an issue with a 'normal' Parallel job, yes? If so, I'll move it for you.
(and now moved)
DSXchange
A short text to describe your forum
http://www.dsxchange.com/
JDBC Connector Exadata - failed to locate a suitable driver
Page 1 of 1
Posted: Mon Nov 26, 2018 5:59 am
(and now moved)
Posted: Mon Nov 26, 2018 10:05 am
Sorry guys.
This approach of pointing to 'Conductor Node Name' at the advanced sheet only worked out using ODBC Connector.
Actually we are trying to figure out what happens when use JDBC Connector.
As a Workaround, we are using ODBC for now.
Unfortunately we do not have the solution yet.
Thanks,
This approach of pointing to 'Conductor Node Name' at the advanced sheet only worked out using ODBC Connector.
Actually we are trying to figure out what happens when use JDBC Connector.
As a Workaround, we are using ODBC for now.
Unfortunately we do not have the solution yet.
Thanks,