Yes, I had this issue too. I had an upgrade that stalled out but some of the tables were created and when I tried it again, I got that error.
Basically, for each table (there were three offenders in my case all to do with event monitoring), go into your database and rename those tables to something else (add old at the end of the name worked well for me). Then rerun the upgrade. It took a few attempts for me because it took three tries to get all three offending tables listed. Once I knew which ones they were, I was able to rename them all and then the upgrade ran successfully. After I checked everything was working correctly, I deleted the "old" tables and the site was good to go.