| Author |
Message
|
| b_anup |
 Posted: Fri Jun 27, 2014 8:10 am Post subject: Error - Attribute called InstallationName that is not valid |
 |
|
Novice
Joined: 26 Jun 2014
Posts: 11
|
After MQ upgrade to 7.5 on solaris patform we are seeing following error
AMQ7075: Unknown attribute in ini file.
EXPLANATION:
Line 40 of the configuration file /var/mqm/mqs.ini contained an attribute
called InstallationName that is not valid. This attribute is not recognized in
this context.
ACTION:
Check the contents of the file and retry the operation.
When we tried removing InstallationName from mqs.ini queue manager shows status as STATUS(Status not available)
Then we tried to restart queue manager but mqs.ini got updated with InstallationName parameter again.
What could be the resolution to this error? |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Jun 27, 2014 8:28 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Have you defined the primary installation as instructed in the documentation?
_________________
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 |
|
|
| b_anup |
| Posted: Fri Jun 27, 2014 10:28 pm Post subject: |
|
|
Novice
Joined: 26 Jun 2014
Posts: 11
|
Thanks Jedi for your reply.
We tried with ./setmqinst -x -p /opt/mqm/ command but still we are getting same error. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jun 27, 2014 11:40 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
So when you run dspmqinst, what is the InstName and is it in the same case in the mqs.ini?
Do you by any chance run multiple installations of MQ collocated on the box?
If still running WMQ 7.0 did you correctly set the default/primary instance to that installation?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Sat Jun 28, 2014 2:49 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
| If still running WMQ 7.0 did you correctly set the default/primary instance to that installation? |
It is my understanding that while WMQ version 7.0 is installed, you cannot change which installation is the primary installation - it will always be the WMQ V7.0 version.
b_anup, it would be helpful if you could post the content of your mqs.ini file, complete with the 'offending' line.
_________________
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 |
|
|
| b_anup |
| Posted: Sat Jun 28, 2014 2:55 am Post subject: |
|
|
Novice
Joined: 26 Jun 2014
Posts: 11
|
Grand, we did not run multiple installations.
Following is the output of dspmqinst
InstName: Installation1
InstDesc:
Identifier: 1
InstPath: /opt/mqm
Version: 7.5.0.2
Primary: Yes
State: Available
and following is entry in /var/mqm/mqs.ini
| Code: |
DefaultPrefix=/var/mqm
LogDefaults:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogDefaultPath=/var/mqm/log
QueueManager:
Name=XXXXXX
Prefix=/var/mqm
Directory=XXXXXX
InstallationName=Installation1 |
where XXXXXX is a queue manager name.
Also we have used setmqinst -i -p /opt/mqm to set primary instance. |
|
| Back to top |
|
|
| exerk |
| Posted: Sat Jun 28, 2014 3:12 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
You stated, "...Line 40 of the configuration file /var/mqm/mqs.ini contained an attribute called InstallationName that is not valid...", so what's in Line 40, because there aren't 40 lines in the content you've posted?
_________________
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 |
|
|
| b_anup |
| Posted: Sat Jun 28, 2014 3:29 am Post subject: |
|
|
Novice
Joined: 26 Jun 2014
Posts: 11
|
| Code: |
#********************************************************************#
#* *#
#* <N_OCO_COPYRIGHT> *#
#* Licensed Materials - Property of IBM *#
#* *#
#* 63H9336 *#
#* (C) Copyright IBM Corporation 1994, 2003 *#
#* *#
#* <NOC_COPYRIGHT> *#
#* *#
#********************************************************************#
#***********************************************************************#
#* Module Name: mqs.ini *#
#* Type : WebSphere MQ Machine-wide Configuration File *#
#* Function : Define WebSphere MQ resources for an entire machine *#
#* *#
#***********************************************************************#
#* Notes : *#
#* 1) This is the installation time default configuration *#
#* *#
#***********************************************************************#
AllQueueManagers:
#********************************************************************#
#* The path to the qmgrs directory, below which queue manager data *#
#* is stored *#
#********************************************************************#
DefaultPrefix=/var/mqm
LogDefaults:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogDefaultPath=/var/mqm/log
QueueManager:
Name=XXXXXX
Prefix=/var/mqm
Directory=XXXXXX
InstallationName=Installation1 |
|
|
| Back to top |
|
|
| exerk |
| Posted: Sat Jun 28, 2014 6:09 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
OK, thank you, that makes things clearer. I wasn't sure if you were omitting the stuff at the top or had multiple queue managers specified. Worth your while opening a PMR with this one I think.
_________________
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 |
|
|
| fjb_saper |
| Posted: Sat Jun 28, 2014 2:40 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Make sure there is no space after the installation name... and you should probably have a blank line after that too.
Alternatively run setmqm -n installationname -m qmgrname
This should update the mqs.ini
make sure to only leave a single space between installation name and qmgr name.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Philip_Morten |
| Posted: Sun Jun 29, 2014 11:06 am Post subject: |
|
|
Newbie
Joined: 11 Dec 2006
Posts: 5
Location: Hursley Park
|
It might be of interest to check the contents of /etc/opt/mqm/mqinst.ini and see if the values there match what it is in your mqs.ini.
_________________
--
Philip Morten |
|
| Back to top |
|
|
|
|
