| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configmgr shows no flows deployed |
« View previous topic :: View next topic » |
| Author |
Message
|
| williad |
 Posted: Mon Nov 09, 2009 5:41 am Post subject: Configmgr shows no flows deployed |
 |
|
Apprentice
Joined: 08 Sep 2005
Posts: 40
Location: London
|
HI
we are running wmq 6.0.2.6 and wmb6103 on a sun solaris 10 broker
We have a oracle database that contains the wmb61 broker tables in a schema called wmb_dmh_brkr. There are 2 other schemas in this database, one used by another application, the other schema contains application data used by the message flows.
What we have done is to export out the wmb_dmh_brkr schema, and then restored the whole database from a previous month ago backup. We have then re-imported the wmb_dmh_brkr schema back into the database, so that the broker tables are back and in synch with our configuration manager.
But when we started up the configmgr we started getting messages as shown below, and it with messages about removing the message flows:
Nov 9 10:45:01 ts2dmh-mid WebSphere Broker v6103[3268]: [ID 702911 user.info] (ts2configmgr)[31]BIP1583W: The Configuration
Manager has discovered message flow 'Pace_Fundworks_Security_Rating' on broker 'TS2LNB01'. The message flow unique identifier is '7
f4f0e49-2401-0000-0080-b9820274d11e'; the execution group unique identifier is '5e1ee524-2401-0000-0080-99d919cbd90e'. : ts2configmg
r.agent: /build/S610_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: addMessageFlow: ts2configmgr: ts2configmgr
Nov 9 10:45:31 ts2dmh-mid WebSphere Broker v6103[3268]: [ID 702911 user.info] (ts2configmgr)[31]BIP1583W: The Configuration
Manager has discovered message flow 'SILMA_GFP_Export' on broker 'TS2LNB01'. The message flow unique identifier is '4ea742c4-2401-0
000-0080-db6bd25bca83'; the execution group unique identifier is '650edf24-2401-0000-0080-99d919cbd90e'. : ts2configmgr.agent: /buil
d/S610_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: addMessageFlow: ts2configmgr: ts2configmgr
when we look at the configmgr via the toolkit, all our execution groups have gone and been renamed to ExecutionGroup, but there are no flows deployed.
When we look at the broker using mqslist, all the execution groups and their flows are still there running.
Does anyone know why the configmr behaved like this by removing all the flows and renaming the execution groups? and is there a way of resynching the configmgr back from the broker?
Thanking you again for your help |
|
| Back to top |
|
 |
| williad |
| Posted: Fri Nov 13, 2009 2:42 am Post subject: |
|
|
Apprentice
Joined: 08 Sep 2005
Posts: 40
Location: London
|
Hi
appologies for not getting back
but we solved this problem
what happened was that we stopped broker, and then exported the broker database schema from the oracle database, and then restored the whole database back from a month old or so backup.
becuase our broker is controlled via VCS. one of our unix admin saw that the broker was down, and so started it. This then made the configmgr see the broker, and hence the internal flow ids etc were out of synch, and therefore the configmgr removed the flows and execution groups from it database. and therefore our toolkits showed no proper named execution group and no flows deployed
we managed to get the configmgr back in sync with the database, by re-importing the exported schema, and getting a backup restore of the configmgr BERNARD directory of when we first stopped the broker.
I have also been told that there is a way to resync the configmgr from the broker. but i dont know how t o do it that way.
so all is good. 
I hope this makes sense 
Thank you all |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
