repairdb does not fix problem with oops error on login

I recently updated my version of OpManager to 8.1.0.8810. Since then I haven't been able to get into the web interface and always get the error ' Oops looks like a few tables got corrupted. Don't worry.. Run RepairDB.bat from bin directory and restart the server'. Although I've run the repairdb and restarted the server a number of times, I'm still unable to login to OpManager. The service seems to be running alright as I have gotten a few alerts via email when the service is running, but that hardly helps me when I can't login to see what's going on.

I've followed the directions in the post ' Possible solution on Oops... ... Run repairDB.bat', but that hasn't helped me either. Pretty much at a loss at this point and need some help.

If you need logs, I need to know if you want the old logs before I changed the log folder name or the new logs.

Thank you in advance for your help.