| Author |
Message
|
| rajasri |
 Posted: Wed Jun 14, 2006 11:51 pm Post subject: regarding execution-groups |
 |
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
| Hi IBM'ers, I am facing problem with execution groups. I heard that the Number of DataFlowEmgine services running is equal to the number of Excution Groups in th broker. Even though I had 3 execution groups, i removed one, and now i have only two. but the number of data flow engines are shown to be 3. it is giving me some problems frequently. Like, when a message is put ina queue, the expected output is going to a Queue which WAS related to the deleted execution group. And some times it goes to the correct outptqueue . So now i want to delete the dataflow engine. but iam not able to that. tried many ways, restating broker, ConfigMgr, Computer. Nothing works. Help plz |
|
| Back to top |
|
 |
| edarasumanth |
| Posted: Thu Jun 15, 2006 1:20 am Post subject: Restart the Agent Controller Service |
|
|
Novice
Joined: 15 Jun 2006
Posts: 21
|
| Restart the Agent Controller Service |
|
| Back to top |
|
|
| rajasri |
| Posted: Thu Jun 15, 2006 1:48 am Post subject: execution group |
|
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Jun 15, 2006 2:09 am Post subject: Re: regarding execution-groups |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi rajasri,
| rajasri wrote: |
| Hi IBM'ers, |
Not all IBMers here....avoid asking specific people 
| rajasri wrote: |
| Even though I had 3 execution groups, i removed one, and now i have only two. but the number of data flow engines are shown to be 3. it is giving me some problems frequently. Like, when a message is put ina queue, the expected output is going to a Queue which WAS related to the deleted execution group. And some times it goes to the correct outptqueue . So now i want to delete the dataflow engine. but iam not able to that. tried many ways, restating broker, ConfigMgr, Computer. Nothing works. Help plz |
Usually the problem should not occur...even when it does a restart of the system fixes it...if it still exists you better do the mqsilist on the broker and check the execution groups...maybe it did not delete properly...
Else last resort, you can delete the row from the database.
Regards. |
|
| Back to top |
|
|
| edarasumanth |
| Posted: Thu Jun 15, 2006 2:47 am Post subject: |
|
|
Novice
Joined: 15 Jun 2006
Posts: 21
|
What Elvis suggested is the exact action to be performed.
No of Execution groups that are present in the Broker topology should be equal to the no of flow engines.
u had mentioned that u had deleted one of the execution group. but u r seeing the flow engine related to that broker.
Agentcontroller service belongs to the debugger perspective.
when u r adding the mesage flows to the debugger perspective u can see the flowengines related to the brokers present in the broker topology.
once u r restarting that service that flow engine sometimes disappears.
while restarting the service close the tool kit. stop all the brokers and perform the action.
just try issuing the mqsilist command. |
|
| Back to top |
|
|
| rajasri |
| Posted: Thu Jun 15, 2006 3:02 am Post subject: Execution Group |
|
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
| Hi all, I have isued the command mqsilist brokername, and it shows me the deleted execution group also. then i stopped the broker, closed the tool kit and restarted the AgentController. But the problem still persists, there are still 3 dataflowengines. And, what is the table which has this list of execution groups. i tried to find that but there are many tables. And is there any command to delete the Exe group from the command console. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Jun 15, 2006 3:13 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
|
| Back to top |
|
|
| rajasri |
| Posted: Thu Jun 15, 2006 3:24 am Post subject: execution group |
|
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
| Hi Elvis, the page u referred has beeen removed i guess. Iam not able to view it. i even gave a search in the forum. all the pages related to execution group are expired. |
|
| Back to top |
|
|
| edarasumanth |
| Posted: Thu Jun 15, 2006 3:24 am Post subject: |
|
|
Novice
Joined: 15 Jun 2006
Posts: 21
|
Hai
Before going to issue this command start your configuration manager.
This is the command for deleting the execution group
mqsideleteexecutiongroup -b brokername -e executiongroupname -q queuemanagername -v tracefilename
here brokername and execution group name are mandatory for this command |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 15, 2006 3:36 am Post subject: Re: execution group |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rajasri wrote: |
| Hi Elvis, the page u referred has beeen removed i guess. Iam not able to view it. i even gave a search in the forum. all the pages related to execution group are expired. |
I can view the link no problem - likewise the search popped up some stuff! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Jun 15, 2006 3:50 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi rajasri,
| Quote: |
We have the same Problem with Broker V.6 and IBM gave us the following answer upon our request.
-------------------------------------------
Once it has been verified that there are no outstanding deploys the 'rogue' execution groups can be removed from the broker database with the following SQL. Please note, it is strongly recommended that the broker is stopped and the broker database is backed up prior to manually updating database records.
0. mqsiservice <BROKER_NAME>
So you get the UUID of the broker.
With ...
mqsibrowse <BROKER_NAME> -t BROKERAAEG > c:\brokeraaeg.out
... you can get the UUID of the EG(s), which you want to remove.
1. Stop the broker if it is not already stopped.
2. Connect to the broker database as the broker service user ID.
3. Depending on the RDBMS that's used for the broker database, run the following SQL to remove each rogue execution group.
a) DB2 Broker Database
UPDATE BROKERAAEG SET ProcessState=3, DynamicState=3 WHERE BrokerUUID= x'<UUID of Broker in uppercase without hyphens>' AND ExecGroupUUID = x'<UUID of Execution Group in uppercase without hyphens>'
b) Oracle Broker Database
UPDATE BROKERAAEG
SET ProcessState=3, DynamicState=3
WHERE BrokerUUID= '<UUID of Broker in uppercase without hyphens>' AND ExecGroupUUID = '<UUID of Execution Group in uppercase without
hyphens>'
4. Restart the broker and ensure that the number of execution groups that are started reflects the number of execution groups that are displayed in the Tooling. |
Talk about spoon-feeding 
Regards. |
|
| Back to top |
|
|
|
|
