| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Start faild after patching Solaris |
« View previous topic :: View next topic » |
| Author |
Message
|
| Magneto |
 Posted: Wed Aug 13, 2008 6:01 am Post subject: Start faild after patching Solaris |
 |
|
Newbie
Joined: 13 Aug 2008
Posts: 2
|
Hi at all,
My MQ Version:
Name: WebSphere MQ
Version: 530.10 CSD10
CMVC level: p530-10-L050504
BuildType: IKAP - (Production)
Operationsystem: (uname -a)
SunOS XXXXXXX 5.10 Generic_137111-04 sun4u sparc SUNW,Sun-Fire-V490
here my problem during start up MQ 5.3 on Solaris 10 (sparc) after patch the system with required patches by SUN:
strmqm return my: strmqm rc(71) - AMQ5615: Default objects cannot be created: CompCode = 0 Reason = 0
When i try to create a new queue Manager with crtmqm it return only "Bus Error" the RC is 138 (not specified error).
When i turn back the patch level to older version (SunOS XXXXXX 5.10 Generic_127111-05 sun4u sparc SUNW,Sun-Fire-V490) there no problem / errors occurred while start the same installation from MQ.
First i think i can solve the probelm with latest FixPack (CSD) 14, but this shows no effekt 
I try also crtmqm with truss:
Here come the end of the output:
/1: chmod("/var/mqm/qmgrs/TRY3!QM/shmem/shm.1", 0660) = 0
/1: stat("/var/mqm/qmgrs/TRY3!QM/shmem/shm.1", 0xFFBFCB98) = 0
/1: shmget(7951940, 159744, 0660|IPC_CREAT|IPC_EXCL) = 28
/1: shmat(28, 0, SHM_RND) = 0xFE930000
/1: getuid() = 700 [700]
/1: Incurred fault #5, FLTACCESS %pc = 0xFEB2F040
/1: siginfo: SIGBUS BUS_ADRALN addr=0xFE01A3DC
/1: Received signal #10, SIGBUS [caught]
/1: siginfo: SIGBUS BUS_ADRALN addr=0xFE01A3DC
/1: setcontext(0xFFBFC5C0)
/1: Incurred fault #5, FLTACCESS %pc = 0xFEB2F040
/1: siginfo: SIGBUS BUS_ADRALN addr=0xFE01A3DC
/1: Received signal #10, SIGBUS [default]
/1: siginfo: SIGBUS BUS_ADRALN addr=0xFE01A3DC
Any ideas but no upgrade to newer version are welcome.
A case to SUN is open, but SUN told me: "Please ask IBM for an analysis of the core. The command receives the SIGBUS, because a userland address it computed was not valid. Only IBM can analyze this."
Thanks in advance |
|
| Back to top |
|
 |
| David.Partridge |
| Posted: Wed Aug 13, 2008 6:26 am Post subject: |
|
|
Master
Joined: 28 Jun 2001
Posts: 249
|
So, do you have an extended support contract for MQ 5.3 with IBM?
If you do, open a PMR.
If not then you are SOL as 5.3 is now out of support unless you have an extended support deal.
If the latter case holds you only have two options:
1. Run without the Solaris patches.
2. Upgrade to MQ 6 or MQ 7
_________________
Cheers,
David C. Partridge |
|
| Back to top |
|
|
| SAFraser |
| Posted: Mon Aug 18, 2008 7:11 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I, myself, never tried MQ 5.3 on Solaris 10. I do not recollect if it was a supported platform for 5.3.
If your site is willing to go to Solaris 10, surely you can get them to agree to MQ 6.0 !! |
|
| Back to top |
|
|
| Magneto |
| Posted: Tue Aug 26, 2008 12:07 am Post subject: |
|
|
Newbie
Joined: 13 Aug 2008
Posts: 2
|
Thank at all 
we install now MQ 6 on our Solaris 10 Systems |
|
| Back to top |
|
|
| veech23 |
| Posted: Tue Aug 26, 2008 3:20 pm Post subject: |
|
|
Novice
Joined: 25 Apr 2007
Posts: 23
Location: canberra
|
| have you tried strmqm -c which will recreate default objects? this will fix the startup issue but there is an inherent problem in losing data in those default objects. |
|
| 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
|
|
|
|
