| Author |
Message
|
| Lex |
 Posted: Thu Nov 16, 2006 4:36 am Post subject: mqsimigratemsgflows: unknown error (BIP0871E) |
 |
|
Acolyte
Joined: 14 Nov 2006
Posts: 73
|
Well after having trouble to get my mqsimigratemsgflows command to work properly, i encounter a new problem while migrating my existing flows.
Each flow i have migrated encounter the same problem, as described in the mqsimigratemsgflows.report.txt:
| Code: |
================================================================================
Migration du fichier d'exportation D:\Migration12A\FL_Archivage.xml.
--------------------------------------------------
Migration du flux de messages FL_Archivage.
Error: BIP0871E La conversion depuis la chaîne {0} en Date a échoué.
Impossible d'affecter une valeur pour la propriété validateFixup depuis le flux FL_Archivage.
Utilisez WebSphere Studio pour ouvrir le flux et affecter une valeur admise.
Le format pour une propriété Date ESQL est : aaaa-mm-jj
Error: BIP0871E La conversion depuis la chaîne {0} en Date a échoué.
Impossible d'affecter une valeur pour la propriété validateFailureAction depuis le flux FL_Archivage.
Utilisez WebSphere Studio pour ouvrir le flux et affecter une valeur admise.
Le format pour une propriété Date ESQL est : aaaa-mm-jj
Error: BIP0871E La conversion depuis la chaîne {0} en Date a échoué.
Impossible d'affecter une valeur pour la propriété validateMaster depuis le flux FL_Archivage.
Utilisez WebSphere Studio pour ouvrir le flux et affecter une valeur admise.
Le format pour une propriété Date ESQL est : aaaa-mm-jj |
(Sorry it's a french version)
This problem occurs only on the compute nodes i migrate. I searched the error (BIP0871E) on google and on the IBM Website, but my search returned no result.
Anyone encountered this problem too? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Nov 16, 2006 4:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| Lex |
| Posted: Thu Nov 16, 2006 5:06 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2006
Posts: 73
|
| And what would be the solution for this? |
|
| Back to top |
|
|
| Lex |
| Posted: Thu Nov 16, 2006 5:16 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2006
Posts: 73
|
i checked my .xml files obtained from the 2.1 version, and all these errors are about the same kind of nodes, and the same properties (validateMaster, validateFailureAction and validateFixup).
These properties have kept the default value. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 16, 2006 5:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I don't know the solution for this - I've never worked with the French edition...
My thought is that it is complaining about the format of dates because when you run mqsiprofile.cmd before running mqsimigratemsgflows, you are overwriting or otherwise not including the environment variables that tell the mqsimigrateflows command to use French formatted dates, rather than U.K standard formatted dates or whatever the default is.
I suspect you need to open a PMR, but maybe someone else knows better.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Lex |
| Posted: Thu Nov 16, 2006 6:06 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2006
Posts: 73
|
| i also have problem with nodes, like "impossible to locate the terminal "in" on node "your_node", and some kinds of node are not recognized (like ComIbmCompute or ComIbmFilter). |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 16, 2006 7:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Then I would say you have a bad installation.
Possibly you only installed or only applied the FixPack for EventBroker instead of MessageBroker?
If it is failing to recognize ComIBMCompute, then almost certainly you have not installed Message Broker but only Event Broker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Lex |
| Posted: Thu Nov 16, 2006 7:58 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2006
Posts: 73
|
I have a set of 5 CDs, and it's written Message Broker Toolkit, i hope it's the right thing...
But at the end of the installation, i had a screen telling me that eclipse was initializing and it stayed for like 10 minutes before i had a message telling me the installation had failed.
That's the 3rd time i install it and still i can't use the Toolkit  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 16, 2006 8:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You may have bad CDs.
You almost certainly are installing the Event Broker Toolkit, which is not as clearly labeled as it might be from what I have seen.
I would uninstall the Toolkit completely, and start over after double-checking that you have CDs that are correct and valid, and that you are actually running the Message Broker Toolkit install.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Lex |
| Posted: Thu Nov 16, 2006 11:43 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2006
Posts: 73
|
I reinstalled the toolkit (which is really the message broker toolkit, as it is labeled on the CD).
After 2 hours 30 minutes i finally got a clean install which seems to work (the migration did no error).
Why is the installation taking so much time in the end, while it installs the 6.0.0.1 version? |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Nov 16, 2006 11:51 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
I don't know why it takes that long, but your not done.
Close the toolkit and bring up the Rational Product Updater. Click on the Update tab and update to 6.0.0.2!
And wait for a long time again.
_________________
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 |
|
|
| Lex |
| Posted: Fri Nov 17, 2006 12:56 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2006
Posts: 73
|
| What does the 6.0.0.2 fix? Is this update worth it? Cause i don't want to corrupt my new install with this update and begin a new install again, i'm very short in time lol |
|
| Back to top |
|
|
|
|
