Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Andrzejek on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
db2fmp gone mad
- Thread starter martynh
- Start date
gregsimpson
Programmer
- Apr 18, 2002
- 521
It's the fault manager process. Check the usual things such as the db2diag and the .nfy for any reported problems.
Cheers
Greg
Cheers
Greg
- Thread starter
- #3
I thought that too. However, there's nothing in these to suggest a problem.
The rate that the process is burning cpu cycles I don't think it's on speaking terms with the rest of the server. I've rebooted the server and on reboot all looks quiet, so I'll watch it now.
I've also opened a PMR and I'll post how I get on.
The rate that the process is burning cpu cycles I don't think it's on speaking terms with the rest of the server. I've rebooted the server and on reboot all looks quiet, so I'll watch it now.
I've also opened a PMR and I'll post how I get on.
ionobelisk
Programmer
Hi,
db2fmp is not the fault manager, it's the fenced mode processor. If a db2fmp is eating processor/memory, it probably means that you've got a truly horrible stored procedure executing against the database, or one that's been fed with "the query from hell".
Cheers
ChrisW
db2fmp is not the fault manager, it's the fenced mode processor. If a db2fmp is eating processor/memory, it probably means that you've got a truly horrible stored procedure executing against the database, or one that's been fed with "the query from hell".
Cheers
ChrisW
gregsimpson
Programmer
- Apr 18, 2002
- 521
ionobelisk,
nice spot. I'll double check everything my IBM consultant tells me from now on. We've had problems with this and what you've said backs up what I've seen as regards 1 and only stored procedure, which we run.
Greg
nice spot. I'll double check everything my IBM consultant tells me from now on. We've had problems with this and what you've said backs up what I've seen as regards 1 and only stored procedure, which we run.
Greg
- Thread starter
- #6
I'd forgotten about this. For the sake of anyone finding this in the future, the problem did not recur on the original (single DB2 instance) server. However, it did recur on another. What was spooky was that on the second server it happened with both instances that were running there. This makes me think it was related to a DB2 upgrade and that it happened once per instance just after an upgrade. IBM support simply said watch it and see if it happens again.
- Status