| Author |
Message
|
| skol |
 Posted: Wed Dec 20, 2006 6:44 am Post subject: Phantom local execution groups |
 |
|
Apprentice
Joined: 05 Apr 2006
Posts: 38
|
I have three local execution groups running on my local development broker that don't show up in the toolkit, and one that does. I want to delete the three "phantom" EGs as the broker still runs them, and found the forum post that shows how to query the UUIDs of the groups from the BROKERAAEG table. But one step says - "Connect to the broker database as the broker service user ID". How do I do that on a local/development V6.0.0.2 windows broker installation? If someone can point me at doc for this I'd appreciate it. Once I get connected, the note has the UPDATE statements I need to run, which make sense, I just don't know what to use (program and credential) to get connected to the default local DB the installer set up.
Thanks in advance...
_________________
Steve |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Wed Dec 20, 2006 6:52 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Hmmm, are the phantom EGs there because you deleted them and they just haven't gone away yet?
They will hang around for a short period of time or go away on restart of the broker.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| skol |
| Posted: Wed Dec 20, 2006 7:02 am Post subject: |
|
|
Apprentice
Joined: 05 Apr 2006
Posts: 38
|
No, these have been around for months, and I'm finally trying to get rid of them after a long procrastination  The extra three DataFlowEngine processes are consuming virtual memory that is getting more valuable on my machine.
Do you know how I connect to the local database the installer set up?
_________________
Steve |
|
| Back to top |
|
|
| skol |
| Posted: Wed Dec 20, 2006 7:13 am Post subject: |
|
|
Apprentice
Joined: 05 Apr 2006
Posts: 38
|
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Dec 20, 2006 7:16 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Well if it is DB2, the DB2 Command Line processor.
Oracle, SqlPlus
There are other clients and other databases. What DB did you use for your broker? If it was Derby, then I don't know.
You can always remove the broker from the domain and delete it. Recreate it and add it again. Drastic, but it works. Could be quicker.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| skol |
| Posted: Wed Dec 20, 2006 7:21 am Post subject: |
|
|
Apprentice
Joined: 05 Apr 2006
Posts: 38
|
Yeah, I was hoping to avoid deleting the broker just for this.
I believe the installer lays down Derby by default, but am unsure. I have a JDBC tool for accessing it, but have no clue what credential to use, what derby's connect string looks like for this local install, and don't know where to look that up in the broker doc (if it exists).
Maybe nuking my Broker and creating a new one is the best bet, oh well.
Thanks for your help!
_________________
Steve |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Dec 20, 2006 7:33 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Hmmm, Windows makes it tricky. If it was UNIX, you would just look at the .odbc.ini file.
In the WMB Command prompt, try mqsiservice 'broker name'
It will list your broker DB. It is not Derby by default.
If you used the "Create default stuff", then it is DB2.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| skol |
| Posted: Wed Dec 20, 2006 7:44 am Post subject: |
|
|
Apprentice
Joined: 05 Apr 2006
Posts: 38
|
This is what comes back - I've done this before looking for the UUID and didn't even notice that there is a user and password right there:
BIPv600 en US
ucnv Console CCSID 437 dft ucnv CCSID 5348
OS windows-1252 ICUW ibm-5348_P100-1997 ICUA ibm-5348_P100-1997
Install Path = C:\Program Files\IBM\MQSI\6.0
Working Path = C:\Documents and Settings\All Users\Application Data\IBM\MQSI
Component UUID = 413ac68f-0a01-0000-0080-be965c8f05bc
process id = 7768
broker db name = WRKDB
broker db userId = IBMBroker
broker db password =
queue manager = QM_l05860
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
BIP8071I: Successful command completion.
But, how do you tell whether it is DB2 or Derby from this?
_________________
Steve |
|
| Back to top |
|
|
| skol |
| Posted: Wed Dec 20, 2006 7:49 am Post subject: |
|
|
Apprentice
Joined: 05 Apr 2006
Posts: 38
|
Well, just to try I got into my local DB2 command editor, and under all of my DB2 Connect databases I see WRKDB. So I must be DB2. But the connection dialog requires a password, and I can't tell if there is one for "IBMBroker". Closer....
_________________
Steve |
|
| Back to top |
|
|
| skol |
| Posted: Wed Dec 20, 2006 7:50 am Post subject: |
|
|
Apprentice
Joined: 05 Apr 2006
Posts: 38
|
I'm IN! It took any old password - so I'm all set. Thanks for your help!!
_________________
Steve |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Dec 20, 2006 7:53 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
There is one and I have no idea what it is. You can stop the broker. Change the password to the one you want.
mqsichangebroker to update the password.
check to see if the CM is also using the same ID on this machine, if so mqsichangecfgmanager to update the password there too.
Then restart and good to go.
Of course, if you are the DBA, then you don't need any password but yours.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 20, 2006 7:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I solved this same problem (on aix) by deleting the "real" EG from the toolkit, restarting broker, and recreating the EG.
I didn't have to play around with the database.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| skol |
| Posted: Wed Dec 20, 2006 7:58 am Post subject: |
|
|
Apprentice
Joined: 05 Apr 2006
Posts: 38
|
After all the above struggling, I just got done with the steps in the original thread, and it worked - I no longer have the three execution groups (three instances of DataFlowEngine.exe) that were only visble from the command line, not from the toolkit.
Thanks to all...
_________________
Steve |
|
| Back to top |
|
|
| gilbert |
| Posted: Thu Dec 21, 2006 12:41 am Post subject: |
|
|
Novice
Joined: 31 Oct 2006
Posts: 14
|
Skol: Do you have any clue what causes the execution groups to be created?
I've run to similar problem and it seems that phantom execution groups prevent debugger from working.
I've usually applied brute force tactics: delete and recreate broker. |
|
| Back to top |
|
|
| Edde |
| Posted: Thu Dec 21, 2006 9:31 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2006
Posts: 67
Location: Moscow, Russia
|
| gilbert wrote: |
Skol: Do you have any clue what causes the execution groups to be created?
I've run to similar problem and it seems that phantom execution groups prevent debugger from working.
I've usually applied brute force tactics: delete and recreate broker. |
One way to create a phantom EG is delete and recreate EG while channels between broker and CM are stopped.
I suppose there are other ways. |
|
| Back to top |
|
|
|
|
