| Author |
Message
|
| koko |
 Posted: Wed Jun 22, 2005 11:58 am Post subject: [SOLVED] Any one here on AIX + MQWF 3.5 SP4 |
 |
|
Master
Joined: 26 Sep 2003
Posts: 206
|
Hi,
We were running wf 3.5 Sp2 fine and upgraded to 3.5 sp4. We are not able to start any new instances in WF.
We get the following error.
| Quote: |
FmcAssertionException, Condition=*** Pre-condition failed in /projects/fmc
/drv2/lbld/v350/aix/src/fmccdvmq.cxx(387): messageId.Length() == MQ_MSG_ID_LENGTH
|
_________________
Thanks
Koko
Last edited by koko on Thu Jul 28, 2005 6:17 pm; edited 1 time in total |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Jun 22, 2005 12:31 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I don't have any problems with SP4 on AIX
What patch level of MQ, DB2 and AIX are you at? |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Jun 22, 2005 1:00 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Koko: did you do the rebind after the upgrade?
I am running
FMC34154I: WebSphere MQ Workflow Version 3.5.0.4 is installed.
On windows, with no problems.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| hos |
| Posted: Wed Jun 22, 2005 10:06 pm Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Are you talking about XML API to create and start new instances?
The error seems to indicate some corruption in the MQ message.
Have you ensured that all fmc processes were stopped while you installed SP#4? |
|
| Back to top |
|
|
| koko |
| Posted: Thu Jun 23, 2005 7:10 am Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
we are on AIX 5.2 DB2 8.2.1 WF 3.5 SP2 /SP4
we shut down all workflow proceses. Ran both fmcclean, slibclean and followed the Readme VERBATIM.
We have some strange stuff going on our DB side. I am suspecting something on their side is causing this. I will update everyone with what I find.
_________________
Thanks
Koko |
|
| Back to top |
|
|
| supreeth |
| Posted: Thu Jun 23, 2005 10:54 pm Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi,
What is the DB2 version you are using.
I had installed DB2 8.2 and after that added FP 9. I did not do an update on the instance and hence i could not even issue "db2start".
Try downloading the readme for installing the fix pack. it has exact steps to be followed. I dont know how i can attach a file here. I have the file with me and can send it to you if you want 
As a summary, i can quote the instance update is necessary and also the re-bind of all the existing databases is a must.... else, it wont work
Thanks and Regards,
Supreeth |
|
| Back to top |
|
|
| koko |
| Posted: Mon Jun 27, 2005 6:42 am Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
Hi Supreeth,
We are not upgrading DB2. We are just upgrading WF from SP2 to SP4. I think you are referring to readme of DB2. I dont think we need to do any db2updt commands if we are not touching DB2 at all.
Right now we have a direction from IBM saying it might be the extended memory issue on both the mq and the database side.
_________________
Thanks
Koko |
|
| Back to top |
|
|
| supreeth |
| Posted: Mon Jun 27, 2005 10:33 pm Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi Koko,
I think this has gotta do with the OS EXTSHM issue. Try Applying
"HIPER APAR IY66127 (IY66147 on 5.3)", which will revert to the old behavior of EXTSHM.
This would help if this is an issue with the EXTSHM.
lemme kno if tis piece of information helps.
Thanks and Regards,
Supreeth |
|
| Back to top |
|
|
| koko |
| Posted: Tue Jun 28, 2005 3:27 am Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
Hi Supreeth,
We tried turning the EXTSHM variable in the userid profile (fmc) who starts the WF trigger monitor, changed the ThreadOfControl variable in qm.ini file for the Qmanager for workflow and retried it. But it didnt work.
The only thing that we still didnt do is bounce the Database on the database server with this env variable on.
| Quote: |
Try Applying
"HIPER APAR IY66127 (IY66147 on 5.3)", which will revert to the old behavior of EXTSHM
|
What you mean here?. Is this an APAR for MQ 5.3 or Is it for AIX OS?
Can you paste the link where you got this information please....
_________________
Thanks
Koko |
|
| Back to top |
|
|
| supreeth |
| Posted: Tue Jun 28, 2005 10:14 pm Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi Koko,
I am talkin about applying the OS patch "HIPER APAR IY66127", if your OS is AIX 5.2. The patch name would be "HIPER APAR IY66147" if your OS is AIX 5.3.
I got the information through mail. I shal let you know the link shortly.
Its basically related to the behavior of the system when you have the EXTSHM=ON in the environment.
I didn exactly get what do you mean by bouncing the database on the server and also why is it required.
Thanks and Regards,
Supreeth |
|
| Back to top |
|
|
| supreeth |
| Posted: Tue Jun 28, 2005 10:22 pm Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
|
| Back to top |
|
|
| koko |
| Posted: Thu Jul 28, 2005 6:17 pm Post subject: [SOLVED] |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
Hi there,
Just for information, it was a bug with SP4. We had IBM develop an APAR to fix our problem.
_________________
Thanks
Koko |
|
| Back to top |
|
|
|
|
