| Author |
Message
|
| satya_jammy |
 Posted: Mon Nov 09, 2009 10:02 am Post subject: |
 |
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
yes i agree with you and i already insisted my client to upgrade .but that is a long process. Now my concentration is what is casuing this failure.. is the OS version 5.8 causing the failure.. 
if i apply fixpack CSD 14 for this server do i also need to apply tfixpack to all the clients that are currently using this server? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Nov 09, 2009 10:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| satya_jammy wrote: |
| is the OS version 5.8 causing the failure.. |
Only IBM (via a PMR) could say for sure. Unless you have extended support you can't raise a PMR. If you do have extended support, you should already have raised a PMR.
| satya_jammy wrote: |
| if i apply fixpack CSD 14 for this server do i also need to apply tfixpack to all the clients that are currently using this server? |
Probably not, but I'd hate to rely on that statement in production.
| satya_jammy wrote: |
| i already insisted my client to upgrade .but that is a long process |
It's been a long time since v5.3 went out of support and even longer since CSD07 was a good idea. Your client has had plenty of time to deal with this.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Nov 09, 2009 10:11 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
As Vitor stated, it may do no harm, but it may not 'fix' the problem either. In regard to applying the same fix level to the clients, the same caveat applies - it may be OK, but it may not.
If your client has been unwilling to upgrade the middleware, against best advice, well, they are now harvesting the results of that decision. I have recently been in the position where the only way I could get WMQ to work on a 'rebuilt' server was to go to a later version - an OS patch had completely broken the base code.
This has now wonderfully focussed the client as they in are the dilemma of applying the same OS patch in Production, thereby potentially losing the infrastructure, but they don't want to upgrade the middleware because the system may be replaced in 6 months, but the OS patch is security related and has to be implemented.
_________________
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 |
|
|
| satya_jammy |
| Posted: Tue Nov 10, 2009 5:18 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
i have installed the fixpack CSD 14...But the Qmanagers are not getting started and even unable to create a New Qm.  |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Nov 10, 2009 5:49 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Any FDC's? Anything in the queue manager logs? Anything in the Sys Logs? Throw us a bone here, we're trying to help 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 |
|
|
| satya_jammy |
| Posted: Tue Nov 10, 2009 7:12 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
these are the fdcs getting generated while i attempting to start or create a new QM
-----------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Tuesday November 10 07:58:53 MST 2009 |
| Host Name :- wcdevtst (SunOS 5.8) |
| PIDS :- 5724B4103 |
| LVLS :- 530.14 CSD14 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- XC303040 |
| Application Name :- MQM |
| Component :- xlsCreateMutex |
| Build Date :- Dec 15 2007 |
| CMVC level :- p530-14-L071214 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000104 (mqm) |
| Program Name :- amqzxma0_nd |
| Process :- 00029206 |
| Thread :- 00000001 |
| Major Errorcode :- Unknown(16) |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ0016 |
| Probe Severity :- 4 |
| Probe Description :- AMQ6090: WebSphere MQ was unable to display an error |
| message 16. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
07:10:50.508428 16378.1 | |
07:10:50.508475 16378.1 | WebSphere MQ First Failure Symptom Report |
07:10:50.508521 16378.1 | ========================================= |
07:10:50.508568 16378.1 | |
07:10:50.508614 16378.1 | Date/Time :- Tuesday November 10 07:10:50 MST 2009 |
07:10:50.508660 16378.1 | Host Name :- wcdevtst (SunOS 5.8) |
07:10:50.508706 16378.1 | PIDS :- 5724B4103 |
07:10:50.508754 16378.1 | LVLS :- 530.14 CSD14 |
07:10:50.508800 16378.1 | Product Long Name :- WebSphere MQ for Sun Solaris |
07:10:50.508846 16378.1 | Vendor :- IBM |
07:10:50.508892 16378.1 | Probe Id :- XY398005 |
07:10:50.508939 16378.1 | Application Name :- MQM |
07:10:50.508985 16378.1 | Component :- xcsFreeMemBlock |
07:10:50.509031 16378.1 | Build Date :- Dec 15 2007 |
07:10:50.509078 16378.1 | CMVC level :- p530-14-L071214 |
07:10:50.509123 16378.1 | Build Type :- IKAP - (Production) |
07:10:50.509170 16378.1 | UserID :- 00000104 (mqm) |
07:10:50.509216 16378.1 | Program Name :- crtmqm |
07:10:50.509262 16378.1 | Process :- 00016378 |
07:10:50.509308 16378.1 | Thread :- 00000001 |
07:10:50.509354 16378.1 | Major Errorcode :- STOP |
07:10:50.509400 16378.1 | Minor Errorcode :- OK |
07:10:50.509446 16378.1 | Probe Type :- HALT6109 |
07:10:50.509492 16378.1 | Probe Severity :- 1 |
07:10:50.509539 16378.1 | Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
07:10:50.509585 16378.1 | FDCSequenceNumber :- 1 |
07:10:50.509632 16378.1 | Comment1 :- Failed to match eyecatcher on start memory CB during |
07:10:50.509678 16378.1 | free. |
07:10:50.509724 16378.1 | |
07:10:50.509770 16378.1 +-----------------------------------------------------------------------------+
07:10:50.509814 16378.1
i am observing this below error in the trace files
msgid:00000016 a1:00000000 a2:00000000 c1:(null) c2:(null) c2:(null)
07:10:41.623538 16361.1 Opened msg cat /usr/lib/locale/C/LC_MESSAGES/amq.cat
07:10:41.623659 16361.1 -------{ xcsQueryCCSIDType
07:10:41.623706 16361.1 -------}! xcsQueryCCSIDType rc=xecC_E_NOT_INIT
07:10:41.623755 16361.1 Failed to extract message 0x16 from catalog. catgets errno=35 07:10:41.624291 16361.1 ------}! xcsGetMessage rc=xecE_W_DEFAULT_TEXT_SUBSTITUTED
07:10:41.624350 16361.1 ------{ xcsQueryDateTime2
07:10:41.624402 16361.1 -------{ xcsLocaltime |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Nov 10, 2009 7:27 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Google the Probe ID, see if the hit is relevant to your issue...
_________________
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 |
|
|
| satya_jammy |
| Posted: Tue Nov 10, 2009 12:36 pm Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
| Any other suggestions by observing those FDC's? |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Nov 10, 2009 12:40 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| satya_jammy wrote: |
| Any other suggestions by observing those FDC's? |
Other than you reading it and seeing if it's applicable to you? No...
_________________
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 |
|
|
| satya_jammy |
| Posted: Wed Nov 11, 2009 10:35 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
i am trying to install freshly MQ5.3 on the new server i have got the mq5.3
software file C48UHML.tar up on extracting i got the files
-rwxr-xr-x 1 226 12201 3476 Jan 10 2003 mqlicense.sh
-r--r--r-- 1 10273 12201 14240 Jan 10 2003 readme
drwxr-sr-x 2 226 12201 1024 Jan 31 2003 licenses
drwxr-sr-x 2 226 12201 512 Jan 31 2003 silent
drwxr-sr-x 4 226 12201 512 Jan 31 2003 mqm
drwxr-sr-x 4 226 12201 512 Jan 31 2003 gsk6bas
drwxr-sr-x 4 226 12201 512 Jan 31 2003 lap
drwxr-sr-x 14 226 12201 512 Jan 31 2003 READMEs
i am not finding any .img file to start my installation... i have read the Quick beginings it is showing the instruction installing from the CDROM..But how i can install with those available files from the directory using pkgaddd? |
|
| Back to top |
|
|
| satya_jammy |
| Posted: Wed Nov 11, 2009 12:03 pm Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 11, 2009 12:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Though ironically enough these instructions are for v6, not the out of support v5.3 you're trying to install.
The pkgadd command doesn't vary though.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
