| Author |
Message
|
| lancia |
 Posted: Fri Sep 26, 2008 12:33 am Post subject: Messageset lost! |
 |
|
Novice
Joined: 25 Sep 2008
Posts: 10
|
Hello
I'm a total newbie to MQ integrator, i suffered an issue during the
creation of certain execution groups, i was not even able to import
the messageset itself.
PRODUCT WEBSPHERE INTEGRATOR FOR MULTIPLATFORMS version 2.1
PLATFORM : WINDOWS 2000 SERVER
A messageset was imported through windows command line delivering the
following command:
mqsiimpexpmsgset -i -nMQSIMRDB -uUSER -pPASSWD -fC:\ftp\mensajes
\MessageSetMESSAGESET_NAME.xml
This command ended with a success message, but it is imposible to add
it to the MQIntegrator workspace since it does not appear on the list available on the MessageSet tab
MessageSet TAB
I
L------------> Add to Workspace----------------> MessageSet
neither it does appear on the PROJECT table of the DB2 MQSIMRDB
database (Config Manager's Database).
It seems that the messageset is lost somewhere amidst the ms-dos
import command execution and the MQSI database.
i tried to export the message to get rid of it (same
command "mqsiimpexp" but whith the "-e" flag") and obtained this
response:
BIP8186E: The message set MESSAGESETNAME with level -1 is
referenced, but it does not exist in the message repository.
Just excatly as i said, there's no message on PROJECT table of the DB2
database (called MQSIMRDB) but somewhere a referecence for this
messageset exists.
¿Has anyone the slightest idea of what can be done to eliminate this
"ghost" messageset?
Last edited by lancia on Thu Oct 09, 2008 7:27 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Sep 26, 2008 1:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| I would start by upgrading to Message Broker version 6. |
|
| Back to top |
|
|
| lancia |
| Posted: Fri Sep 26, 2008 1:42 am Post subject: |
|
|
Novice
Joined: 25 Sep 2008
Posts: 10
|
| mqjeff wrote: |
| I would start by upgrading to Message Broker version 6. |
Quite obvious, but it's totally impossible, let me add the existant backup is unviable and,as it's clear, the software is unsuported by IBM itself, so you get an idea of my despair.
¿any helpful ideas? |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Sep 26, 2008 8:00 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I would also echo the sentiment of upgrading to a supported version.
If that isn't an option, then I'd suggest that you look into renaming things so that you can avoid the name used by your 'ghost'.
However, I'd really suggest that you move forward to a supported version. |
|
| Back to top |
|
|
| lancia |
| Posted: Fri Sep 26, 2008 10:16 am Post subject: |
|
|
Novice
Joined: 25 Sep 2008
Posts: 10
|
| bower5932 wrote: |
I would also echo the sentiment of upgrading to a supported version.
If that isn't an option, then I'd suggest that you look into renaming things so that you can avoid the name used by your 'ghost'.
However, I'd really suggest that you move forward to a supported version. |
Given the case i'm allowed to make an upgrade (real hard time, really) ¿how can i migrate the existing executions groups and messagesets to it?
¿wouldn't the ghost messageset persist with such an operation? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 26, 2008 10:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Take the opportunity to educate the customer on the rationale for maintaining software at current levels.
Examine the MRM database to see if you can do any manual edits - preferably comparing against an existing MRM database.
Remember that 2.1 does not support anything other than very generic basic XML, niceties like "namespaces" may not be parsable. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Sep 26, 2008 12:19 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| the software is unsuported by IBM itself |
Yes and no.
I'm pretty certain that you can get IBM Global Services (or some other 3rd-party) to come onsite to help.
Long ago, mgt at my company suggested not upgrading (it wasn't MQ) to avoid the cost of the new license. As a contingency, I had them budget $20k for 3rd party support, figuring $300 per hour, minimum 1 day, ...
We had one incident (again, not MQ) where the software failed. IBM came out, two people, 3 days. Beyond this cost, the cost of emploeee lost time was far in excess of the $20k.
It was a learning experience for mgt.
Upgrading or not, hardware/software support licensing or not, these are choices that mgt must make. Choices are just choices - neither good or bad; but mgt must live with the consequences. (Yes, I know, we get blamed...)
I certainly felt compassion for the employees that couldn't do their work, and the customers that couldn't buy our product. But that was the result of the choice made by mgt.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| lancia |
| Posted: Sat Sep 27, 2008 2:09 am Post subject: |
|
|
Novice
Joined: 25 Sep 2008
Posts: 10
|
| bruce2359 wrote: |
| Quote: |
| the software is unsuported by IBM itself |
Yes and no.
I'm pretty certain that you can get IBM Global Services (or some other 3rd-party) to come onsite to help.
|
I regard this installation as resource for learning, this software level is designed to support 6 execution groups and we have 150 , sometimes is a nightmare but everytime a problem arise you learn something new.
Last edited by lancia on Thu Oct 09, 2008 7:29 am; edited 1 time in total |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Sep 27, 2008 2:35 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well the something you should be learning out of this is that you need very strict source version control so that you can redeploy or recreate any artifact from scratch.
Even at version 6 we use svn for the message set, the flows and the bar files.
This way you can check out the deployables or recreate them.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| lancia |
| Posted: Mon Sep 29, 2008 12:40 am Post subject: mrmwebdav.pdb edition |
|
|
Novice
Joined: 25 Sep 2008
Posts: 10
|
Hello.
I guess that the lost messageset definition lies in the archive
mrmwebdav.pdb
Does anyone knows wich program can be used to edit this fileformat?
cheers |
|
| Back to top |
|
|
| bower5932 |
| Posted: Mon Sep 29, 2008 7:36 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Sep 29, 2008 11:30 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I guess that the lost messageset definition lies in the archive |
I don't understand what this means.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| lancia |
| Posted: Mon Sep 29, 2008 11:33 pm Post subject: Seeking for the archive that |
|
|
Novice
Joined: 25 Sep 2008
Posts: 10
|
| bruce2359 wrote: |
| Quote: |
| I guess that the lost messageset definition lies in the archive |
I don't understand what this means. |
Hello Bruce.
I'm trying to seek the physical archive that contains the "ghost" messageset reference, since in the DB2 databases is not included. In other words, the files in wich the repository content is defined.
Being a MQSeries Integrator v2.1 there's no BAR file and thence no broker.xml, but something similar must exist , whether it is a queue, an xml or a flat text archive.
BTW the IC01 supportpac includes a command called mqsideletemsgset, wich is pretty promising, but i'm dubious of asking it, i've heard a lot of complains about it and the last thing i need are more problems. |
|
| Back to top |
|
|
| lancia |
| Posted: Tue Sep 30, 2008 3:35 am Post subject: IC01 supportpac |
|
|
Novice
Joined: 25 Sep 2008
Posts: 10
|
I finally decided to use the IC01 supportpac.
Delivering the following command :
"mqsideletemsgset MessageSetName.xml"
I get a message wich states that the messageset does not exist in MRM, i try to delete it using various level flags too (-l 1, or -l 2 ...-l #) and the result is the same, but whenever i try to import it once more, i get the error code of the first post:
BIP8175: Duplicate message set identifier.
0_O |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 30, 2008 3:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
From what little I remember of 2.1, the only place anything is kept is in the database.
It sounds like you have removed all of the data records for the message set, but somehow not removed all of the index records that associate the data with the message set UUID.
That is, some row somewhere in some table still knows about the message set identifier.
As I said earlier, you probably need to do very careful manual edits on the MRM database. |
|
| Back to top |
|
|
|
|
