When you open NNM 7.x Native interface ovw it opens automatically another window is called alarm browser where you can see all the received traps plus system events grenerated by NNM Components.
this window might hang because dirty shutdown the its database “Events database. to ensure that this is the case you can run ovdumpevents command which will dump the events to your display in ASCII format and it will display message like the highlghted below, if it can not parse it
1247535448 1 Tue Jul 14 05:37:28 2009 computername - Pattern Delete: Event type .220.127.116.11.18.104.22.168.22.214.171.124916867 0 false 3 335241 0 false source:computername(correlate to e2aa977e-7016-71de-0e4b-949781b50000) by ECS;1 126.96.36.199916883 0
1247535450 1 Tue Jul 14 05:37:30 2009 computername – Incorrect Community Name (authenticationFailure Trap) enterprise:ENTERPRISES.3188.8.131.52.1.2 (.184.108.40.206.4.1.3220.127.116.11.1.2) args(0):;2 .18.104.22.168.22.214.171.124.126.96.36.199.188.8.131.52.3184.108.40.206.1.2 0
1247535452 1 Tue Jul 14 05:37:32 2009 computername – Incorrect Community Name (authenticationFailure Trap) enterprise:ENTERPRISES.3220.127.116.11.1.2 (.18.104.22.168.4.1.322.214.171.124.1.2) args(0):;2 .126.96.36.199.188.8.131.52.184.108.40.206.220.127.116.11.318.104.22.168.1.2 0
T ovtrapd disconnected from pmd;1 22.214.171.124179057 0
Unable to read events from the OV Event Database: Read a corrupted record from the OV Event Log: ()
In this case we can remove the current log file and this can be done by the following.
change the directory to the Event database directory
rename the statelog file to be statelog.anything
/var/opt/OV/share/databases/eventdb# mv statelog statelog.corrupted
Restart the ovalarmsrv
/var/opt/OV/share/databases/eventdb# ovstop ovalarmsrv
/var/opt/OV/share/databases/eventdb# ovstart ovalarmsrv
try to start the nnm again or just the Alarm Browsers by running xnmevents.
If the problem still exists it may be the whole database is corrupted so you may remove all the files in the /var/opt/OV/share/databases/eventdb then restart the ovalarm service and hopefully “Insha’ Allah” it will work 🙂 .