| Author |
Message
|
| zigeesha |
 Posted: Tue Mar 15, 2005 11:41 am Post subject: WebSphere MQ error (893) on solaris |
 |
|
Apprentice
Joined: 16 Aug 2004
Posts: 32
Location: california
|
Hi all,
I have installed MQ 5.3.0.7 on Solaris 9, created a queue manager qm.sun.s01 and have been working on it for a while.
I used the kill -9 command to stop the queue manager and since then i have not been able to access most of the commands from the
/opt/mqm/bin directory
when i try runmqsc qm.sun.s01 the following error shows up
AMQ8135: Not authorized
when i try dspmqaut it says
WebSphere MQ error (893)
i have tried logging in as the root as well as mqm user
Plz suggest |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Mar 15, 2005 2:11 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Any *.FDC files in the errors subdirectories? Have you recycled the machine? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Mar 15, 2005 3:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Any processes still running for the qmgr you killed?
Any shared memory still busy ? (amqiclen)
Any process still having a hold on the qmgr (typical WAS MDBs) ?
If you try to restart the qmgr do you get a message with pid # mentionned ?
You should not use kill -9 to shutdown a qmgr (way to many processes involved)
Try and use first endmqm -i -m QMGR
and if that does not work
endmqm -p -m QMGR
Enjoy  |
|
| Back to top |
|
|
| zigeesha |
| Posted: Tue Mar 15, 2005 4:12 pm Post subject: |
|
|
Apprentice
Joined: 16 Aug 2004
Posts: 32
Location: california
|
When i start the queue Manager it doesn't shown a PID #
just says Queue Manager started..
I have rebooted the m/c
The *.FDC files say itz a MQRC_SECURITY_ERROR
Still i have no progress.. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Mar 15, 2005 8:57 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
I had 893 on Solaris (MQ v5.3 CSD08) recently and I could not find a way to fix it.
Basically, I deleted the queue manager and then recreate it. Good thing we run MS03 every night. Hence, I could quickly get all queues & channels recreated. Of course, the messages were lost. 
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| xxx |
| Posted: Fri Mar 18, 2005 12:07 pm Post subject: |
|
|
Centurion
Joined: 13 Oct 2003
Posts: 137
|
Check the ulimit -a ,
and the kernal parmeters |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 18, 2005 11:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Sounds like a file permission to me . Somewhere on the file system the owner and / or group are not mqm where they need to be.
Enjoy |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Sat Mar 19, 2005 9:08 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
As explained by IBM, the queue manager has corrupted its own log file(s), hence, there isn't much you can do (other than rebuild the queue manager).
xxx, what exactly should the person be looking for? 'Check the ulimit -a for what? Which value may be wrong/incorrect/too high/too low ??
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| xxx |
| Posted: Wed Mar 23, 2005 8:15 pm Post subject: |
|
|
Centurion
Joined: 13 Oct 2003
Posts: 137
|
I get this error most often ,
Please check the solaris Quick beginings , for the /etc/system parameters ,
Ulimit check for the file discriptors |
|
| Back to top |
|
|
|
|
