| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| broker database migration |
« View previous topic :: View next topic » |
| Author |
Message
|
| mrgate |
 Posted: Mon Apr 26, 2010 12:50 am Post subject: broker database migration |
 |
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
Hi All, in ours production environment we are having WMB 6.1.0.4,WMQ 7.0.0.1 , DB2 v8.1.1.160. we need to migrate db2 database from ours existing server to a new server and mb,mq will remain same on existing server. we are replacing db2 server with db2 client in local server and cataloging remote database in the machine where wmb was installed. so ours brokers database is a remote database.
May I know during this migration do we need to reinstall the existing broker component or just cataloing the remote database is enough. the new and existing database names will be same.
_________________
MQSeries terrorist |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Apr 26, 2010 2:44 am Post subject: Re: broker database migration |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
| mrgate wrote: |
Hi All, in ours production environment we are having WMB 6.1.0.4,WMQ 7.0.0.1 , DB2 v8.1.1.160. we need to migrate db2 database from ours existing server to a new server and mb,mq will remain same on existing server. we are replacing db2 server with db2 client in local server and cataloging remote database in the machine where wmb was installed. so ours brokers database is a remote database.
May I know during this migration do we need to reinstall the existing broker component or just cataloing the remote database is enough. the new and existing database names will be same. |
You do realize that you are introducing another point of failure to the broker.
When the communication between the broker and the DB is broken you can see strange behavior appearing on the broker.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mrgate |
| Posted: Mon Apr 26, 2010 3:15 am Post subject: Re: broker database migration |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
| fjb_saper wrote: |
You do realize that you are introducing another point of failure to the broker.
When the communication between the broker and the DB is broken you can see strange behavior appearing on the broker.
Have fun |
Hi, thanks for a very good response. we will work on the same. But, we need to know whether the broker component is to be removed or not.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Apr 26, 2010 4:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You should not need to do anything other than stop the broker and start the broker.
The broker will need to be fully stopped while the database is being migrated and the client is being installed and configured, and then start the broker after you have fully tested the database connectivity. |
|
| Back to top |
|
|
| mrgate |
| Posted: Mon Apr 26, 2010 9:06 pm Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
| mqjeff wrote: |
You should not need to do anything other than stop the broker and start the broker.
The broker will need to be fully stopped while the database is being migrated and the client is being installed and configured, and then start the broker after you have fully tested the database connectivity. |
Thanks mqjeff for a valid reason. Your's post is a valid point when we are migrating(taking backup on local machine and restoring on remote machine). I think if we did not take a backup,removed the database and a new database on the remote server will cause an issue as we are not going to have brokers repository information.
_________________
MQSeries terrorist |
|
| 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
|
|
|
|
