For Oracle monitor, there's the two main probles:
CA UIM for Oracle probe
CA UIM Oracle-logmon probe
You can always download packages from support.nimsoft.com.
Note that the oracle_logmon probe hasnt been updated since 2003. Im not sure how valuable this will be for you...
Thank you for your answer.
So, can I use the logmon probe instead? Can I collect the same as from oracle_logmon?
But...those dates :(
In that probe you have some pre-configured profiles for oracle errors, e.g.,
ORA-00600 internal_error_code criticalORA-060 deadlocks criticalORA-01578 block_corruption majorORA-018 max_session_exceeded majorORA-020 max_proc_exceeded majorORA-034 commit_rollback_disable majorORA-051 timeout majorORA-055 max_dml_locks majorORA-059 max_db_files majorORA-0206 disk_io_failure criticalORA-0601 cleanup lock conflict criticalORA-0602 internal programming exeption criticalORA-0603 server_session_terminate criticalORA-0604 recursive_sql_error majorORA-0606 internal error code criticalORA-07445 core_dump criticalORA-01650 unable_extend_rollback minorORA-01652 unable_extend_tempseg minorORA-01555 snapshot_to_old minorORA-* all_ora_messages information
But yes, with the logmon probe you can just create profiles for such Oracle errors as needed.
Just to follow on to Stephen Danseglio's comment, the oracle_logmon probe isn't a probe, it's a set of watchers intended to be used by logmon. They are ancient and even 10 years ago, well out of date.
It is worth looking at to see what was done but not especially useful today. And even as a starting point, there's the question about whether it's better to spend the time creating new or correcting the old. When We looked at this content, we decided to write new based on existing knowledge of what was relevant rather than trying to capture all.
Thank you Stephen Danseglio
Hi Garin Walsh
So, what I should use to monitor my oracle databases?
Well that depends....
At a very high level, there's the "oracle" probe which monitors the oracle server kind of from the perspective of an administrator.
You have the processes probe (and/or ntservices) where you can monitor the existence and resource usage of the various Oracle processes
You have the logmon probe where you can monitor the oracle logs for particular events
You have the CDM probe where you can monitor dis space used by Oracle
You have the jdbc_response probe where you can issue SQL against the Oracle server to query it
And back to logmon, you can use logmon to execute "scripts" so anything you could type at the command prompt could potentially become a source of data.
We mainly use jdbc_response and logmon monitoring log files to capture the events we care about.
And taking a step further back, based on a guess at the source of your question, there are two ways to approach "monitoring"- try to capture everything and then pick the interesting things out of it later or look at your historic issue and configure monitoring specifically to detect those historic issues.
Neither approach is better but if you are just starting out, and based on my personal experience, I would suggest that you want to go the route of trying to detect the handful of issues you historically see repeating. That makes the learning curve much shallower than the "configure everything at once" approach. It also helps driving acceptance because you can easily do the dog and pony show where you have the uncluttered presentation of "see, UIM detected this one issue".
What is the differente between these two monitoring tools, do I need both?
Those two items are parts of different products
You are looking for this:
for Oracle Server monitoring
Excellent Garin Walsh