| Author |
Message
|
| rcrippen |
 Posted: Tue Jul 06, 2004 11:30 am Post subject: Self-inflicted wounds migrating to v5 |
 |
|
Apprentice
Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY
|
I know this has been done before, but I can't find any reference to the solution on this board.
We didn't follow the appropriate steps to migrate one of our servers from MQSI Version 2.1 to WBIMB V5 and have know totally snafu-ed the server. The symptoms are WebSphere MQ, a new V5 configmgr and a new V5 broker services will not start up on the windows 2000 server after a migration to WBIMB V5.
The steps perfomed were
Uninstall DB2 V7.1 (did not save the tables)
Uninstall MQSI V2.1 (did not delete the brokers)
install DB2 V8.1
Install WBIMB V5
Upgraded to CSD06 for WebSphere MQ V5.3
Created configmgr and broker Databases in DB2 V8.1 as well as new ODBC instances.
created configmgr and broker in WBIMB V5
The V2.1 broker service is still listed in the windows services and is dependant on WebSphere MQ.
When we try to start up WMQ, we get a 'dependancy marked for deletion' error and the startup fails.
Can anyone recommend a painless (as possible) way to remove the dependancies between WMQ and WBIMB in windows services?
Our initial thought was to uninstall everything and start over, but I don't think that will get rid of the V2.1 broker, will it?
One more thing, the WebSphere MQ service has a dependancy of DB2 Security Server. Is that normal or did that happen when DB2 V8.1 was installed?
Any help would be appreciated.
Rob |
|
| Back to top |
|
 |
| Rockon |
| Posted: Tue Jul 06, 2004 1:56 pm Post subject: removing a windows service |
|
|
Apprentice
Joined: 24 May 2004
Posts: 43
|
[quote]Can anyone recommend a painless (as possible) way to remove the dependancies between WMQ and WBIMB in windows services?[/quote]
1.run regedit
2.goto HKEYLocalMachine/System/CurrentControlSet/Services
3.Find ur Service and check if the file it is dependent on still exist .....get rid of the file and then the service
reboot ur machine |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 06, 2004 2:04 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You could try mqsideletebroker...
I won't guarantee it will succeed, though.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rcrippen |
| Posted: Wed Jul 07, 2004 4:08 am Post subject: |
|
|
Apprentice
Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY
|
Rockon:
Thanks, that did allow us to remove the old Broker service, now the only issue is the db2 Security Service dependancy for WMQ. We are thinking that since we installed a new version of DB2, the WMQ service is 'confused' as to where the dependancy exists and/or doesn't think that it is started yet. We will continue to pursue this line.
Jeff:
Thanks for your response also, yes you were right, it did not work, I couldn't delete the broker because the config mgr database was already gone.
Rob |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jul 07, 2004 5:12 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| I couldn't delete the broker because the config mgr database was already gone. |
What has config mgr database got to do with creating/deleting a broker?
Maybe you were not able to delete it but it should be because of some other reason I guess |
|
| Back to top |
|
|
| rcrippen |
| Posted: Wed Jul 07, 2004 5:19 am Post subject: |
|
|
Apprentice
Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY
|
Vennela:
I guess what I meant to say was I believe the reason that I couldn't delete the broker was because the DB2 V7.1 instance was removed without deleting the broker first. When I tried to delete the broker after installing DB2 V8.1, the broker database could not be found since it didn't exist in the new database instance. Actually, the ODBC instance that the delete command was trying to use did not point to any database.
Thanks,
Rob |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jul 07, 2004 5:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you try mqsideletebroker with the "preserve tables" options?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rcrippen |
| Posted: Wed Jul 07, 2004 5:32 am Post subject: |
|
|
Apprentice
Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY
|
Jeff,
No, didn't try that, probably would have worked though!
We have found out why the WMQ service will not start......Since MQ Workflow is also installed and configured on this server, the dependancy between WMQ and DB2 Sec Service was due to the 2phase commit for Workflow. Since we had already removed the Workflow DB2 tables also, we have removed the Workflow configurations and are doing to uninstall Workflow to get the dependancy removed.
Thanks for all your help.
Rob |
|
| Back to top |
|
|
|
|
