| Author |
Message
|
| relheop |
 Posted: Sun Feb 03, 2008 11:36 am Post subject: Restore WMB broker database db2 after failure. |
 |
|
Apprentice
Joined: 30 Jan 2003
Posts: 40
|
Hallo @,
We have one scenario: Broker database crashed and we would like to restore database without deleting the current broker database and WMB broker.
Which is the best way to rebuild the environment to the current state? Is it possible to rebuild broker database from the “db2 [b]online[/b]” backup? I found information in IBM books only for creating new broker database or restoring database from “Offline” db2 backup.
We tried to rebuild from “db2 online” backup with forward recovery but the environment is not consistent. mqsilist delivers not the same count of execution groups or some execution groups are empty.
Any ideas?
[/b] |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sun Feb 03, 2008 4:10 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can redeploy your stuff without "deleting the broker or the broker database".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| relheop |
| Posted: Mon Feb 04, 2008 10:23 am Post subject: |
|
|
Apprentice
Joined: 30 Jan 2003
Posts: 40
|
| Can you describe the way to recover broker database from DB2 online backup? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Feb 04, 2008 10:52 am Post subject: Re: Restore WMB broker database db2 after failure. |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| relheop wrote: |
| Which is the best way to rebuild the environment to the current state? |
You're always at your current state, there's nothing to do 
What happens when you deploy to this broker? If that works, the best and easiest way to get yourself back to the last working state is to just redeploy all your bar files.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Feb 04, 2008 11:14 pm Post subject: In situations like this |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
It is almost always quicker to do the following:-
1) delete errant broker from config
2) drop DB2 Database
3) re-create the database ( you do have a script to do this don't you?)
4) recreate the Broker ( using a script )
5) deploy everything again ( using more scripts )
I had to do this recently on a production server where a DBA (???? ) forgot which DB he was using and really messed up the broker DB.
Luckily, all the above steps were scripted and the broker was rebuilt and back in service in less than 20mins. No SLA's were breached and everyone was happy. The DBA had to dig deep into his pockets to fund the beer that evening.  
_________________
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 |
|
|
| jefflowrey |
| Posted: Tue Feb 05, 2008 4:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If the broker is functioning, it's quicker to redeploy everything (from scripts) than to delete the broker and recreate it - including removing it from configmgr in the proper order.
It's safer to recreate the broker from scripts, I agree.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
