Re: MYSQL error requires IPL

Hi Dale,

I've been following this thread, and I'm going to wager a guess that the
problem you hit with the PID file being "in use" had nothing to do with
MySQL (or PHP or Apache). MySQL just happened to be in the wrong place at
the wrong time and stumbled over a bug in the OS.

The symptoms that you've described sound very similar to an issue that was
discovered internally recently in the IBM lab and that has its roots deep
in the IFS. There are PTFs for 6.1 (MF46884) and 6.1.1 (MF46740), and a
v5r4 fix is in the works. Without being able to diagnose your system in
its problem state, I can't be certain that you hit the same problem
corrected by these PTFs, but it does sound pretty suspicious. It's
unfortunate that IBM support didn't pursue this further, since a failure
to delete a streamfile because of being "in use" when the only programs
using it have been ended is, in my opinion, strongly indicative of an OS
bug.

Thanks
Tim Clark

date: Thu, 29 Oct 2009 14:19:34 -0400
from: dale janus <dalejanus@xxxxxxxxxxxxxxxxx>
subject: [WEB400] MYSQL error requires IPL

Matt,

I'm sorry I was not clear.
The file we could not delete was not a database table but a MYSQL
system file, a .PID file that MYSQL needed to create when it started up.
We tried to get it to create a .PID file with another name, but got
a different error. It appears that MYSQL wants its 'stuff' exactly
where it wants it to be with exactly the name it wants to call it.

---Dale

The table we were trying to modify was created with the MYISAM

engine,

not the IBMDB2I engine.

Interesting. I assume that means the file lock issue is only a

problem

when using something other than the IBMDB2I? Another reason to stick

with

IBMDB2I I suppose.