Author |
Message
|
Kanwar |
Posted: Sat Mar 21, 2009 2:36 am Post subject: not able to create queue manager |
|
|
Novice
Joined: 21 Mar 2009 Posts: 15
|
hi all
while trying to create a new queue manager m getting the following error message:
****************************************************
AMQ8101: WebSphere MQ was unable to open a message catalog to display an error message for message id hexadecimal 20008101, with inserts 2195, 0, , , and . The following command, issued on a system that does not have message catalog difficulties, may provide more information about that message: mqrc AMQ8101
****************************************************
on doing /opt/mqm/bin> mqrc AMQ8101
/build/p600_P/src/cmd/tools/mqrc/mqrc.c[923]
lpiObtainQMDetails --> 545261715
 |
|
Back to top |
|
 |
bruce2359 |
Posted: Sat Mar 21, 2009 5:27 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
What o/s?
What WMQ version? What maintenance level?
Any other qmgrs created/running on this server?
Post the exact command you used when you attempted to create the qmgr.
Did an FDC get created? If so, post it here. _________________ 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 |
|
 |
Kanwar |
Posted: Mon Mar 23, 2009 12:24 am Post subject: |
|
|
Novice
Joined: 21 Mar 2009 Posts: 15
|
o/s : HP-UX B.11.31 U ia64
WMQ version: 6.0.1.0
Any other qmgrs created/running on this server: none
command to create the qmgr: /opt/mqm/bin> crtmqm test_kj
status of FDC : no FDC created
status of /var/mqm:
/var/mqm> ls -lrt
total 0
drwxr-xr-x 2 root sys 96 Mar 12 2008 tivoli/ |
|
Back to top |
|
 |
sumit |
Posted: Mon Mar 23, 2009 12:52 am Post subject: Re: not able to create queue manager |
|
|
Partisan
Joined: 19 Jan 2006 Posts: 398
|
Kanwar wrote: |
on doing /opt/mqm/bin> mqrc AMQ8101
/build/p600_P/src/cmd/tools/mqrc/mqrc.c[923]
lpiObtainQMDetails --> 545261715
 |
Are you sure that you successfully installed MQ on your server? I did mqrc on my machine and got this:
U:\>mqrc AMQ8101
536903937 0x20008101 ocmRC_UNEXPECTED_CSV_STATE
536903937 0x20008101 ocmRC_UNEXPECTED_ERROR
536903937 0x20008101 urcMS_ERROR
536903937 0x20008101 zrc_CSPRC_UNEXPECTED_ERROR
MESSAGE:
WebSphere MQ error (457) has occurred.
EXPLANATION:
An unexpected reason code with hexadecimal value 457 was received from the
WebSphere MQ queue manager during command processing. (Note that hexadecimal
values in the range X'07D1'-X'0BB7' correspond to MQI reason codes 2001-2999.)
More information might be available in the log. If the reason code value
indicates that the error was associated with a particular parameter, the
parameter concerned is <insert two>.
ACTION:
Correct the error and then try the command again. _________________ Regards
Sumit |
|
Back to top |
|
 |
Kanwar |
Posted: Mon Mar 23, 2009 12:56 am Post subject: |
|
|
Novice
Joined: 21 Mar 2009 Posts: 15
|
on doing dspmqver, i get the following output:
/opt/mqm/bin> dspmqver
Name: WebSphere MQ
Version: 6.0.1.0
CMVC level: p600-100-051021
BuildType: IKAP - (Production)
how do i check if i have a successfull installation or not? |
|
Back to top |
|
 |
Vitor |
Posted: Mon Mar 23, 2009 1:17 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Kanwar wrote: |
status of /var/mqm:
/var/mqm> ls -lrt
total 0
drwxr-xr-x 2 root sys 96 Mar 12 2008 tivoli/ |
Does root also own /var/mqm? Possibly also /opt/mqm? Why doesn't mqm own these?
(Hint - permissions are set by the install script. If it works properly....) _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Philip Morten |
Posted: Mon Mar 23, 2009 1:23 am Post subject: |
|
|
Master
Joined: 07 Mar 2002 Posts: 230 Location: Hursley Park
|
Kanwar wrote: |
on doing dspmqver, i get the following output:
/opt/mqm/bin> dspmqver
Name: WebSphere MQ
Version: 6.0.1.0
CMVC level: p600-100-051021
BuildType: IKAP - (Production)
how do i check if i have a successfull installation or not? |
swjob will let you view swinstall's installation logs.
swlist MQSERIES will show you which filesets are installed
swverify MQSERIES will check the integrity of the installation against
the product database.
Have you got unusual settings for your locale? Do you have NLSPATH set ? _________________ Philip Morten
The postings on this site are my own and do not necessarily represent IBM's positions, strategies or opinions. |
|
Back to top |
|
 |
markt |
Posted: Mon Mar 23, 2009 1:25 am Post subject: |
|
|
 Knight
Joined: 14 May 2002 Posts: 508
|
You have a near-empty /var/mqm which means you have not installed the product correctly. |
|
Back to top |
|
 |
Kanwar |
Posted: Mon Mar 23, 2009 2:23 am Post subject: |
|
|
Novice
Joined: 21 Mar 2009 Posts: 15
|
/opt/mqm/bin> swjob
#
# Controller: <server_name>
#
#jobid operation state results title
#
<server_name>-0001 Copy Complete
<server_name>-0002 Copy Complete
<server_name>-0003 Copy Complete
<server_name>-0004 Verify (depot) Complete
<server_name>-0006 Configure Complete
<server_name>-0012 Install Complete
<server_name>-0039 Install Complete
<server_name>-0040 Install Complete
<server_name>-0041 Install Complete
<server_name>-0042 Install Complete
<server_name>-0046 Install Complete
<server_name>-0062 Copy Complete
<server_name>-0063 Copy Complete
<server_name>-0064 Copy Complete
<server_name>-0065 Verify (depot) Complete
<server_name>-0066 Configure Complete
<server_name>-0073 Install Complete
<server_name>-0074 Install Complete
<server_name>-0075 Install Complete
<server_name>-0076 Install Complete
/opt/mqm/bin> swlist MQSERIES
# Initializing...
# Contacting target "<server_name>"...
#
# Target: <server_name>:/
#
# MQSERIES 6.0.1.0 WebSphere MQ for HP-UX
MQSERIES.MQM-BASE 6.0.1.0 WebSphere MQ SDK fileset
MQSERIES.MQM-CL-HPUX 6.0.1.0 WebSphere MQ Client for HP-UX
MQSERIES.MQM-JAVA 6.0.1.0 WebSphere MQ Java Client, JMS and SOAP support
MQSERIES.MQM-JAVASDK 6.0.1.0 HP SDK for J2SE HP-UX 11i platform
MQSERIES.MQM-KEYMAN 6.0.1.0 WebSphere MQ SSL Key management
MQSERIES.MQM-MAN 6.0.1.0 WebSphere MQ man pages
MQSERIES.MQM-MC-CHINES 6.0.1.0 WebSphere MQ Message catalog for Simplified Chinese
MQSERIES.MQM-MC-CHINET 6.0.1.0 WebSphere MQ Message catalog for Traditional Chinese
MQSERIES.MQM-MC-FRENCH 6.0.1.0 WebSphere MQ Message catalog for French
MQSERIES.MQM-MC-GERMAN 6.0.1.0 WebSphere MQ Message catalog for German
MQSERIES.MQM-MC-ITALIAN 6.0.1.0 WebSphere MQ Message catalog for Italian
MQSERIES.MQM-MC-JAPAN 6.0.1.0 WebSphere MQ Message catalog for Japanese
MQSERIES.MQM-MC-KOREAN 6.0.1.0 WebSphere MQ Message catalog for Korean
MQSERIES.MQM-MC-PORT 6.0.1.0 WebSphere MQ Message catalog for Portuguese
MQSERIES.MQM-MC-SPANISH 6.0.1.0 WebSphere MQ Message catalog for Spanish
MQSERIES.MQM-RUNTIME 6.0.1.0 WebSphere MQ Runtime fileset
MQSERIES.MQM-SAMPLES 6.0.1.0 WebSphere MQ Sample programs
MQSERIES.MQM-SERVER 6.0.1.0 WebSphere MQ Server fileset
MQSERIES.MQM-TXCLIENT 6.0.1.0 WebSphere MQ Transactional Client
/opt/mqm/bin> swverify MQSERIES
======= 03/23/09 15:52:45 IST BEGIN swverify SESSION
(non-interactive) (jobid=<server_name>-0089)
* Session started for user "mqm@<server_name>".
* Beginning Selection
ERROR: "<server_name>:/": You do not have the required permissions to
select this target. Check permissions using the "swacl"
command or see your system administrator for assistance. Or,
to manage applications designed and packaged for nonprivileged
mode, see the "run_as_superuser" option in the "sd" man page.
* Target connection failed for "<server_name>:/".
ERROR: More information may be found in the daemon logfile on this
target (default location is <server_name>:/var/adm/sw/swagentd.log).
* Selection had errors.
======= 03/23/09 15:52:46 IST END swverify SESSION (non-interactive)
(jobid=<server_name>-0089)
mqm owns /var/mqm & /opt/mqm
i'm really feeling encouraged to see such great support [/i] |
|
Back to top |
|
 |
Philip Morten |
Posted: Mon Mar 23, 2009 3:12 am Post subject: |
|
|
Master
Joined: 07 Mar 2002 Posts: 230 Location: Hursley Park
|
Kanwar wrote: |
/opt/mqm/bin> swjob
#
# Controller: <server_name>
#
#jobid operation state results title
#
<server_name>-0001 Copy Complete
<server_name>-0002 Copy Complete
<server_name>-0003 Copy Complete
<server_name>-0004 Verify (depot) Complete
<server_name>-0006 Configure Complete
<server_name>-0012 Install Complete
<server_name>-0039 Install Complete
<server_name>-0040 Install Complete
<server_name>-0041 Install Complete
<server_name>-0042 Install Complete
<server_name>-0046 Install Complete
<server_name>-0062 Copy Complete
<server_name>-0063 Copy Complete
<server_name>-0064 Copy Complete
<server_name>-0065 Verify (depot) Complete
<server_name>-0066 Configure Complete
<server_name>-0073 Install Complete
<server_name>-0074 Install Complete
<server_name>-0075 Install Complete
<server_name>-0076 Install Complete
|
That looks a bit odd, I would expect to see the real server name where you are getting <server_name>.
You need to identify which of theses entries represents the installation of MQSERIES, swlist -v MQSERIES.MQM-RUNTIME will give a lot of information about the installation including the install date and time, ( it will also show the state which should be 'configured') . swjob -v will give the date and time of each job. By matching these you should be able to identify which job corresponds to the installtion of MQSERIES. Then use the command swjob -a log jobid to see the log for that job. At the end of that output there may be given a command to get more information.
The /var/mqm directory structure is initialised by a program run in the configure stage of the installation so you should look in particular for errors in this area.
Quote: |
/opt/mqm/bin> swlist MQSERIES
# Initializing...
# Contacting target "<server_name>"...
#
# Target: <server_name>:/
#
# MQSERIES 6.0.1.0 WebSphere MQ for HP-UX
MQSERIES.MQM-BASE 6.0.1.0 WebSphere MQ SDK fileset
MQSERIES.MQM-CL-HPUX 6.0.1.0 WebSphere MQ Client for HP-UX
MQSERIES.MQM-JAVA 6.0.1.0 WebSphere MQ Java Client, JMS and SOAP support
MQSERIES.MQM-JAVASDK 6.0.1.0 HP SDK for J2SE HP-UX 11i platform
MQSERIES.MQM-KEYMAN 6.0.1.0 WebSphere MQ SSL Key management
MQSERIES.MQM-MAN 6.0.1.0 WebSphere MQ man pages
MQSERIES.MQM-MC-CHINES 6.0.1.0 WebSphere MQ Message catalog for Simplified Chinese
MQSERIES.MQM-MC-CHINET 6.0.1.0 WebSphere MQ Message catalog for Traditional Chinese
MQSERIES.MQM-MC-FRENCH 6.0.1.0 WebSphere MQ Message catalog for French
MQSERIES.MQM-MC-GERMAN 6.0.1.0 WebSphere MQ Message catalog for German
MQSERIES.MQM-MC-ITALIAN 6.0.1.0 WebSphere MQ Message catalog for Italian
MQSERIES.MQM-MC-JAPAN 6.0.1.0 WebSphere MQ Message catalog for Japanese
MQSERIES.MQM-MC-KOREAN 6.0.1.0 WebSphere MQ Message catalog for Korean
MQSERIES.MQM-MC-PORT 6.0.1.0 WebSphere MQ Message catalog for Portuguese
MQSERIES.MQM-MC-SPANISH 6.0.1.0 WebSphere MQ Message catalog for Spanish
MQSERIES.MQM-RUNTIME 6.0.1.0 WebSphere MQ Runtime fileset
MQSERIES.MQM-SAMPLES 6.0.1.0 WebSphere MQ Sample programs
MQSERIES.MQM-SERVER 6.0.1.0 WebSphere MQ Server fileset
MQSERIES.MQM-TXCLIENT 6.0.1.0 WebSphere MQ Transactional Client
|
This looks OK - except for the odd <server_name> where I would expect to see the hostname.
Quote: |
/opt/mqm/bin> swverify MQSERIES
======= 03/23/09 15:52:45 IST BEGIN swverify SESSION
(non-interactive) (jobid=<server_name>-0089)
* Session started for user "mqm@<server_name>".
* Beginning Selection
ERROR: "<server_name>:/": You do not have the required permissions to
select this target. Check permissions using the "swacl"
command or see your system administrator for assistance. Or,
to manage applications designed and packaged for nonprivileged
mode, see the "run_as_superuser" option in the "sd" man page.
* Target connection failed for "<server_name>:/".
ERROR: More information may be found in the daemon logfile on this
target (default location is <server_name>:/var/adm/sw/swagentd.log).
* Selection had errors.
======= 03/23/09 15:52:46 IST END swverify SESSION (non-interactive)
(jobid=<server_name>-0089)
|
You will need to be root to do this. _________________ Philip Morten
The postings on this site are my own and do not necessarily represent IBM's positions, strategies or opinions. |
|
Back to top |
|
 |
Kanwar |
Posted: Mon Mar 23, 2009 3:46 am Post subject: |
|
|
Novice
Joined: 21 Mar 2009 Posts: 15
|
hi Philip
I had intentionally replaced the server name by this string.
Now i'll check for the things you mentioned.
Regards
Kanwar |
|
Back to top |
|
 |
exerk |
Posted: Mon Mar 23, 2009 3:50 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Kanwar wrote: |
...I had intentionally replaced the server name by this string... |
Then it is always best to state in the original post that you have 'sanitised' the output. _________________ 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 |
|
 |
Kanwar |
Posted: Mon Mar 23, 2009 4:09 am Post subject: |
|
|
Novice
Joined: 21 Mar 2009 Posts: 15
|
sorry for the inconvinience exerk..
Philip please check the output below:
swlist -v MQSERIES.MQM-RUNTIME
# Date: Mon Mar 23 17:40:19 2009
#
MQSERIES.MQM-RUNTIME
fileset
tag MQM-RUNTIME
software_spec MQSERIES.MQM-RUNTIME,l=/opt/mqm,r=6.0.1.0,a=HP-UX_B.11_IA,v=IBM
data_model_revision 2.40
instance_id 1
control_directory MQM-RUNTIME
size 31862934
revision 6.0.1.0
title WebSphere MQ Runtime fileset
description "Runtime component common to Client and Server Installations"
mod_date Mon Mar 17 15:03:56 IST 2008
mod_time 1205746436
create_date Mon Mar 17 15:03:40 IST 2008
create_time 1205746420
install_date 200803171503.56
architecture
machine_type
os_name
os_release
os_version
install_source charaka:/root/mqm/p600-100-051021.v11
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/amqiclen
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/checkinstall
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/checkremove
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/configure
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/postremove
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/unconfigure
is_patch false
supersedes
category_tag
state installed
is_kernel false
is_reboot false
is_secure false
ancestor
media_sequence_number
partial_file
partial_pipe_size
partial_state_path
is_sparse false
applied_patches
is_locatable
location /opt/mqm
dynamic_module
is_drd_safe
swjob -v
everything was complete here.
since the state above is installed, does this mean my /var/mqm directory is not proper.
status of /var/mqm:
/var/mqm> ls -lrt
total 0
drwxr-xr-x 2 root sys 96 Mar 12 2008 tivoli/
/var/mqm is mqm owned. |
|
Back to top |
|
 |
exerk |
Posted: Mon Mar 23, 2009 4:22 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Kanwar wrote: |
sorry for the inconvinience exerk... |
No inconvenience whatsoever. It just stops people from scratching their heads and possibly sending you off on a wild goose chase because it may well affect their answer to you . _________________ 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 |
|
 |
Kanwar |
Posted: Mon Mar 23, 2009 4:28 am Post subject: |
|
|
Novice
Joined: 21 Mar 2009 Posts: 15
|
sorry for the inconvinience exerk..
Philip please check the output below:
swlist -v MQSERIES.MQM-RUNTIME
# Date: Mon Mar 23 17:40:19 2009
#
MQSERIES.MQM-RUNTIME
fileset
tag MQM-RUNTIME
software_spec MQSERIES.MQM-RUNTIME,l=/opt/mqm,r=6.0.1.0,a=HP-UX_B.11_IA,v=IBM
data_model_revision 2.40
instance_id 1
control_directory MQM-RUNTIME
size 31862934
revision 6.0.1.0
title WebSphere MQ Runtime fileset
description "Runtime component common to Client and Server Installations"
mod_date Mon Mar 17 15:03:56 IST 2008
mod_time 1205746436
create_date Mon Mar 17 15:03:40 IST 2008
create_time 1205746420
install_date 200803171503.56
architecture
machine_type
os_name
os_release
os_version
install_source charaka:/root/mqm/p600-100-051021.v11
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/amqiclen
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/checkinstall
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/checkremove
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/configure
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/postremove
control_file //var/adm/sw/products/MQSERIES/MQM-RUNTIME/unconfigure
is_patch false
supersedes
category_tag
state installed
is_kernel false
is_reboot false
is_secure false
ancestor
media_sequence_number
partial_file
partial_pipe_size
partial_state_path
is_sparse false
applied_patches
is_locatable
location /opt/mqm
dynamic_module
is_drd_safe
swjob -v
everything was complete here.
since the state above is installed, does this mean my /var/mqm directory is not proper.
status of /var/mqm:
/var/mqm> ls -lrt
total 0
drwxr-xr-x 2 root sys 96 Mar 12 2008 tivoli/
/var/mqm is mqm owned. |
|
Back to top |
|
 |
|