Author |
Message
|
SphereOfLove |
Posted: Thu Mar 05, 2015 6:23 am Post subject: BIP8004E: Invalid argument '-e' specified. Argument specifie |
|
|
Apprentice
Joined: 13 May 2014 Posts: 38
|
I am running the command to add broker instance info on the second node
Code: |
mqsiaddbrokerinstance testBroker -i "CLUSTERNODE\xxxxxx" -a xxxxxxx –e "C:\MQDisk\Broker\Workspace |
"
It returns with the following Error.
Quote: |
BIP8004E: Invalid argument '-e' specified. Argument specified should be well formed. Correct and reissue the command |
I have tried to run IBM Integration Console with
and then run the above mentioned command, but still no success.
Please help!
Thanks in advanced! |
|
Back to top |
|
 |
Vitor |
Posted: Thu Mar 05, 2015 6:34 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Is this the same environment you described here?
(To save people asking questions about platform & version) _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
SphereOfLove |
Posted: Thu Mar 05, 2015 6:38 am Post subject: |
|
|
Apprentice
Joined: 13 May 2014 Posts: 38
|
Vitor wrote: |
Is this the same environment you described here?
(To save people asking questions about platform & version) |
In short, YES;
I am working on Integration Bus 9 ( MQ 7.5.0.1) on Windows 2008 r2 data center addition MSCS Cluster! |
|
Back to top |
|
 |
Vitor |
Posted: Thu Mar 05, 2015 6:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Have you tried the -e parameter with 2 quotes and no quotes?
The posted example has 1 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Mar 05, 2015 7:01 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Code: |
-e C:\MQDisk\Broker\Workspace |
seems an odd path for shared data. I might expect that for a workpath local i.e. -w flag...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
SphereOfLove |
Posted: Thu Mar 05, 2015 7:30 am Post subject: |
|
|
Apprentice
Joined: 13 May 2014 Posts: 38
|
|
Back to top |
|
 |
mqjeff |
Posted: Thu Mar 05, 2015 7:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
SphereOfLove wrote: |
Let me try this!
Thanks |
You should make sure that the path is actually a valid Windows path - for example that it has the right number of \ in the right places.
You should make sure you know what -e should point to and that you know what -w should point to, and not just switch between them willy-nilly. |
|
Back to top |
|
 |
JosephGramig |
Posted: Thu Mar 05, 2015 11:46 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
I think you have to fail it over before you add it (so the path is valid). Did you do that? |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Mar 05, 2015 12:14 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
The shared path is really strange.
C:\....
Is not normally on a shared drive in windows terms. This is rather strange.
The other thing to consider is how the broker was created in the first place.
If this is not done 100% right the second instance won't run.
It is very easy to get things wrong here. I went through all this (with much contact admin of teeth) a year ago. If you go back through the posts on the Broker forum then you will find a couple of threads started by me on this very subject.
It might be worth your while reading them _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
SphereOfLove |
Posted: Mon Mar 09, 2015 7:07 am Post subject: |
|
|
Apprentice
Joined: 13 May 2014 Posts: 38
|
JosephGramig wrote: |
I think you have to fail it over before you add it (so the path is valid). Did you do that? |
Yes, for adding Broker instance to the other node, i have switched it over to the second node.
I am able to add broker instance into the second node. I had to stop QM endmqm -i QMName, and the restart it with strmqm -si QMName. |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Mar 09, 2015 7:48 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
SphereOfLove wrote: |
JosephGramig wrote: |
I think you have to fail it over before you add it (so the path is valid). Did you do that? |
Yes, for adding Broker instance to the other node, i have switched it over to the second node.
I am able to add broker instance into the second node. I had to stop QM endmqm -i QMName, and the restart it with strmqm -si QMName. |
You should not have to start the QM in interactive mode. What happens if you start it using the MSCS cluster facilities? There could be a problem with the group membership of your service users. What did you set up?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
SphereOfLove |
Posted: Mon Mar 09, 2015 8:12 am Post subject: |
|
|
Apprentice
Joined: 13 May 2014 Posts: 38
|
fjb_saper wrote: |
SphereOfLove wrote: |
JosephGramig wrote: |
I think you have to fail it over before you add it (so the path is valid). Did you do that? |
Yes, for adding Broker instance to the other node, i have switched it over to the second node.
I am able to add broker instance into the second node. I had to stop QM endmqm -i QMName, and the restart it with strmqm -si QMName. |
You should not have to start the QM in interactive mode. What happens if you start it using the MSCS cluster facilities? There could be a problem with the group membership of your service users. What did you set up?  |
When i try to start or stop QM from the MSCS cluster manager, it works fine. I can start and stop QM with out any problem. Also, when i switch between cluster nodes, i couls do that with out any problem with QM.
The problem is with Broker. It is not starting and stopping with MSCS cluster service. Moreover, during node switch, broker service fails and broker does not start:( |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Mar 09, 2015 9:05 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
fjb_saper wrote: |
There could be a problem with the group membership of your service users. What did you set up?  |
All your service users are domain users yes? _________________ MQ & Broker admin |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Mar 09, 2015 9:35 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
http://www.mqseries.net/phpBB2/viewtopic.php?t=67168
May help you out.
Don't add the broker as a MSCS resource until it works manually on both nodes.
When you do you have to make the broker dependent on the QMGR resouce. This way the starting and stopping of everything is nicely synchronised. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
SphereOfLove |
Posted: Tue Mar 10, 2015 7:08 am Post subject: |
|
|
Apprentice
Joined: 13 May 2014 Posts: 38
|
smdavies99 wrote: |
http://www.mqseries.net/phpBB2/viewtopic.php?t=67168
May help you out.
Don't add the broker as a MSCS resource until it works manually on both nodes.
When you do you have to make the broker dependent on the QMGR resouce. This way the starting and stopping of everything is nicely synchronised. |
Thank you smdavies99. I followed your instruction and the link you sent in this post and as well on the other post from me.
Thank you again! |
|
Back to top |
|
 |
|