PRTG Manual: Oracle Tablespace Sensor

.NET 4.7.2 or later

This sensor requires .NET 4.7.2 or later to be installed on the probe system (on every cluster node, if on a cluster probe).

If the framework is missing, you cannot create this sensor.

For more information, see the Knowledge Base: Which .NET version does PRTG require?

Sufficient account privileges

Use an account for the connection that has the privileges to see all (or specific) views. We recommend that you use the SYSTEM account if possible, otherwise grant your database administrator the SELECT_CATALOG_ROLE to the account that you use. Without sufficient privileges, you might see the error message ORA-00942: table or view does not exist.

Tablespace

Select the tablespaces that you want to monitor. PRTG creates one sensor for each tablespace that you select.

Enable check boxes in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.

Sensor Name

Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?

Parent Tags

Shows tags that the sensor inherits from its parent device, parent group, and parent probe.

This setting is for your information only. You cannot change it.

Tags

Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.

It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

For performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

▪sqlsensor

Priority

Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority ().

Identifier

Enter the Oracle System ID (SID) or the SERVICE_NAME of the database that the sensor connects to. Specify the Identification Parameter below. By default, the sensor uses the SID as the connection string.

You can find the SID or SERVICE_NAME in the CONNECT_DATA part of the TNSNames.ora file on the Oracle server. For example, a SID can look like this: orcl

Identification Parameter

Define the type of identifier that you want to use to connect to the database:

▪SID (default): Connect to the database instance using the SID as the connection string.

▪SERVICE_NAME: Connect to the database instance using the SERVICE_NAME as the connection string.

The type of identifier that you need to use depends on the configuration of the Oracle server.

Sensor Name Prefix

Define if you want to use the SERVICE_NAME as the prefix for the sensor name:

▪Do not use a prefix for the sensor name: Only show the name of the tablespace that this sensor monitors.

▪Use SERVICE_NAME as prefix for the sensor name: Add the SERVICE_NAME to the beginning of the sensor name.

If you have multiple databases on your Oracle server, use the SERVICE_NAME as the prefix to distinguish the tablespaces that you monitor.

Tablespaces

Shows the tablespace that this sensor monitors.

PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

▪Show channels independently (default): Show a graph for each channel.

▪Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status

Free Blocks

The number of free blocks

Free Blocks %

The number of free blocks in percent

Free Space

The free space

Free Space %

The free space (%)

Online Status

The online status

▪Up status: Online, System

▪Warning status: Recover

▪Down status: Offline, Sysoff, Unknown

This channel is the primary channel by default.

Status

The status

▪Up status: Available

▪Down status: Invalid, Unknown

Tablespace Size

The size of the tablespace

Tablespace Size on Disk

The size of the tablespace on disk