Borndba

If your shop using OEM as monitoring tool, then you should be aware of this. If not try it out. Create a group and put all the DB under that group. If you get into the group you will see the launch dashboard. That will invoke the console. This will be one place where you get all the information. Critical,warning, target down, target unknow information. There is a option to customize also.
In our shop we have given a extra TFT monitor to each DBA and he moves this console to this extra monitor. After implementing this there was tremendous progress in our monitoring ability. We are on top of all the alerts now. If budget permits you can go for a wall mounted LCD

convert this post to pdf.

This tool needs to be installed in OMS server preferreably in OMS_HOME. Create a directory called “emdiag” to store these binaries.
You can follow the note 421053.1 and 421499.1 for this.
Once the installation is done you can get the debug details for all the target monitored using

./repvfy -usr SYSMAN -pwd  -tns emrep test -level 9 -detail

If you want to fix some of the debug issues you need to get the number from detail*.log or verify*.log in $EMDIAG_HOME/log location
These files will ahve info like,

001. Agents without a monitored host target: 1
101. Active Agents with clock-skew problems: 8
105. Agents not uploading any data: 6
106. Agents with improper ping status (5440008): 4
110. Agents not marked as potentially down (6314624): 4

so to fix 001 you need to run

$ ./repvfy -tns emrep verify blackouts -test 1 -fix

Please enter the SYSMAN password: 

-- --------------------------------------------------------------------- --
-- EMDIAG: 2009.0711     Repository: 10.2.0.4.0     06-Aug-2009 09:04:50 --
---------------------------------------------------------------------------
-- -- -- - Running in FIX mode: Data updated for all fixed tests - -- -- --
-- --------------------------------------------------------------------- --
verifyBLACKOUTS

These are some of the other module which can be fixed.

$ repvfy verify availability -test 100 -fix

$ repvfy verify targets -test 709 -fix
$ repvfy verify targets -test 705 -fix
$ repvfy verify targets -test 703 -fix
$ repvfy verify targets -test 702 -fix
$ repvfy verify targets -test 701 -fix
$ repvfy verify targets -test 206 -fix
$ repvfy verify targets -test 130 -fix
$ repvfy verify targets -test 122 -fix
$ repvfy verify targets -test 106 -fix

$ repvfy verify repository -test 706 -fix

$ repvfy verify policies -test 702 -fix
$ repvfy verify policies -test 700 -fix
$ repvfy verify policies -test 103 -fix
$ repvfy verify metrics -test 199 -fix
$ repvfy verify policies -test 101 -fix

$ repvfy verify metrics -test 705 -fix
$ repvfy verify ecm -test 799 -fix
$ repvfy verify metrics -test 703 -fix
$ repvfy verify metrics -test 110 -fix
$ repvfy verify targets -test 189 -fix

$ repvfy verify loaders -test 700 -fix

./repvfy -usr SYSMAN -tns emrep -pwd
 -module TARGETS -level 9 -detail
./repvfy -usr SYSMAN -tns emrep -pwd
 dump target -name  -type oracle_database

convert this post to pdf.