Author |
Message
|
veera_clr |
Posted: Mon Oct 12, 2009 4:00 am Post subject: JDBCException |
|
|
Novice
Joined: 12 Oct 2009 Posts: 17
|
Hi All,
I am new to WBIMB.
I am working on WBIMB6.1 Database route node. While interacting with the Database Route node throwing following exception.
com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:162)
com.ibm.broker.jdbcnodes.JDBCConnection.createConnection(JDBCConnection.java:257)
com.ibm.broker.jdbcnodes.JDBCConnection.getNodeConnection(JDBCConnection.java:128)
com.ibm.broker.jdbcnodes.DatabaseRouteNode.evaluate(DatabaseRouteNode.java:408)
com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1434)]'
The node was unable to establish a connection to the given database URL.
Contact your WebSphere Message Brokers administrator.
Could you any body help me on this. What might be the problem. |
|
Back to top |
|
 |
stallin |
Posted: Mon Oct 12, 2009 4:58 am Post subject: |
|
|
Novice
Joined: 11 Jan 2009 Posts: 21
|
Problem is with your DSN. Have you configured a ODBC with associated Data Source? |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Oct 12, 2009 5:21 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Also, creating a user Trace of the message that passes through the flow will show far more information about the problem.
If you get one (the formatted output not the .xml) and extract the relevant bits and post them here you will get (i hope) more explanations as to the cause of the problem. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
veera_clr |
Posted: Mon Oct 12, 2009 5:41 am Post subject: |
|
|
Novice
Joined: 12 Oct 2009 Posts: 17
|
Yes i have created ODBC. I am using Database Route node for routing. It is expecting JDBCConnection. For that I have run the command as follows for setting the configurable services.
1. mqsicreateconfigurableservice SMPLBRK -c JDBCProviders -o DB2EXTRA -n DB2 -v "jdbc:db2://'SMPLDB':50000/SMPLDB:user=db2admin;password=db2admin;"
2. mqsireportproperties SMPLBRK -c JDBCProviders -o D
B2EXTRA -r
JDBCProviders
DB2EXTRA
connectionUrlFormat='jdbc:db2://SMPLDB:50000/SMPLDB:user=db2admin;password=d
b2admin;'
connectionUrlFormatAttr1=''
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='default_Database_Name'
databaseType='default_Database_Type'
databaseVersion='default_Database_Version'
description='default_Description'
jarsURL='default_Path'
portNumber='default_Port_Number'
securityIdentity='default_User@default_Server'
serverName='default_Database_Server_Name'
type4DatasourceClassName='default_Type_Four_Datasource_Class_Name'
type4DriverClassName='default_Type_Four_Driver_Class_Name'
BIP8071I: Successful command completion.
Still in trace i am getting this comment
3. Still it is giving the exception as follows.
There was a problem establishing a connection to the given database URL: 'jdbc:db2://default_Database_Server_Name:50000/default_Database_Name:user=********;password=********;' Exception details: ' error message: Unknown server default_Database_Server_Name, vendor's error code: -99999, stack trace: [com.ibm.db2.jcc.a.a.<init>(a.java:134)
Still I am not able to understand.
Could you please find these 3 points and do need ful. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Oct 12, 2009 5:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
DO NOT CHANGE THE connectionUrlFormat
EVER
DO NOT CHANGE THIS.
RESTORE IT TO WHAT IT WAS.
PUT YOUR VALUES IN the other properties.
Broker will replace them in the connectionURLFormat for you. |
|
Back to top |
|
 |
stallin |
Posted: Mon Oct 12, 2009 6:17 am Post subject: |
|
|
Novice
Joined: 11 Jan 2009 Posts: 21
|
What is SMPLDB in SMPLDB:50000? SMPLDB should be the m/c name or URL or if same m/c localhost. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Oct 12, 2009 6:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Looking at it again, every last bit of the JDBCProvider configuration is entirely wrong.
veera_clr, start over. Start with the sample *DB2* jdbc provider, and edit *only* the fields that have your specific informatoin. |
|
Back to top |
|
 |
veera_clr |
Posted: Tue Oct 13, 2009 3:10 am Post subject: |
|
|
Novice
Joined: 12 Oct 2009 Posts: 17
|
Hi,
I have changed as you mentioned by setting only required things and tested. Still i am facing the same issue.
Please find below and suggest me,
mqsireportproperties VEERABRK -c JDBCProviders -o DB2 -r
JDBCProviders
DB2
connectionUrlFormat='jdbc:db2://[serverName]:[portNumber]/[databaseName]:user=[user];password=[password];'
connectionUrlFormatAttr1=''
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='SMPLDB'
databaseType='DB2 Universal Database'
databaseVersion='8.2'
description='default_Description'
jarsURL='C:\Program Files\IBM\SQLLIB\java'
portNumber='50000'
securityIdentity='default_User@default_Server'
serverName='localhost'
type4DatasourceClassName='com.ibm.db2.jcc.DB2XADataSource'
type4DriverClassName='com.ibm.db2.jcc.DB2Driver'
Thanks,
Veera |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Oct 13, 2009 3:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Is the database local, or remote? Is it listening on that port? If it is remote, is it cataloged? |
|
Back to top |
|
 |
veera_clr |
Posted: Tue Oct 13, 2009 4:30 am Post subject: |
|
|
Novice
Joined: 12 Oct 2009 Posts: 17
|
Hi,
Thanks for reply.
Database is running on the local machine. I am not sure weather that is running on that port or not. how can i see the port number for that database.
Thanks,
Veera |
|
Back to top |
|
 |
Vitor |
Posted: Tue Oct 13, 2009 6:50 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
veera_clr wrote: |
how can i see the port number for that database.
|
Check the database properties. If uncertain how to do this, check the database documentation. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|