| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2013E: The broker was unable to access its database. |
« View previous topic :: View next topic » |
| Author |
Message
|
| mmahdi |
 Posted: Mon Jan 25, 2010 1:45 am Post subject: BIP2013E: The broker was unable to access its database. |
 |
|
Novice
Joined: 13 Feb 2007
Posts: 18
|
Hi All,
i am unable to start the broker and able to see the following error :
Jan 24 18:03:01 prodser1 WebSphere Broker v6009[25496]: [ID 702911 user.error] (PRD.BROKER)[1]BIP2013E: The broker was unable to access its database. : PRD.BROKER.service: /build/S600_P/src/AdminAgent/ControlProcess/Solaris/ImbControlService.cpp: 406: ImbControlService::GetAAexitCode: :
The above error was encountered after a major upgrade ativity on our production servers. The upgrade activity included in sequence :
1) MQ upgrade (from v5 to v6)
2) MB upgrade (from v5 to v6009)
3) Oracle upgrade (from 9i to 10g)
After succesful oracle upgrade, we started the brokers, they were fine and running. Suddenly after couple of minutes, Mountpoint for MQ went 100 % and Alias Queues and channels were corrupted and hence we started MQ activities to make the alias queues and channels functioning fine. Afther succesful MQ activity, when we retried to start the broker, and then we encountered the error as :
Jan 24 18:03:01 prodser1 WebSphere Broker v6009[25496]: [ID 702911 user.error] (PRD.BROKER)[1]BIP2013E: The broker was unable to access its database. : PRD.BROKER.service: /build/S600_P/src/AdminAgent/ControlProcess/Solaris/ImbControlService.cpp: 406: ImbControlService::GetAAexitCode: :
Latest Environment details :
Messsage broker Version: 6009
Database : Oracle 10g
OS : Solaris
Can anyone please advice on the same ?
This is a production issue and needs to be resolved at the earliest ?
Thanks in Advance
Mahdi Mithani
Tech Mahindra |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Jan 25, 2010 3:34 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
ODBC Definitions?
Have you checked that the .so files referenced exist?
_________________
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 |
|
|
| mqjeff |
| Posted: Mon Jan 25, 2010 3:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There's usually another BIP that goes with that 2013 that would have the DB error, as well.
The first suspect in all database issues is user credentials - it's easiest to verify and resolve and thus eliminate. So confirm the broker database user exists in the new Oracle 10g and is authorized to what it needs to be. |
|
| 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
|
|
|
|
