| Author |
Message
|
| rkford11 |
 Posted: Tue Oct 26, 2004 2:21 pm Post subject: ODBC connection for Broker database |
 |
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
i know that this is not the place to ask this question but if anybody has a solution please reply.
I want to create an ODBC connection for the broker database and test it but when i do that it gives me an error
Specified ODBC driver could not be downloaded due to system error code 126 (IBM DB2 ODBC driver)
i created JDBC connection for configmgr database and i could create that but for broker we do need to have ODBC connection.
i checked the ODBC drivers and they are fine
Thanks |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Oct 26, 2004 4:17 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
To create an ODBC connection:
Start -> Settings -> Control Panel -> Administrative tools -> Data Sources (ODBC)
Goto SYSTEM DSN tab and Add your broker DB
If you are not asking this then you might reframe your question. |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Oct 26, 2004 5:07 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
If you are using DB2 as database then you can use DB2 Client Configuration Assistant to define ODBC connections.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| rkford11 |
| Posted: Wed Oct 27, 2004 5:37 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| kirani wrote: |
| If you are using DB2 as database then you can use DB2 Client Configuration Assistant to define ODBC connections. |
Thanks Kirani and Vennela. I have done what you have said, but after adding database when i test the connection it gives me an error saying
ODBC connection failed. Specified ODBC driver could not be downloaded due to system error code 126( IBM DB2 ODBC DRIVER).
Thanks |
|
| Back to top |
|
|
| waugh |
| Posted: Wed Oct 27, 2004 6:26 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
do you have DB2 client installed on that box?
do you have
C:\PROGRA~1\IBM\SQLLIB\BIN in your PATH variable?
to check, type in PATH on command prompt
you need DB2 client installed on that machine.... |
|
| Back to top |
|
|
| rkford11 |
| Posted: Wed Oct 27, 2004 7:33 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| waugh wrote: |
do you have DB2 client installed on that box?
do you have
C:\PROGRA~1\IBM\SQLLIB\BIN in your PATH variable?
to check, type in PATH on command prompt
you need DB2 client installed on that machine.... |
yes i do have DB2 client installed on that box. |
|
| Back to top |
|
|
| JT |
| Posted: Wed Oct 27, 2004 8:11 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| By chance, is there another error message being produced, maybe a BIP8040E error? |
|
| Back to top |
|
|
| rkford11 |
| Posted: Wed Oct 27, 2004 9:17 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| JT wrote: |
| By chance, is there another error message being produced, maybe a BIP8040E error? |
There is no such error. and i have not yet installed message broker. these ODBC connections that i am creating are for the configmgr and broker.
Thanks |
|
| Back to top |
|
|
| siliconfish |
| Posted: Wed Oct 27, 2004 11:29 am Post subject: |
|
|
Master
Joined: 12 Aug 2002
Posts: 203
Location: USA
|
This is an info I got from google in some forum (forgot to copy the link- closed the window) Hope this helps --
| Quote: |
Problem with loading ODBC IBM driver most definitely indicates an issue with your UDB DB2 client installation.
What type of client do you use, Development, Administrative or Runtime?
Make sure you are not using personal client edition.
Are you able to connect from the same workstation to any other version 7 UDB database?
Usually, the only one thing you should do when going from UDB client 8 to UDB Data Bases version 7 is to rebind all utilities (ODBC, CLI, Data Base, etc) from client 8 to the target DB you want to access. But before you can do so you should be able to connect without any problem. If you can’t establish a connection to any DB from the same workstation, then it’s definitely a client installation problem.
If you cannot connect just to version 7 UDB DB, then check your set up of catalog entries.
It also should not matter if you connecting to the database on UNIX or Z/OS or OS/390 MVS system. Proper catalog entries should be set up on your client workstation including DCS directory.
|
_________________
siliconfish |
|
| Back to top |
|
|
| waugh |
| Posted: Thu Oct 28, 2004 4:36 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
Rockford11,
do you see any errors in application log?
please post them here |
|
| Back to top |
|
|
| rkford11 |
| Posted: Thu Oct 28, 2004 5:57 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| waugh wrote: |
Rockford11,
do you see any errors in application log?
please post them here |
Waugh,
I dont find any errors in the application log, but in the system log it says DB2DAS - DB2DAS00 service hung on starting.
Now its more being a DB2 question, hope someone can help out.
Thanks |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Oct 28, 2004 7:01 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| I am not a DB2 person. If I get any DB2 errors, I would start off by stopping all the services and starting them top to down. |
|
| Back to top |
|
|
| waugh |
| Posted: Thu Oct 28, 2004 7:31 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
try what vennala suggested here if that dosnt help do a complete new install,
do mqsideleteconfigmgr
uninstall DB2
reboot
install DB2 |
|
| Back to top |
|
|
|
|
