| Author |
Message
|
| mqsme |
 Posted: Fri Sep 09, 2016 10:56 am Post subject: Linux: Applying maintenance level upgrades |
 |
|
Acolyte
Joined: 16 Sep 2013
Posts: 51
|
Hi,
I'm trying to apply FP for MQv8.0.0.2 in Linux. From the following page,
https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q008050_.htm
"If this fix pack is to be upgraded on an installation, other than the first installation on the system, run the crtmqfp command to create and use a unique set of packages to install on the system. Note, that if this is the first, or only, IBM MQ installation on the system, you can ignore this step. You must install the pax command in order for the crtmqfp command to run on Linux."
Q: If i only installed MQv8 and IIB V10 in the server. created 2 MQmanagers, should i ignore this step?
Q: in /opt/mqm/bin, it only has crtmqcvx, crtmqenv, crtmqinst, crtmqm, but not crtmqfp. should i skip this step?
Thanks. |
|
| Back to top |
|
 |
| mqsme |
| Posted: Fri Sep 09, 2016 1:06 pm Post subject: |
|
|
Acolyte
Joined: 16 Sep 2013
Posts: 51
|
oh.. just extract the gz file and found the file is included..
5613 Oct 17 2015 crtmqfp
but wondering should i run it or not |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Sep 09, 2016 9:46 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
So what happens when you try to apply the fixpack?
_________________
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 |
|
|
| exerk |
| Posted: Sat Sep 10, 2016 1:05 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Quote: |
| ...Note, that if this is the first, or only, IBM MQ installation on the system, you can ignore this step... |
What is the output from dspmqver -i ?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mqsme |
| Posted: Mon Sep 12, 2016 2:20 pm Post subject: |
|
|
Acolyte
Joined: 16 Sep 2013
Posts: 51
|
I did not specially run crtmqfp and continue the installation and got followings
Name: WebSphere MQ
Version: 8.0.0.4
Level: p800-004-151017
BuildType: IKAP - (Production)
Platform: WebSphere MQ for Linux (x86-64 platform)
Mode: 64-bit
O/S: Linux 2.6.32-573.18.1.el6.x86_64
InstName: Installation1
InstDesc:
Primary: Yes
InstPath: /opt/mqm
DataPath: /var/mqm
MaxCmdLevel: 802
LicenseType: Production
Why I want to install the FP is because I cannot run mqsichangeauthmode [i]integrationNodeName[/i] -s active -m mq under 8.0.0.2
On the other machine i installed 8.0.0.4 from scratch, then I run the mqsichangeauthmode. Now I updated FP from 8.0.0.2 to 8.0.0.4, still fail to run the command and get this error... weird
BIP8051E: Unable to create WebSphere MQ Queue 'SYSTEM.BROKER.AUTH.TEST' on Queue Manager '[i]integrationNodeName[/i]'.
This command attempts to create a WebSphere MQ Queue but was unable to do so.
Locate and resolve the problem and retry the command. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Sep 12, 2016 2:50 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Is the above the output from dspmqver -i ?
When I Googled BIP8051E I found THIS.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mqsme |
| Posted: Mon Sep 12, 2016 3:20 pm Post subject: |
|
|
Acolyte
Joined: 16 Sep 2013
Posts: 51
|
Hi exerk,
Yes, that is the output from dspmqver -i
I also found the same link, that's why it inspired me to update from 8.0.0.2 to 8.0.0.4 since i thought it was fixed by 8.0.0.3. However still fail even after putting fp.
what more interesting is it complains about Unable to create WebSphere MQ Queue SYSTEM.BROKER.AUTH.TEST, but not SYSTEM.BROKER.AUTH as mentioned in the link. Probably have to uninstall all versions and install 8.0.0.4 or upper again. |
|
| Back to top |
|
|
|
|
