Oracle Monitor

[Paulo Pires]

Dear Community,

For Oracle monitor, there's the two main probles:

CA UIM for Oracle probe

• https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/implementing-agents/infrastructure-agent/oracle-database-monitoring.html
• http://support.nimsoft.com/unsecure/archive.aspx?id=36

CA UIM Oracle-logmon probe

• Do you know the links for this one? Broadcom and Nimsoft?

Thanks

Paulo

[Stephen Danseglio]

Hi Paulo,

You can always download packages from support.nimsoft.com.

http://support.nimsoft.com/Default.aspx?center=felles/archive&state=ALL

http://support.nimsoft.com/Files/Archive/00078/oracle_logmon-1_02.zip

Note that the oracle_logmon probe hasnt been updated since 2003. Im not sure how valuable this will be for you...

Steve

------------------------------
Support Engineer
Broadcom
US
------------------------------

[Paulo Pires]

Hi Steve,

Thank you for your answer.

So, can I use the logmon probe instead? Can I collect the same as from oracle_logmon?

• Record oriented, multiple-line files such as logs generated by Oracle products. To extract information from a record-oriented log-file, the probe needs to determine the location where a block starts and ends. This may be specified using string matching rules and/or a line counter. A typical scenario is to have a set of format rules with watchers when using monitoring record-oriented log-files.

But...those dates :(

• oracle - Oracle RDBMS Monitor - 03.Mar 2020
• oracle_logmon - A logmon extension to monitor the Oracle Alert Log - 06.Jan 2003
• logmon - Log monitoring probe - 17.Mar 2022    

Thanks

Paulo

[Stephen Danseglio]

In that probe you have some pre-configured profiles for oracle errors, e.g.,

ORA-00600 internal_error_code critical
ORA-060 deadlocks critical
ORA-01578 block_corruption major
ORA-018 max_session_exceeded major
ORA-020 max_proc_exceeded major
ORA-034 commit_rollback_disable major
ORA-051 timeout major
ORA-055 max_dml_locks major
ORA-059 max_db_files major
ORA-0206 disk_io_failure critical
ORA-0601 cleanup lock conflict critical
ORA-0602 internal programming exeption critical
ORA-0603 server_session_terminate critical
ORA-0604 recursive_sql_error major
ORA-0606 internal error code critical
ORA-07445 core_dump critical
ORA-01650 unable_extend_rollback minor
ORA-01652 unable_extend_tempseg minor
ORA-01555 snapshot_to_old minor
ORA-* all_ora_messages information

But yes, with the logmon probe you can just create profiles for such Oracle errors as needed.

Steve

------------------------------
Support Engineer
Broadcom
US
------------------------------

[Garin Walsh]

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.

[Paulo Pires]

Thank you Stephen Danseglio

Hi Garin Walsh

So, what I should use to monitor my oracle databases?

Thanks

Paulo

[Garin Walsh]

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".

[Paulo Pires]

What is the differente between these two monitoring tools, do I need both?

Oracle Database Monitoring

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/implementing-agents/infrastructure-agent/oracle-database-monitoring.html

Oracle RDBMS Services Monitor

https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/data-center-security-(dcs)/6-9/policies-v127947621-d3608e175970/oracle-rdbms-services-monitor-v127972428-d3608e196943.html

Thanks

Paulo

[Garin Walsh]

Those two items are parts of different products

You are looking for this:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/bigdata-databases-and-storage/oracle-oracle-database-monitoring.html

for Oracle Server monitoring

[Paulo Pires]

Excellent Garin Walsh

Thank you