DB2ATS + Transaction log full + backup fails

I had the backup team contact me because a backup had failed because of a transaction log full.

when I investigated this transaction log issue, the connection was held by a job launch by the DB2ATS ( db2 automatic task scheduler )

I tried to follow the action suggested in the db2diag.log trying to force the connection mentioned there,
but for some reason you are not allowed to force ATS connections ( I feel this is not good , If I decide to kill a connection it's my responsibility :)).

I tried deactivating the automated task scheduler using db2set

db2set DB2_ATS_ENABLE=NO

however this did not solve my problem,

after some time I decided to see if db2pd could help me,
and rememberd some searches we did in the past for deadlatch situations when a database was hanging,
the database was actually hanging but I was out of options.

so I launched db2pd -latches
and I saw a huge list of latches:

all of them of this type:
SQLO_LT_sqlerFmpRow__ipcLatch

I did a search on google an luckily a support link came out;
IC76825: THREADED DB2FMP PROCESS LOOPS IN ITS SIGNAL HANDLER WHEN IT RECEIVES NESTED SIGNALS

in there they said to check for a db2fmp process consuming CPU,

so I did a ps -ef | grep db2fmp | grep <instance owner>

and then did a db2fmpterm <pid of the db2fmp of my instance>

after this the database got into a more normal state, all of the latches had dissappeared,
and backup worked as it should ...