| Author |
Message
|
| RNStanich |
 Posted: Thu Oct 02, 2008 4:31 am Post subject: Synchronization message when migrating to v6.1 |
 |
|
Acolyte
Joined: 23 Apr 2002
Posts: 64
|
Hi all, I'm in the process of testing a migration from WMB v6.0.0.3 to WMB v6.1.0.2. In two different scenarios; one being an install and creation of new configmgr and broker and one being an upgrade/migration of an existing server I'm receiving the below Windows event. BTW this is on Windows 2003.
( WMB6P_CONFIGMGR ) The Configuration Manager was unable to process a synchronization message
The Configuration Manager was unable to process a synchronization message from broker ''CCHUBP_BRKR''. This means that if the Configuration Manager and broker are reporting conflicting information, the Configuration Manager was not able to resolve the situation automatically. This may be due to an incorrectly formatted message from the broker, or it may suggest an error in the Configuration Manager repository.
Further information is available below. Review this information and if the problem cannot be resolved, contact your IBM support team for further assistance.
Has anyone seen anything similar or have any particular issues with a straightforward migration?
thanks...
_________________
Regards, Bob |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Oct 02, 2008 4:36 am Post subject: Re: Synchronization message when migrating to v6.1 |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| RNStanich wrote: |
| Further information is available below. |
What is the "further information" that would have been available below?
What steps did you take to perform the migration? |
|
| Back to top |
|
|
| RNStanich |
| Posted: Thu Oct 02, 2008 4:44 am Post subject: |
|
|
Acolyte
Joined: 23 Apr 2002
Posts: 64
|
Hi mqjeff. I believe the further information is just the normal stuff included in Windows events:
000: 34 00 38 00 32 00 34 00 4.8.2.4.
0008: 00 00 57 00 4d 00 42 00 ..W.M.B.
0010: 36 00 50 00 5f 00 43 00 6.P._.C.
0018: 4f 00 4e 00 46 00 49 00 O.N.F.I.
0020: 47 00 4d 00 47 00 52 00 G.M.G.R.
0028: 2e 00 61 00 67 00 65 00 ..a.g.e.
0030: 6e 00 74 00 00 00 46 00 n.t...F.
0038: 3a 00 5c 00 62 00 75 00 :.\.b.u.
0040: 69 00 6c 00 64 00 5c 00 i.l.d.\.
0048: 53 00 36 00 31 00 30 00 S.6.1.0.
0050: 5f 00 50 00 5c 00 73 00 _.P.\.s.
0058: 72 00 63 00 5c 00 44 00 r.c.\.D.
0060: 61 00 74 00 61 00 46 00 a.t.a.F.
0068: 6c 00 6f 00 77 00 45 00 l.o.w.E.
0070: 6e 00 67 00 69 00 6e 00 n.g.i.n.
0078: 65 00 5c 00 4e 00 61 00 e.\.N.a.
0080: 74 00 69 00 76 00 65 00 t.i.v.e.
0088: 54 00 72 00 61 00 63 00 T.r.a.c.
0090: 65 00 5c 00 49 00 6d 00 e.\.I.m.
0098: 62 00 4e 00 61 00 74 00 b.N.a.t.
00a0: 69 00 76 00 65 00 54 00 i.v.e.T.
00a8: 72 00 61 00 63 00 65 00 r.a.c.e.
00b0: 2e 00 63 00 70 00 70 00 ..c.p.p.
00b8: 00 00 37 00 33 00 39 00 ..7.3.9.
00c0: 00 00 72 00 65 00 62 00 ..r.e.b.
00c8: 75 00 69 00 6c 00 64 00 u.i.l.d.
00d0: 4d 00 65 00 73 00 73 00 M.e.s.s.
00d8: 61 00 67 00 65 00 46 00 a.g.e.F.
00e0: 6c 00 6f 00 77 00 49 00 l.o.w.I.
00e8: 6e 00 66 00 6f 00 72 00 n.f.o.r.
00f0: 6d 00 61 00 74 00 69 00 m.a.t.i.
00f8: 6f 00 6e 00 46 00 6f 00 o.n.F.o.
0100: 72 00 57 00 4d 00 42 00 r.W.M.B.
0108: 36 00 50 00 5f 00 43 00 6.P._.C.
0110: 4f 00 4e 00 46 00 49 00 O.N.F.I.
0118: 47 00 4d 00 47 00 52 00 G.M.G.R.
0120: 00 00 57 00 4d 00 42 00 ..W.M.B.
0128: 36 00 50 00 5f 00 43 00 6.P._.C.
0130: 4f 00 4e 00 46 00 49 00 O.N.F.I.
0138: 47 00 4d 00 47 00 52 00 G.M.G.R.
0140: 00 00 ..
Migration was by the book; stop both components, run the migrate command first with the -c and afterward with the -v. In both cases I was told the migration was successful. AND as I indicated one case was not a migration, but simply defining new v6.1 components. I am using a v6.0 bar file.
Also I am in touch with IBM but I was hoping someone encountered this issue and found their own solution.
_________________
Regards, Bob |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Thu Oct 02, 2008 5:10 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
Check that you have right command environment for version 6.1 components(when migrating and starting).
Check that you don't have orphan / chost flows runing on the brokers.
Marko |
|
| Back to top |
|
|
| RNStanich |
| Posted: Thu Oct 02, 2008 5:15 am Post subject: |
|
|
Acolyte
Joined: 23 Apr 2002
Posts: 64
|
Hi, definitely the correct command window; I was careful about that.
Broker is stopped during migration step; not sure what "orphan / chost flows" means...sorry
_________________
Regards, Bob |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Thu Oct 02, 2008 10:28 pm Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
For me orphan / ghost flows are flows that are hiding on the broker(database) and don't show themselves to configmgr. They can't also be administered any more through configmgr. mqsilist command shows them at least sometimes.
To find/remove them you can perhaps try to use "Remove Deployed Children" command
from Toolkit and then check from broker database is there any flows hiding
| Quote: |
just for an example:
db2 => select cast(resourcetype as varchar(36) for sbcs data), cast(resourcename
as varchar(36) for sbcs data) from brokerresources where cast(resourcetype as v
archar(36) for sbcs data) = 'MessageFlow'
1 2
------------------------------------ ------------------------------------
MessageFlow 25a10d9b-1c01-0000-0080-ed10ea47e6e3
MessageFlow bf5e229e-1c01-0000-0080-d05ee2de71a7
2 record(s) selected.
RDC command from toolkit
db2 => select cast(resourcetype as varchar(36) for sbcs data), cast(resourcename
as varchar(36) for sbcs data) from brokerresources where cast(resourcetype as v
archar(36) for sbcs data) = 'MessageFlow'
1 2
------------------------------------ ------------------------------------
0 record(s) selected.
|
and if there is ask from IBM how to solve the situation. Or perhaps you need to do something more advanced to find them.
Marko |
|
| Back to top |
|
|
| RNStanich |
| Posted: Fri Oct 03, 2008 4:04 am Post subject: |
|
|
Acolyte
Joined: 23 Apr 2002
Posts: 64
|
Thank you, I'll give that a try.
_________________
Regards, Bob |
|
| Back to top |
|
|
|
|
