| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problems installing Fix Pack 6.0.2.6 |
« View previous topic :: View next topic » |
| Author |
Message
|
| rickwatsonb |
 Posted: Tue Jun 23, 2009 6:50 am Post subject: Problems installing Fix Pack 6.0.2.6 |
 |
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
Hi,
We recently did our first fix pack install for MQ fix pack 6.0.2.6 on Sun Solaris 10 (6.0.2.0 to 6.0.2.6). I am able to create a new queue manager but it fails to start.
I can see that the problem is due to incorrect symbolic links in the bin directory and lib directory. For example, instead of amqzxma0 -> /opt/mqm/bin/amqzxma0_nd we have amqzxma0 -> /tmp/opt/mqm/bin/amqzxma0_nd (directory info is also shwn below).
The install was done from a directory in /tmp. I have not seen anything in the documentation specifying that the install must be done from a specific directory. Please advise. Thanks for your help.
brgede001:/var/mqm/errors>dspmqver
Name: WebSphere MQ
Version: 6.0.2.6
CMVC level: p600-206-090217
BuildType: IKAP - (Production)
brgede001:/var/mqm>crtmqm TEST.QMGR2
WebSphere MQ queue manager created.
brgede001:/var/mqm>dspmq
QMNAME(TEST.QMGR2) STATUS(Ended normally)
brgede001:/var/mqm>strmqm TEST.QMGR2
An unexpected error was encountered by a command.
The FDC file shows (partial display):
…
| UserID :- 00000200 (mqm)
| Program Name :- strmqm
| Addressing mode :- 64-bit
| Process :- 5789
| Thread :- 1
| QueueManager :- TEST.QMGR2
| Last HQC :- 0.0.0-0
| Last HSHMEMB :- 0.0.0-0
| Major Errorcode :- xecP_E_PGM_NOT_FOUND
| Minor Errorcode :- OK
| Probe Type :- MSGAMQ6025
| Probe Severity :- 2
| Probe Description :- AMQ6025: Program not found.
| FDCSequenceNumber :- 0
| Arith1 :- 2 2
| Comment1 :- No such file or directory
| Comment2 :- /opt/mqm/bin/amqzxma0
Log:
EXPLANATION:
WebSphere MQ is unable to start program No such file or directory because it
was not found.
ACTION:
Check the program name is correctly specified and rerun the program.
----- amqxfdcx.c : 768 --------------------------------------------------------
06/23/09 10:03:22 - Process(5789.1) User(mqm) Program(strmqm)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
TEST.QMGR2.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 5789.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 807 --------------------------------------------------------
06/23/09 10:03:22 - Process(5789.1) User(mqm) Program(strmqm)
AMQ6025: Program not found.
bin
brgede001:/opt/mqm>cd bin;ll (note: not all files displayed (…))
total 12006
dr-xr-xr-x 2 mqm mqm 2048 Jun 8 18:21 .
drwxr-xr-x 12 root root 512 May 2 2008 ..
lrwxrwxrwx 1 root root 25 Dec 5 2008 amqcctca -> /tmp/opt/mqm/lib/amqcctca
lrwxrwxrwx 1 root root 25 Dec 5 2008 amqcltca -> /tmp/opt/mqm/lib/amqcltca
lrwxrwxrwx 1 root other 28 Dec 5 2008 amqcrs6a -> /tmp/opt/mqm/bin/amqcrs6a_nd
-r-sr-sr-x 1 mqm mqm 18720 Feb 17 19:15 amqcrs6a_nd
lrwxrwxrwx 1 root other 28 Dec 5 2008 amqcrsta -> /tmp/opt/mqm/bin/amqcrsta_nd
-r-sr-s--- 1 mqm mqm 20448 Feb 17 19:14 amqcrsta_nd
…
-r-sr-sr-x 1 mqm mqm 23896 Feb 17 19:18 amqxmsg0
-r-sr-s--- 1 mqm mqm 215896 Feb 17 19:14 amqzdmaa
-r-sr-s--- 1 mqm mqm 101288 Feb 17 19:19 amqzfuma
lrwxrwxrwx 1 root other 28 Dec 5 2008 amqzlaa0 -> /tmp/opt/mqm/bin/amqzlaa0_nd
-r-sr-s--- 1 mqm mqm 430472 Feb 17 19:06 amqzlaa0_nd
-r-sr-s--- 1 mqm mqm 20936 Feb 17 19:07 amqzllp0
lrwxrwxrwx 1 root other 28 Dec 5 2008 amqzlsa0 -> /tmp/opt/mqm/bin/amqzlsa0_nd
-r-sr-s--- 1 mqm mqm 412552 Feb 17 19:07 amqzlsa0_nd
-r-sr-s--- 1 mqm mqm 30168 Feb 17 19:18 amqzlwa0
…
lrwxrwxrwx 1 root other 28 Dec 5 2008 amqzxma0 -> /tmp/opt/mqm/bin/amqzxma0_nd
...
lib
brgede001:/opt/mqm>cd lib;ll (note: not all files displayed (…))
total 33766
dr-xr-xr-x 3 mqm mqm 1024 Jun 8 18:21 .
drwxr-xr-x 12 root root 512 May 2 2008 ..
-r-sr-sr-x 1 mqm mqm 176892 Feb 17 19:04 amqcc62a
…
lrwxrwxrwx 1 root root 25 Dec 5 2008 amqzfu -> /tmp/opt/mqm/lib64/amqzfu
-r-xr-xr-- 1 mqm mqm 55948 Feb 17 19:04 amqzsc
... |
|
| Back to top |
|
 |
| rickwatsonb |
| Posted: Tue Jun 23, 2009 11:38 am Post subject: |
|
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
Hi,
I am going to give feedback to my own question, so please do not spend time on this question if you agree with my suggestion.
I think it would be best if we did a re-install of MQ and then applied the fix pack. We are working on a lower environment server that has not had any active queue managers for quite some time. I can now see that the bad symbolic links were created a while ago and are not relative to applying the fix pack. Sorry I did not see this before creating the post!
I am not sure how the bad links were created - I was out that day in December! |
|
| Back to top |
|
|
| rickwatsonb |
| Posted: Wed Jun 24, 2009 7:46 am Post subject: |
|
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
As a second follow up to my own post:
Our server admin has confirmed the following: /opt/mqm files were restored, however, the links were not restored properly and broke after reboot. The links have been fixed.
Thus, it now looks like a re-install of MQ will not be necessary.
We will proceed with the MQ fix pack install in the next couple of weeks, as time permits. If there are any more problems, relative to this post, I will add comments. |
|
| 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
|
|
|
|
