| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Database crashes, destroying broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| rmah |
 Posted: Fri Apr 11, 2008 9:55 am Post subject: Database crashes, destroying broker |
 |
|
Centurion
Joined: 04 May 2007
Posts: 142
|
Hi all,
If the broker internal database goes down or crashes, and the broker continues to run, does this mean end game for the broker?
We've noticed that nothing starts up and nothing deploys after an unplanned outage of the broker's internal database. Deployment freezes and flows do not listen on their queues.
After dropping the tables from the broker database (ORACLE), and rebuildilng the broker, we can deploy flows and they listen on their queues.
Thoughts?
Thanks!
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Apr 11, 2008 10:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If the database is mangled, yes, you have to assume you need to rebuild the broker.
If the database is recoverable, then you should be able to recover the broker.
Yes, while the database is unavailable you should assume that Broker will have issues - and shut it down as gracefully as you can. That doesn't mean you can't survive short periods of unavailability (and it depends on what featuers you are using, too)... but you shouldn't count on it.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
