|
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:25 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 |
|
 |
exerk |
Posted: Mon Jan 25, 2010 1:42 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Moving to the Broker forum...
Obvious question maybe, but - using a client, can you establish a connection to the database from the Broker server? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
mmahdi |
Posted: Mon Jan 25, 2010 2:31 am Post subject: |
|
|
Novice
Joined: 13 Feb 2007 Posts: 18
|
Yes exerk,
We tried that. It was succesful . Manually we were succesful to test that db connection. while starting the broker we encountered such errors.
Any idea ? |
|
Back to top |
|
 |
exerk |
Posted: Mon Jan 25, 2010 2:36 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
mmahdi wrote: |
Yes exerk,
We tried that. It was succesful . Manually we were succesful to test that db connection. while starting the broker we encountered such errors.
Any idea ? |
None from me I'm afraid, far too long since I've been anywhere near Broker. I can only suggest that you look HERE to see if there is relevance to your issue, or wait for someone knowledgeable to turn up  _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
vmcgloin |
Posted: Mon Jan 25, 2010 2:43 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002 Posts: 560 Location: Scotland
|
Just to confirm: the database is started and you tested the database connection on the same server with the same profile as used when starting the broker?
You need to identify what in the 'MQ recovery actions' taken caused the broker/database issue... so it might help to be more specific about those here? |
|
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
|
|
|
|