DB2 TSM backup hung, how to take back control?

[yoyo]

So I get a call from my customer this morning, he tells me the database
has hung during the TSM backup and nobody can connect.
After tyring a few things, I resorted to db2_kill, and db2start.
I don't feel this was the best solution, but since the database was in
quiesce'd mode there wasn't much else I could think of off hand.

I'm not the guy who wrote the backup routine, but he quiesce's it, then
backups it up and then unquiesce's it. db2 force applications doesn't
work it just says the db is in use and no connection can be made.
db2stop obviously doesn't work for the same reasons. trying an unquiesce
doesn't work, it requires a connection first, which obviously could not
be obtained.
Is there a better way than db2_kill. I knew there was a good backup from
Friday, and few people work on the weekend, so I was confident if the
db was lost we had everything we needed. db2_kill worked, but I'm pretty
sure there was a better way to get it back without killing it off?

Ken

[Ian]

yoyo wrote:

So I get a call from my customer this morning, he tells me the database
has hung during the TSM backup and nobody can connect.
After tyring a few things, I resorted to db2_kill, and db2start.
I don't feel this was the best solution, but since the database was in
quiesce'd mode there wasn't much else I could think of off hand.

I'm not the guy who wrote the backup routine, but he quiesce's it, then
backups it up and then unquiesce's it. db2 force applications doesn't
work it just says the db is in use and no connection can be made.
db2stop obviously doesn't work for the same reasons. trying an unquiesce
doesn't work, it requires a connection first, which obviously could not
be obtained.
Is there a better way than db2_kill. I knew there was a good backup from
Friday, and few people work on the weekend, so I was confident if the
db was lost we had everything we needed. db2_kill worked, but I'm pretty
sure there was a better way to get it back without killing it off?

Yes, have the TSM administrator kill the session.

The TSM Admin would also be helpful in telling you *why* the backup
was hung (i.e. was it waiting for a tape mount, etc.)

[yoyo]

Ian wrote:

yoyo wrote:

So I get a call from my customer this morning, he tells me the
database has hung during the TSM backup and nobody can connect.
After tyring a few things, I resorted to db2_kill, and db2start.
I don't feel this was the best solution, but since the database was in
quiesce'd mode there wasn't much else I could think of off hand.

I'm not the guy who wrote the backup routine, but he quiesce's it,
then backups it up and then unquiesce's it. db2 force applications
doesn't work it just says the db is in use and no connection can be
made. db2stop obviously doesn't work for the same reasons. trying an
unquiesce doesn't work, it requires a connection first, which
obviously could not be obtained.
Is there a better way than db2_kill. I knew there was a good backup
from Friday, and few people work on the weekend, so I was confident
if the db was lost we had everything we needed. db2_kill worked, but
I'm pretty sure there was a better way to get it back without killing
it off?

Yes, have the TSM administrator kill the session.

The TSM Admin would also be helpful in telling you *why* the backup
was hung (i.e. was it waiting for a tape mount, etc.)

Yeah, they are "working" on that. No answer yet.

[Mark Yudkin]

We've had this too. I don't remember the PMR number I'm afraid, but you
should contact support as there is a resolution for this problem. I do not
recall if the fix is in DB2 or in TSM, but we reported it against DB2.

"yoyo" <yo**@ma.com> wrote in message
news:7K******************************@centurytel.n et...

So I get a call from my customer this morning, he tells me the database
has hung during the TSM backup and nobody can connect.
After tyring a few things, I resorted to db2_kill, and db2start.
I don't feel this was the best solution, but since the database was in
quiesce'd mode there wasn't much else I could think of off hand.

I'm not the guy who wrote the backup routine, but he quiesce's it, then
backups it up and then unquiesce's it. db2 force applications doesn't work
it just says the db is in use and no connection can be made. db2stop
obviously doesn't work for the same reasons. trying an unquiesce doesn't
work, it requires a connection first, which obviously could not be
obtained.
Is there a better way than db2_kill. I knew there was a good backup from
Friday, and few people work on the weekend, so I was confident if the db
was lost we had everything we needed. db2_kill worked, but I'm pretty sure
there was a better way to get it back without killing it off?

Ken