| Author |
Message
|
| beekumar |
 Posted: Fri Apr 24, 2009 6:40 am Post subject: Mq Error multiple errors while creating QM |
 |
|
Newbie
Joined: 24 Apr 2009
Posts: 8
|
As I am new to MQ I am unable to resolve this issue... can anybody help me...
Actually my task is to create broker. 2 days back it went fine with creating qmgr2 QM but some errors with odbc. later next day morning I started creating new broker. And I came up with below error:
AMQ8101: WebSphere MQ error (893) has occurred.
BIP8081 An exception was caught while processing the response message for the command, 'Unable to format an ImbException message for output, ImbException message number is BIP8069
While creating a broker.
MQ ErrorAMQ8101: WebSphere MQ error (893) has occurred.
BIP8069
**************************************************************
planned to create qm by user mqm. just checking...
Already existing QM qmgr2. stopped and started.
bash-3.00$ strmqm qmgr2
WebSphere MQ queue manager 'qmgr2' starting.
5 log records accessed on queue manager 'qmgr2' during the log replay phase.
Log replay for queue manager 'qmgr2' complete.
Transaction manager state recovered for queue manager 'qmgr2'.
WebSphere MQ queue manager 'qmgr2' started.
Creating new QM...
bash-3.00$ crtmqm qm11
bash-3.00$ strmqm qm11
WebSphere MQ queue manager 'qm11' starting.
The queue manager does not exist.
trying to delete and later create the existing QM
bash-3.00$ dltmqm qmgr2
WebSphere MQ queue manager running.
bash-3.00$ endmqm -i qmgr2
WebSphere MQ queue manager 'qmgr2' ending.
WebSphere MQ queue manager 'qmgr2' ended.
bash-3.00$ dltmqm qmgr2
WebSphere MQ queue manager 'qmgr2' deleted.
bash-3.00$ crtmqm qmgr2
WebSphere MQ queue manager created.
Creating or replacing default objects for qmgr2.
Default objects statistics : 40 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
bash-3.00$ strmqm qmgr2
WebSphere MQ queue manager 'qmgr2' starting.
5 log records accessed on queue manager 'qmgr2' during the log replay phase.
Log replay for queue manager 'qmgr2' complete.
Transaction manager state recovered for queue manager 'qmgr2'.
WebSphere MQ queue manager 'qmgr2' started.
Simply , noticed that new one is not letting to either create or start..
The queue manager does not exist.
Sometimes I got this error also while creating new QM.
Error : A WebSphere MQ installable service component could not be initialized. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Apr 24, 2009 7:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What version of WMQ?
What OS?
What database?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| beekumar |
| Posted: Mon May 11, 2009 11:37 am Post subject: |
|
|
Newbie
Joined: 24 Apr 2009
Posts: 8
|
WMQ 6.0
Solaris SUN SPARC
IBM DB2 v8.1
And FYI WMB 6.1
ODBC error is fixed by exporting LD_LIBRARY_PATH
But sometimes I am getting the MQ same errorunable to create.
MQ ErrorAMQ8101: WebSphere MQ error (893) has occurred.
and some times
A WebSphere MQ installable service component could not be initialized. |
|
| Back to top |
|
|
| beekumar |
| Posted: Wed May 20, 2009 7:04 am Post subject: Mq Error multiple errors while creating QM |
|
|
Newbie
Joined: 24 Apr 2009
Posts: 8
|
| Please, anyone help me in this out ??? |
|
| Back to top |
|
|
| harish_td |
| Posted: Wed May 20, 2009 8:23 am Post subject: |
|
|
Master
Joined: 13 Feb 2006
Posts: 236
|
There are have been many posts on this site about the 893 error. To re-iterate, please check the FDC for the Probe id. Most 893 errors are accompanied with an entry in the FDC's.
Among other causes it could also be due to a permissions issue for this user id from calling/ executing the required binaries. |
|
| Back to top |
|
|
| sumit |
| Posted: Wed May 20, 2009 8:26 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
How many queue managers are already there on the server?
I remember if you have 4 queue managers then in order to create another queue manager will need projadd details for mqm. But that's for Solaris 10. IS your Solaris 10 as well?
_________________
Regards
Sumit |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed May 20, 2009 9:54 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
it looks like something went terribly wrong in your infrastructure...
Check the FDC and error logs
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| beekumar |
| Posted: Thu May 21, 2009 5:52 am Post subject: |
|
|
Newbie
Joined: 24 Apr 2009
Posts: 8
|
Sumit, right now 4 qm's are there in server and ours is solrais 10 (5.10).
I remeber, created more than 5 qm's before. Onething what I noticed is applied fixpaks for OS later I restarted server then I started all services WAS, MQ, DB2. Then I tried to create qm, it went very well with out any errors. I thought somehow problem got fixed by restarting. Created and deleted qm's everything went fine. Later on tried to create qm and I got this same problem again. |
|
| Back to top |
|
|
| manicminer |
| Posted: Thu May 21, 2009 6:03 am Post subject: |
|
|
Disciple
Joined: 11 Jul 2007
Posts: 177
|
Does your machine have enough free resources to create the new queue manager?
e.g.
Enough disk space?
Enough memory?
Enough shared memory?
Enough of some other weird Solaris resource that is required?
If you are creating a lot of queue managers you may well run out of resources, and this may depend on how many queue managers are currently running, what they are currently doing, what other things are consuming resources on your box.
Any FDCs created when you try and do this? or errors in the logs?
_________________
Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime. |
|
| Back to top |
|
|
| beekumar |
| Posted: Thu May 21, 2009 7:23 am Post subject: |
|
|
Newbie
Joined: 24 Apr 2009
Posts: 8
|
This is the latest FDC when I tried to create QM.
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday May 21 11:05:53 EDT 2009 |
| Host Name :- BRAVO (SunOS 5.10) |
| PIDS :- 5724H7203 |
| LVLS :- 6.0.2.5 |
| Product Long Name :- WebSphere MQ for Solaris (SPARC platform) |
| Vendor :- IBM |
| Probe Id :- XY132002 |
| Application Name :- MQM |
| Component :- xstCreateExtent |
| SCCS Info :- lib/cs/unix/amqxstex.c, 1.83.1.10 |
| Line Number :- 536 |
| Build Date :- Sep 24 2008 |
| CMVC level :- p600-205-080922 |
| Build Type :- IKAP - (Production) |
| UserID :- 00001006 (mqm) |
| Program Name :- crtmqm |
| Addressing mode :- 64-bit |
| Process :- 25883 |
| Thread :- 1 |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (Failed to get memory segment: shmget(0x00146099, 8392704) [rc=-1 |
| errno=28] No space left on device) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 18446744073709551615 ffffffffffffffff |
| Arith2 :- 28 1c |
| Comment1 :- Failed to get memory segment: shmget(0x00146099, |
| 8392704) [rc=-1 errno=28] No space left on device |
| Comment2 :- No space left on device [/quote][/code][/url][/list] |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 21, 2009 7:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| beekumar wrote: |
| Comment1 :- Failed to get memory segment: shmget(0x00146099, |
| 8392704) [rc=-1 errno=28] No space left on device |
| Comment2 :- No space left on device |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sumit |
| Posted: Thu May 21, 2009 7:28 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| beekumar wrote: |
| I remeber, created more than 5 qm's before. |
On the same server?
Can you execute 'projects -l' and see if you are getting MQ related stanza. Cross check your values with IBM mannual if it's there.
| beekumar wrote: |
| | Comment1 :- Failed to get memory segment: shmget(0x00146099, | |
Here you go....
_________________
Regards
Sumit |
|
| Back to top |
|
|
| beekumar |
| Posted: Thu May 21, 2009 7:38 am Post subject: |
|
|
Newbie
Joined: 24 Apr 2009
Posts: 8
|
Yes Sumit it is on same server.
bash-3.00$ projects -l
system
projid : 0
comment: ""
users : (none)
groups : (none)
attribs:
user.root
projid : 1
comment: ""
users : (none)
groups : (none)
attribs:
noproject
projid : 2
comment: ""
users : (none)
groups : (none)
attribs:
default
projid : 3
comment: ""
users : (none)
groups : (none)
attribs:
group.staff
projid : 10
comment: ""
users : (none)
groups : (none)
attribs: |
|
| Back to top |
|
|
| beekumar |
| Posted: Thu May 21, 2009 7:43 am Post subject: |
|
|
Newbie
Joined: 24 Apr 2009
Posts: 8
|
|
| Back to top |
|
|
| beekumar |
| Posted: Thu May 21, 2009 9:38 am Post subject: |
|
|
Newbie
Joined: 24 Apr 2009
Posts: 8
|
Hi all,
First, Thanks for everybody for your quick response and also thanks for mqseries.net
Here my problem got resolved by giving following command:
projadd -c "WebSphere MQ default settings"
-K "process.max-file-descriptor=(basic,10000,deny)"
-K "project.max-shm-memory=(priv,4GB,deny)"
-K "project.max-sem-ids=(priv,1024,deny)"
-K "project.max-shm-ids=(priv,1024,deny)" group.mqm
Thanks Again,
beekumar |
|
| Back to top |
|
|
|
|
