| Author |
Message
|
| chetu777 |
 Posted: Sun Oct 11, 2009 9:27 pm Post subject: Problem with old execution group? |
 |
|
Acolyte
Joined: 07 Sep 2009
Posts: 59
|
Hey guys I am in a sort of trouble
First of all my MB version is 5 with CSD 08
I had a configuration Manager running on a windows machine and broker on AIX 5.2. I had done some deployment into the broker execution group, due to some problem with the configuration manager I ahd to delete that configuration manager and recreate it using new config DB and new Config QM.
The problem now is those flows I had deployed previously with older config is still running and when new domain connection is done in toolkit and when broker is added to the topology I am not able to view any execution group or flows running through toolkit. I am able to see only default execution group.
My Q is
1) How to remove the old execution group and its children?
2) Is that when we create a new config mgr and then add any old broker doesnt it show its previously deployed message flows?
3) Now how can I go about to redeploy new flows in those previous execution groups?
I tried using the command mqsideleteexecutiongroup , but it is of no use because it needs the old config manager details which is deleted now.
Can anyone help me out? |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sun Oct 11, 2009 10:43 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I think you are up the creek without a paddle here.
From what I can remember about V5, you are stuck.
IMHO, you are going to have to delere the broker and re-create everything from scratch.
If you have scripts, this should only take a few minutes (not including Flow deployment).
_________________
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 |
|
|
| Gaya3 |
| Posted: Mon Oct 12, 2009 1:19 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
|
| Back to top |
|
|
| chetu777 |
| Posted: Mon Oct 12, 2009 1:32 am Post subject: |
|
|
Acolyte
Joined: 07 Sep 2009
Posts: 59
|
| no its not the same issue, this issue proped up only when I changed the UUID in CBROKER table of Config manager database. Not I am not able to add or cancel and deployment. This error props up |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Oct 12, 2009 2:05 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
A ministers say in the house of commons when answering questions,
"Please refer to my previous reply" (in this thread)
you have obviously tried to sidestep the issue but what you are doing is, well, you are on your own. I did the same years ago and eventually common sense prevailed and I recreated the Broker and Configmgr from scripts. Only took a few minutes and aroud 10 to deploy everything.
_________________
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 |
|
|
| chetu777 |
| Posted: Mon Oct 12, 2009 2:25 am Post subject: |
|
|
Acolyte
Joined: 07 Sep 2009
Posts: 59
|
Hey just was about to reply the same thing buddy,
Actually I didnt wanted to run away from the issue so was tryin to solve and go ahead. Got bugged up so much that finally delted everything, ran the scripts, created new Config DB, QM and everything and now its working perfectly fine.
Well thanks for all those who tried to help me  |
|
| Back to top |
|
|
|
|
