ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Loss message set after upgrade MQSI from 2.0.2 to 2.1

Post new topic  Reply to topic
 Loss message set after upgrade MQSI from 2.0.2 to 2.1 « View previous topic :: View next topic » 
Author Message
caroljx
PostPosted: Tue Apr 06, 2004 8:40 am    Post subject: Loss message set after upgrade MQSI from 2.0.2 to 2.1 Reply with quote

Newbie

Joined: 06 Apr 2004
Posts: 5
Location: Calgary, AB Canada

We are currently running on AIX 5.1+ML3, MQSeries 5.3.0.1, DB2 7.1.0.40.

We upgraded our MQSI from 2.0.2 to 2.1 but when the developers did test after upgrading, their application didn't work. We found error message in syslog.user:
-------------------------------------------------------------------------------
WMQIv210[13368]: (MQBKD1.default)[2314]BIP5304E: Resource Manager: Dictionary not found for message set DMER410070001. : MQBKD1.77c9c876-e800-0000-0080-9705b4388941: /build/S000_P/src/MTI/MTIforBroker/MtiImbParser2/MtiImbRMErrorMap.cpp: 135: MtiImbRMErrorMap::checkRC: :-------------------------------------------------------------------------------

It seems like we lost some message sets. Is there anyone else experienced this problem before? I appreciate for any ideas or suggestions.

Thanks.
_________________
Eager to learn
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
jefflowrey
PostPosted: Tue Apr 06, 2004 8:57 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I don't know the migration path from 2.0.2 to 2.1, but if you had to export and then import message sets, the unique id for the message set may have changed during the conversion.

Have them compare any uuids that are in their code with the actual uuid for the message set in the Control Center.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
caroljx
PostPosted: Tue Apr 06, 2004 9:09 am    Post subject: Reply with quote

Newbie

Joined: 06 Apr 2004
Posts: 5
Location: Calgary, AB Canada

During the migration, we didn't touch message sets. According to IBM's instruction, we did following steps:

1. Deintall MQSI 2.0.2.
2. Install MQSI 2.1
3. Migrate MQSI broker's database by createing a temporary broker using "mqsicreatebroker" command:

WebSphere MQ queue manager created.
Creating or replacing default objects for TMPQM.
Default objects statistics : 31 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'TMPQM' started.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP8071I: Successful command completion.


4. Remove tempoary broker using "mqsideletebroker" command.

These steps are on MQSI broker only.
_________________
Eager to learn
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
jefflowrey
PostPosted: Tue Apr 06, 2004 9:18 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Was there nothing additional other than "uninstall, install" to upgrade the ConfigMgr?

Can you double-check that the UUID on a known message set is the same as it used to be?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
caroljx
PostPosted: Tue Apr 06, 2004 9:21 am    Post subject: Reply with quote

Newbie

Joined: 06 Apr 2004
Posts: 5
Location: Calgary, AB Canada

We only upgraded broker on our AIX server. (not configuration manager)
_________________
Eager to learn
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
jefflowrey
PostPosted: Tue Apr 06, 2004 9:24 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

caroljx wrote:
We only upgraded broker on our AIX server. (not configuration manager)


Then just redeploy the message sets.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
caroljx
PostPosted: Tue Apr 06, 2004 9:32 am    Post subject: Reply with quote

Newbie

Joined: 06 Apr 2004
Posts: 5
Location: Calgary, AB Canada

Quote:
Then just redeploy the message sets.


But why do we have to do this step? It is not documented in IBM's instruction. I just feel not comfortable with this redeployment step because I don't know whether or not I lost more information than few message sets.
_________________
Eager to learn
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Loss message set after upgrade MQSI from 2.0.2 to 2.1
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.