| Author |
Message
|
| Guava72 |
 Posted: Wed May 26, 2004 6:36 pm Post subject: broker cannot connect to its database |
 |
|
Apprentice
Joined: 06 Jun 2003
Posts: 46
Location: Champaign, IL
|
Hi, we are using WMQI 2.1 CSD05 on AIX 4.3
DB2 was just upgraded from 7.1 to 7.2 CSD05.
But now the brokers will not start, although DB2 instance appears to be running. Can anyone help me? This is a show-stopper for 4 UAT and testing environments...
| Code: |
May 26 21:33:37 vadnxuwfl WMQIv210[89882]: (FRMTITV)[1]BIP2048E: An Exception was caught while issuing database SQL command connect. : FRMTITV.agent: /build/S210_P/src/AdminAgent/ImbAdminStore.cpp: 255: ImbAdminStore::Connect: :
May 26 21:33:37 vadnxuwfl WMQIv210[89882]: (FRMTITV)[1]BIP2321E: Database error: ODBC return code '-1'. : FRMTITV.agent: /build/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 152: ImbOdbcHandle::checkRcInner: :
May 26 21:33:37 vadnxuwfl WMQIv210[89882]: (FRMTITV)[1]BIP2322E: Database error: SQL State 'S1000'; Native Error Code '-1001'; Error Text ''.: FRMTITV.agent: /build/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 252: ImbOdbcHandle::checkRcInner: :
May 26 21:33:37 vadnxuwfl WMQIv210[89882]: (FRMTITV)[1]BIP2322E: Database error: SQL State '01000'; Native Error Code '364'; Error Text 'The driver returned invalid (or failed to return) SQL_DRIVER_ODBC_VER: '. : FRMTITV.agent: /build/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 252: ImbOdbcHandle::checkRcInner: :
May 26 21:33:37 vadnxuwfl WMQIv210[89882]: (FRMTITV)[1]BIP2053E: The broker made an unsuccessful attempt to access its database BKDBITV with userid db2inst1. : FRMTITV.agent: /build/S210_P/src/AdminAgent/ImbAdminAgent.cpp: 440: ImbAdminAgent::instanceOfAdminAgent: :
|
|
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed May 26, 2004 6:40 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
DB2 itself might be logging more information about what's going on...
Also, are you using globally coordinated transactions?
If so, it might not hurt to recompile or reinstall the db2 switch file to the broker/queue manager.
But I'd double-check that it's not a permissions problem first.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JT |
| Posted: Wed May 26, 2004 7:30 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
You can also capture some database information from your broker server by activating the odbc trace within your .odbc.ini file.
| Quote: |
[ODBC]
Trace=1
TraceFile=/var/wmqi/odbc/odbctrace.out
TraceDll=/usr/opt/wmqi/merant/lib/odbctrac.so
InstallDir=/usr/opt/wmqi/merant
|
Review the odbctrace.out file for details of your problem. |
|
| Back to top |
|
|
| Nick Lethbridge |
| Posted: Thu May 27, 2004 3:51 am Post subject: |
|
|
Voyager
Joined: 13 Aug 2001
Posts: 88
Location: Santander, UK
|
| You might also want to read the "Merant driver updates" section of the memo.ptf file - are you pointing at the correct DB2 driver (libdb2.a) ? |
|
| Back to top |
|
|
| Guava72 |
| Posted: Sat May 29, 2004 11:47 am Post subject: [solved] broker can't connect to its database |
|
|
Apprentice
Joined: 06 Jun 2003
Posts: 46
Location: Champaign, IL
|
| Thanks Nick and everyone who responded! The problem was, in fact, due to the wrong DB2 driver name in the .odbc.ini file. We fixed this and the brokers started right up with no problem. Thanks again!! |
|
| Back to top |
|
|
|
|
