Being very careful with production I would sort the dbdump message list and find the top message, dump it into a file and run it through the appropriate test tool. The problem message is probably one of the currently being processed messages. Then delete the bad one from the db, you still have it in a file to mess with later.