User permissions for monitoring Oracle 10g via J2EE Diagnostics

User permissions for monitoring Oracle 10g.

For the Oracle 10g performance monitoring, the user collecting metrics should at least have the "Create session" and "Select Any Dictionary" rights.

Advertisements

Error: “Unable to execute ‘select srvname, Cast (SERVERPROPERTY(‘ProductVersion’) as varchar) from sys.sysservers’:Invalid”

“Unable to execute ‘select srvname, Cast (SERVERPROPERTY(‘ProductVersion’) as varchar) from sys.sysservers’:Invalid” when Diagnostics8.0 collector connects to SQL 2000 to collect the metrics

Existing database is not compatible with diagnostic collector 8.0

Diagnostic 8.0 collector does support SQL 2005 and SQL 2008 connections ONLY.

Functionality to get a total number of Server Requests per probe

In order to help control and avoid symbol table explosions it is important to monitor the number of Server Requests injected per each one of the probes into the Diagnostics sever.

This will prevent corruptions in the Archive directory of the Diagnostics Server, which could lead to eventual loss of data.

Starting from version 9.02, it is possible to get an automatic report, available at the following URL:

<IP ADDRESS OF THE SERVER>/persistence/?action=countsr

Which will automatically report the number of symbols generated per probe connected to a mediator instead of having to track them manually.

It has to be accessed on each mediator.

The resultant report shows a scan on all Service Requests that have been received on the server for each probe.

If the number is high and keeps increasing, it indicates unique Service Requests that will have to be controlled.

In upgrade 8.07, this feature is also available.

Changing the default Diagnostics Server Port

If you decide to use an alternative port number after you deploy Diagnostics, you must update the properties in the following table for each of the indicated components in your deployment with the new port number to ensure that the proper communications can take place.

Diagnostics Commander Server

<diagnostics_server_install_dir>/etc

Ø webserver.properties – jetty.port

Ø server.properties – commander.url

Ø probe/etc/dispatcher.properties – registrar.url

Diagnostics Mediator Server

<diagnostics_server_install_dir>/etc

Ø mediator.properties – commander.url

<diagnostics_server_install_dir>/probe/etc

Ø dispatcher.properties – registrar.url

Probes

<probe_install_dir>/etc

Ø dispatcher.properties – registrar.url