| Author |
Message
|
| shalabh1976 |
 Posted: Thu Sep 20, 2007 5:22 am Post subject: Phantom Execution Group problem |
 |
|
Partisan
Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India
|
I have already done a search on the forum and tried the possible solutions listed in the posts.
My problem is that the moment the Broker is started a DataFlowEngine is started even if no execution group is running.
Now when I deploy the flows a number of DataFlowEngines start depending on the number of execution groups.
I think this is not normal. As per my understanding the no. of DataFlowEngines = no. of execution groups running.
However my number is 1 greater.
Even after stopping/starting the broker/RAC the problem remains.
I even updated the BROKER database as shown in one of the posts on this issue.
However the problem remains.
My environment is MB 6 on Win XP Pro.
Any help is welcome
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Sep 20, 2007 5:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Can you tell what the name of the phantom EG is? Is it "sys_mqsi" or similar?
Or is it the same name as one of your existing and defined EGs?
The most drastic step here is to delete the entire broker and the entire configmgr, and start from scratch. But don't do that until you answer the above question/questions.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| shalabh1976 |
| Posted: Fri Sep 21, 2007 4:21 am Post subject: |
|
|
Partisan
Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India
|
Jeff,
| Quote: |
Can you tell what the name of the phantom EG is? Is it "sys_mqsi" or similar?
|
Name is temp
| Quote: |
| Or is it the same name as one of your existing and defined EGs? |
No.
| Quote: |
| The most drastic step here is to delete the entire broker and the entire configmgr, and start from scratch. |
I'll hold off on that
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 21, 2007 5:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So if the name of the EG is 'temp'... and there is no 'temp' in the configmgr... Then you can try the following.
Create a new EG named 'temp'. do a Full Deploy of the Topology.
stop and start Broker and ConfigMgr.
Delete the new EG named 'temp'. Do a full deploy of the Topology.
stop and start broker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| shalabh1976 |
| Posted: Sat Sep 22, 2007 3:05 am Post subject: |
|
|
Partisan
Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India
|
Jeff,
Tried what you said. However problem remains as now mqsibrowse shows two exec groups : default and other with no name(UUID is however listed).
Now I don't even know what exec group to delete.
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate |
|
| Back to top |
|
|
| Tonedef |
| Posted: Sat Sep 22, 2007 4:42 am Post subject: |
|
|
Apprentice
Joined: 05 Feb 2007
Posts: 44
|
Some instructions I have for removing phantom exe_grps on V5,
maybe you can mod them if you are on V6:
First we need to establish the UUIDs of the execution groups that the Configuration Manager believes are deployed to the broker. Run the following SQL when connected to the Configuration Manager database to do this:
SELECT E.CBROKERCUUID, B.CNAME, E.CUUID, E.CNAME FROM CBROKER AS B, CEG AS E WHERE B.CNAME = '<brokername>'
AND B.CUUID = E.CBROKERCUUID
AND B.CSECTION = 'DEPLED'
AND E.CSECTION = 'DEPLED'
This will produce a list of the broker's UUID and name, along with the UUIDs and names of the execution groups that are deployed to the broker.
The next step is to determine the execution groups that are actually running on the broker by browsing the entries in the BROKERAAEG table in the broker database, as follows:
mqsibrowse <brokername> -t BROKERAAEG > brokeraaeg.out
Now compare the entries in the brokeraaeg.out file against the output from the SELECT from the Configuration Manager table to determine the execution groups that are running in the broker that aren't reflected in the Configuration Manager database. These are the the candidates for deletion from the broker database.
Before proceeding to delete the execution groups from the broker database it is worth checking that there are no outstanding deploys from the Configuration Manager. To do this check the following:
1. There are no deploy messages on the SYSTEM.BROKER.ADMIN.QUEUE.
2. There are no deploy messages stuck on the transmission queue between the Configuration Manager's queue manager and the Broker's queue manager.
3. There are no outstanding deploys in the COUTSTANDING table in the Configuration Manager's database. Check this with the following SQL:
SELECT COUNT(*) FROM COUTSTANDING
If the count returned is greater than 0 then there are outstanding deploys which should be allowed to complete.
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.
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 without hyphens>'
AND ExecGroupUUID = x'<UUID of Execution Group 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. |
|
| Back to top |
|
|
| shalabh1976 |
| Posted: Sun Sep 23, 2007 8:32 pm Post subject: |
|
|
Partisan
Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India
|
After stopping the broker I opened the BROKERAAEG table and see only 1 entry with processstate=3 & dynamicstate=3.
So updating this with the same values as you show should have no effect.
| Quote: |
UPDATE BROKERAAEG
SET ProcessState=3, DynamicState=3
WHERE BrokerUUID= x'<UUID of Broker without hyphens>'
AND ExecGroupUUID = x'<UUID of Execution Group without hyphens>' |
Anyways I had already tried this before as this is mentioned in one of the previous posts on this issue.
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate |
|
| Back to top |
|
|
|
|
