DB2 ESE 9.5 fp8 on p-linux
started an online backup this morning at 03.00 and was ended at 5.00 because of tsm problem and could not retrieve log
the script starts an online backup to disk : 05.00
this backup seems to be present in application list and utilities but not doing anything. backup file size does not change anymore.. since 1h
we killed the process that started the backup script and now try to force the application belonging to the backup..
we see an entry in diag, but db2bp process performing a backup is still present..
we can connect and use to db. the only thing i wonder is, what will happen this night if a new backup is started ??
we can not stop the instance (prod with 12 db)..
any idea on this ??

Do you see latches ?
Are you able to tie back the latch to a specific EDU?
This may provide more insight to take corrective action.

If the backup starts again, I assume you will get "A backup already in progress" message. Not sure though.

thanks for the update
we see many latches 0x00000000100C7650 1781 0 sqlofmga.C 1683 SQLO_LT_sqlofmga_C__SQLO_TLFL_m_fileLatch
0x0000040092EA167C 5321 0 sqlpxreg.C 733 SQLO_LT_SQLP_TENTRY__applLatch
I presume the file* are for containers
the other latches are appearing and dis-app.
in the mean time I phoned IBM and they recommend to kill the process belonging to db2vend - because db2 is waiting for tsm to receive backup status and do cleanup
we will try todo this later today - because some pmr indicate a db2 crash when killing this process - although another note indicates this should not happen anymore in 9.5