Yesterday I upgraded Opmanager from 7200 & above to 8050. While the installations didn't end with an error, I started receiving "Oops looks like a few tables got corrupted. Don't worry.. Run RepairDB.bat from bin directory and restart the server" errors when I trying to login.
I tried repairdb many times, with no error messages, but that didn't solve the issue.
I found log files in \logs directory that includes many errors as below.
What should I do to repair this issue. I only have the conf folder backed up before upgrade.
09:06:51:296 AM ~~~~~~~~~~~~~~~ Logging continued ~~~~~~~~~~~~~~~
-------General Information------
Product = OpManager Version x.x
Service Pack Version =NONE
os name=Windows 2003
os version=5.2
os architecture=x86
java version=1.5.0_11
java vendor=Sun Microsystems Inc.
java specification=Java Platform API Specification
java specification version=1.5
java vm name=Java HotSpot(TM) Client VM
java vm information =mixed mode
java compiler=null
********************************************************
-------RDBMS related information------
database product name = MySQL
database product version=5.0.46-enterprise-nt
database driver name=MySQL-AB JDBC Driver
database driver version=mysql-connector-java-5.0.8 ( Revision: ${svn.Revision} )
database user name=root@localhost
database URL=jdbc:mysql://localhost:13306/OpManagerDB?dontTrackOpenResources=true
******************************************************
09:06:51:296 AM Messages on ********Thursday, February 4, 2010********
09:06:51:812 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
09:06:52:312 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
09:06:52:812 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
09:06:53:312 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####
09:06:53:812 AM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####