Read the db2diag.log file for problems. This should explain the dump.bin files. If the db2diag.log file is 1 GB after an hour, then you really ought to be reading what is in it. Also check your diaglevel DBM parameter. It should be 3.
I checked the DIAGLEVE and it is set to 3. I tar'd the db2diag.log up and will go through it but what about the locklist.txt. Is having a lot of these normal and does the DIAGLEVEL dictate the generation of locklist.txt?
I think I found the problem. The db2diag.log was filled with errors from the SAMPLE database which had crashed a couple of days ago and was corrupted. All the errors were from this database so I dropped that database and I will monitor the log files to make sure no other db is throwing off errors.