| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WebSphere MQ V5.3 install on Solaris 5.9 |
« View previous topic :: View next topic » |
| Author |
Message
|
| rcrippen |
 Posted: Sun Mar 28, 2004 5:05 pm Post subject: WebSphere MQ V5.3 install on Solaris 5.9 |
 |
|
Apprentice
Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY
|
I have a client who is trying to create a queue manager on a Solaris 5.9 box. The client has confirmed that all the KERNEL parameters are set properly. The box does not have a database on it but it is getting a shmget failed to get memory segment error. I am including the top section of one of the FDC files that they are getting.
Has anyone got any gotchas for installing and creating with Solaris 5.9 that I can look at?
Thanks for any assistance.
Rob Crippen
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday March 25 13:47:15 EST 2004 |
| Host Name :- nyppldev15 (SunOS 5.9) |
| PIDS :- 5724B4103 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- XY132002 |
| Application Name :- MQM |
| Component :- xstCreateExtent |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000998 (root) |
| Program Name :- crtmqm |
| Process :- 00006944 |
| Thread :- 00000001 |
| 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(0x00013c26, 8323072) [rc=-1 |
| errno=22] Invalid argument) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 4294967295 ffffffff |
| Arith2 :- 22 16 |
| Comment1 :- Failed to get memory segment: shmget(0x00013c26, |
| 8323072) [rc=- |
| Comment2 :- Invalid argument |
| |
| |
+-----------------------------------------------------------------------------+
[/img] |
|
| Back to top |
|
 |
| kman |
| Posted: Sun Mar 28, 2004 11:24 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
Your customer may have set the kernel wrongly. Could be a mispelled somewhere. Check if they had use semsys instead of shmsys on the shmmni.
This is the correct one,
| Quote: |
set shmsys:shminfo_shmmni |
because the list of parameters in the manual may have been read wrongly.. or keyed in wrongly. I had the same experience.  |
|
| Back to top |
|
|
| rcrippen |
| Posted: Tue Mar 30, 2004 12:38 pm Post subject: |
|
|
Apprentice
Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY
|
kman,
Thanks for your suggestion. You were right on. The client had a list of KERNEL parameters that were for running on an INTEL CPU instead of a SPARC.
They changed the parameters and have created the queue manager.
Thanks again,
Rob :wink: |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
