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: Oracle Tablespace
- Russian: Tablespace Oracle
- Simplified Chinese: Oracle 表空间
- Spanish: Oracle Tablespace
- This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.
- This sensor requires sufficient privileges for the account that you use for the connection. We recommend that you use the SYSTEM account.
- This sensor requires .NET 4.7.2 or later from Microsoft on the probe system.
- This sensor does not support overprovisioning.
- This sensor supports Oracle database servers as of version 10.2.
- This sensor supports IPv6.
- This sensor uses lookups to determine the status values of one or more channels.
- Define the credentials for database management systems in settings that are higher in the object hierarchy.
- 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 |
---|---|
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. |
|
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).
|
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.
|
Parent Tags |
The 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 |
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 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 under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
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.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
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.
For more information, see section Root Group Settings, section Channel Unit Configuration.
Which 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 |
Free Blocks |
The number of free blocks |
Free Blocks % |
The number of free blocks (%)
|
Free Space |
The free space |
Free Space % |
The free space (%)
|
Online Status |
The online status
|
Status |
The status
|
Tablespace Size |
The size of the tablespace |
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?