We just had Lawson finish the install of LSF9 on our separate sever upgrade from 8.0.3 to LSF9. We are on AIX.
First problem didn't take long to find. We found db2fm using a lot of CPU. We used the shutdown/startup from the knowledgebase, (wouldn't expect the Lawson installer to share that info), and now we have 2 db2fm running and our system is crawling.
Lawson says to upgrade Tivoli from 6.0.0.41 to 6.0.0.5 as per critical notification on 11/16/07. Apparently the installer didn't find this to be critical? But ok, if that's what it takes. While waiting, I found a KB article, 558831, that says for thie db2fm problem, upgrade db2 with APAR IY64683, which is very messy, or apply FP 14. I mentioned this to Lawson support, and they said, "Yes, do that too".
Ok, I'm disgusted that they overlooked that, but that's not unusual. But, I'm trying to find out, has anyone had this problem? Is all this necessary? Is there a more direct fix?
Additonally, for anyone running LSF9 on AIX, should we look at a separate sever for Tivoli LDAP? Is this going to be a recurring issue?
Thanks.
You're scaring me. We're about to start our LSF9 installs on Monday on our new AIX box. I hope our installer has more up-to-date info than yours did. Ours will be all on one box, sorry I can't help in your situation. We're going with WAS 6.1 and TDS 6.1 so hopefully we'll skip your issues. Was TDS 6.1 an option for you?
-GW
Known bug in the DB2 Fault Monitor. Tivoli and DB2 need patching. The short term work-around is to edit initab and change the db2fm command from respawn to once and then kill and refresh it. Do the same on reboot and refreshes.
Just in case, you can ask them about it Greg. If they don't know (and they may not) let me know and I'll find the patch info for you.