LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Error in JDBC Query node

    Employee
    Posted 01-29-2014 09:19

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Sreya

    Hi All,

    I am tryinh to use JDBC Query node. I have given my database user name and password correctly. Now I am not sure on what should be given as DBurl and DBdriver field.

    I have given URL as: <database_schema name>@//172.25.69.49:1521/orcl
    driver as: jdbcracle:thin:@//machine_ip:1521/orcl

    But I am getting the following error:
    Exited with non zero status
    2014-01-29 21:45:38.000; ERROR: unable to load db driver: jdbcracle:thin:@//172.25.69.49:1521/orcl
    id: 0 chain: 0 group: 0
    cppDetail: context: loadDBDriver DBNode.java@47

    2014-01-29 21:45:38.000; ERROR: Exited with non zero status
    id: 0 chain: 0 group: 0
    cppDetail: context: Salmon::NED::NodeMain::errorMsg() .\NodeMain.cpp@28


    Can anybody help me on this?
    Thanks a lot..


  • 2.  RE: Error in JDBC Query node

    Employee
    Posted 01-29-2014 09:44

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ejones

    For Oracle, the DbDriver should be oracle.jdbc.OracleDriver

    The value you currently have in DbDriver looks like the correct value for DbUrl for an Oracle database.

    This web site shows several possible versions of the JDBC URL. For me, there have been a few instances where the URL that has the TNS names entry was the only one I could get working. http://www.orafaq.com/wiki/JDBC


  • 3.  RE: Error in JDBC Query node

    Employee
    Posted 01-29-2014 10:04

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Sreya

    hi,

    Even after trying with the full tns name entry in the url, and "oracle.jdbc.OracleDriver" as the driver name, I am getting the same error mentioned above. Is there any possibility where I can go wrong?


  • 4.  RE: Error in JDBC Query node

    Employee
    Posted 01-29-2014 10:20

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ejones

    So the error message looks the same? hmm. Please check to make sure the DbDriver value is different.

    The error you posted at first contains this message: ERROR: unable to load db driver: jdbcracle:thin:@//172.25.69.49:1521/orcl
    And "jdbcracle:thin:@//172.25.69.49:1521/orcl" looks like a valid value for DbUrl. And DbDriver should have a syntax that looks more like string.string. ...


  • 5.  RE: Error in JDBC Query node

    Employee
    Posted 01-29-2014 10:27

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Sreya

    yes. I have corrected that in my graph. I have given DB driver as "oracle.jdbc.OracleDriver"
    and db URL as "jdbcracle:thin:@//machine_ip:1521/orcl"

    Still the same error comes up.


  • 6.  RE: Error in JDBC Query node

    Employee
    Posted 01-29-2014 10:53

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ejones

    So, I'm hearing two things.
    1) The error message you're seeing states that the value you have in DbDriver is jdbcracle:thin:@//machine_ip:1521/orcl
    2) Your post telling me that the value in DbDriver is the correct one for Oracle, oracle.jdbc.OracleDriver
    Then my brain spinning around trying to reconcile the conflicting information. When I'm seeing things like this in my own work, I start wondering whether the software is working correctly. And then in the process of proving to myself or someone else that the software is broken I find my mistake.