JDBC Connector Exadata - failed to locate a suitable driver

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

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.
-craig

"You can never have too many knives" -- Logan Nine Fingers
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

8)

(and now moved)
-craig

"You can never have too many knives" -- Logan Nine Fingers
joycerecacho
Participant
Posts: 298
Joined: Tue Aug 26, 2008 12:17 pm

Post by joycerecacho »

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,
Joyce A. Recacho
São Paulo/SP
Brazil
Post Reply