<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Oracle Tablespace Sensor

The Oracle Tablespace sensor monitors a tablespace on an Oracle server.

Oracle Tablespace Sensor

Oracle Tablespace Sensor

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • Dutch: Oracle Tablespace
  • French: Tablespace Oracle
  • German: Oracle Tablespace
  • Japanese: Oracle テーブルスペース
  • Portuguese: Oracle Tablespace
  • Russian: Tablespace Oracle
  • Simplified Chinese: Oracle 表空间
  • Spanish: Oracle Tablespace

Remarks

  • This sensor has a high performance impact. Use it with care. We recommend that you use no more than 200 sensors of this sensor type on each probe.
  • This sensor requires .NET 4.7.2 or later from Microsoft on the probe system.
  • This sensor requires sufficient privileges for the account that you use for the connection. We recommend that you use the SYSTEM account.
  • This sensor does not support overprovisioning.
  • This sensor supports Oracle database servers as of version 10.2.
  • This sensor supports the IPv6 protocol.
  • Define credentials, custom port (if required), and timeout in the credentials for database management systems settings of the parent device, or in the settings of a group or probe above.
  • This sensor uses lookups to determine the status values of one or more channels. This means that possible states are defined in a lookup file. You can change the behavior of a channel by editing the lookup file that the channel uses. For details, see section Define Lookups.
  • See the Knowledge Base: Why is my Oracle Tablespace sensor showing negative values?

i_podYou cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.

Detailed Requirements

Requirement

Description

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

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

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

Add Sensor

The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.

In the appearing dialog box in the Add Sensor dialog, enter an identifier to access the tablespace selection and click OK.

Oracle Specific

Oracle Specific

i_round_blueThe settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.

Tablespace Specific

Setting

Description

Tablespace

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

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

Basic Sensor Settings

Click the Settings tab of a sensor to change its settings.

Basic Sensor Settings

Basic Sensor Settings

Setting

Description

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.

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

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

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

i_round_blueFor 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 (i_priority_1) to the highest priority (i_priority_5).

Oracle Specific

Oracle Specific

Oracle Specific

Setting

Description

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.

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

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

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

Tablespace Specific

Tablespace Specific

Tablespace Specific

Setting

Description

Tablespaces

Shows the tablespace that this sensor monitors.

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

Sensor Display

Sensor Display

Sensor Display

Setting

Description

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.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary 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.
    i_round_redYou 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.

Inherited Settings

By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Scanning Interval

Scanning Interval

Scanning Interval

i_square_cyanFor more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

i_round_blueYou cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.

Schedules, Dependencies, and Maintenance Window

Schedules, Dependencies, and Maintenance Window

i_square_cyanFor more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

Access Rights

Access Rights

i_square_cyanFor more information, see section Root Group Settings, section Access Rights.

Channel Unit Configuration

i_round_blueWhich channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.

Channel Unit Configuration

Channel Unit Configuration

i_square_cyanFor more information, see section Root Group Settings, section Channel Unit Configuration.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.

Channel

Description

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 in percent.

Free Blocks

The number of free blocks

Free Blocks %

The number of free blocks in percent

Free Space

The free space in bytes

Free Space %

The free space in percent

Online Status

The online status

  • Up status: Online, System
  • Warning status: Recover
  • Down status: Offline, Sysoff, Unknown

i_round_blueThis 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

More

i_square_blueKNOWLEDGE BASE

Why is my Oracle Tablespace sensor showing negative values?

Which .NET version does PRTG require?

What security features does PRTG include?