| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2321E, BIP2322E and BIP2053E with Message Broker on HP-UX |
« View previous topic :: View next topic » |
| Author |
Message
|
| prk |
 Posted: Wed Mar 15, 2006 6:16 am Post subject: BIP2321E, BIP2322E and BIP2053E with Message Broker on HP-UX |
 |
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Here is our environment.
HP-UX 11i
Message Broker 6.0
MQ 5.3 CSD 09
The broker was up and running and suddenly stopped. Tried to restart but it comes up with this error shown below, where MYBROKER is the name of the broker having an issue.
Checked the .odbc.ini, database, restarted the databases and the Configmgr but still having an issue when trying to start the broker.
No issues connecting to the database with sqlplus.
Created a test broker on the same server and no issues with it. Trying to find out why this broker doesn't startup.
Any help is appreciated.
Mar 15 09:03:59 prh361 WebSphere Broker v6000[24171]: (MYBROKER)[1]BIP2321E: Database error: ODBC return code '-1'. : MYBROKER.agent: /build/S000_P/src/DataFlowEngine/ImbOdbc.cpp: 232: ImbOdbcHandle::checkRcInner: :
Mar 15 09:03:59 prh361 WebSphere Broker v6000[24171]: (MYBROKER)[1]BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '[DataDirect][ODBC lib] Data source name not found and no default driver specified'. : MYBROKER.agent: /build/S000_P/src/DataFlowEngine/ImbOdbc.cpp: 360: ImbOdbcHandle::checkRcInner: :
Mar 15 09:03:59 prh361 WebSphere Broker v6000[24171]: (MYBROKER)[1]BIP2053E: The broker made an unsuccessful attempt to access its database qbintb: MYBROKER.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 480: ImbAdminAgent::instanceOfAdminAgent: : |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Mar 15, 2006 6:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Double-check that the broker database user has not been expired, changed, or otherwise mangled.
Likewise, double-check that the broker database user's database permissions have not been mangled.
Enable database level tracing (work with your DBA) and watch what happens when the broker attempts to start up.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| prk |
| Posted: Wed Mar 15, 2006 7:30 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Thanks jefflowrey for the suggestions, did all that before but had no luck.
The issue has been finally resolved by issuing this command and giving the same databasename as before
Stopped the Broker and Configmgr and issued this command
mqsiservice <BrokerName> -r DataSourceName="DatabaseName"
Started the Broker and ConfigMgr and everything came back fine. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Mar 15, 2006 7:36 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
interesting, did you actually type this in:
| Code: |
mqsiservice MYBROKER -r DataSourceName=qbintb
|
or something else?
_________________
-wayne |
|
| Back to top |
|
|
| prk |
| Posted: Wed Mar 15, 2006 9:32 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
| Yes, you are right. The same thing. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
