PRTG Manual: Oracle Tablespace Sensor
The Oracle Tablespace sensor monitors a tablespace on an Oracle server.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Oracle Tablespace
- French: Tablespace Oracle
- German: Oracle Tablespace
- Japanese: Oracle テーブルスペース
- Portuguese: Tablespace Oracle
- Russian: Табличное пространство Oracle
- Simplified Chinese: Oracle 表空间
- Spanish: Oracle Tablespace
- 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 Microsoft .NET 4.7.2 or later 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 version 10.2 or higher.
- 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?
You 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.
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).
|
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. |
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.
The settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.
Setting |
Description |
---|---|
Tablespaces |
Select the tablespaces that you want to monitor. PRTG creates one sensor for each tablespace that you select.
|
Click the Settings tab of a sensor to change its settings.
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. |
Parent Tags |
Shows tags that the sensor inherits from its parent device, parent group, and parent probe.
|
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.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
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 ( |
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.
|
Identification Parameter |
Define the type of identifier that you want to use to connect to the database:
|
Sensor Name Prefix |
Define if you want to use the SERVICE_NAME as the prefix for the sensor name:
|
Tablespace Specific
Setting |
Description |
---|---|
Tablespaces |
Shows the tablespace that this sensor monitors.
|
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.
|
Graph Type |
Define how different channels are shown for this sensor:
|
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. |
By default, all of the following 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 under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
Click to interrupt the inheritance.
Setting |
Description |
---|---|
Scanning Interval |
Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:
|
If a Sensor Query Fails |
Select the number of scanning intervals that the sensor has time to reach and to check a device again if a sensor query fails. Depending on the option that you select, the sensor can try to reach and to check a device again several times before the sensor shows the Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows the Warning status. Choose from:
|
Schedules, Dependencies, and Maintenance Window
You 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.
Setting |
Description |
---|---|
Schedule |
Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:
|
Maintenance Window |
Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:
|
Maintenance Begins |
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the one-time maintenance window. |
Maintenance Ends |
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the one-time maintenance window. |
Dependency Type |
Select a dependency type. You can use dependencies to pause monitoring for an object depending on the status of a different object. You can choose from:
|
Dependency |
This setting is only visible if you enable Select a sensor above. Click |
Dependency Delay (Sec.) |
This setting is only visible if you select Select a sensor above. Define a time span in seconds for the dependency delay. After the master sensor for this dependency returns to the Up status, PRTG additionally delays the monitoring of the dependent objects by the time span you define. This can prevent false alarms, for example, after a server restart or to give systems more time for all services to start. Enter an integer value.
|
Click to interrupt the inheritance.
Setting |
Description |
---|---|
User Group Access |
Define the user groups that have access to the sensor. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:
|
Click to interrupt the inheritance.
Which 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.
Setting |
Description |
---|---|
Channel Unit Types |
For each type of channel, select the unit in which PRTG displays the data. If you define this setting on probe, group, or device level, you can inherit these settings to all sensors underneath. You can set units for the following channel types (if available):
|
Which channels the sensor actually shows might depend on the monitored 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
|
Status |
The status
|
Tablespace Size |
The size of the tableslace |
Tablespace Size on Disk |
The size of the tablespace on disk |
Knowledge Base
Why is my Oracle Tablespace sensor showing negative values?
Which .NET version does PRTG require?
What security features does PRTG include?
For more information about sensor settings, see the following sections: