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
Consider the following remarks and requirements for this sensor:
Remark |
Description |
---|---|
Performance impact |
This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe. |
Sufficient account privileges |
This sensor requires sufficient privileges for the account that you use for the connection. 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. |
.NET 4.7.2 or later |
This sensor requires .NET 4.7.2 or later from Microsoft on the probe system. In a cluster, install it on every cluster node. If the framework is missing, you cannot create this sensor. For more information, see the Knowledge Base: Which .NET version does PRTG require? |
Overprovisioning |
This sensor does not support overprovisioning. |
Oracle version |
This sensor supports Oracle database servers as of version 10.2 |
IPv6 |
This sensor supports IPv6. |
Lookups |
This sensor uses lookups to determine the status values of one or more channels. |
Limits |
This sensor has predefined limits for several metrics. |
Credentials |
Define the credentials for database management systems in settings that are higher in the object hierarchy. |
Knowledge Base |
Knowledge Base: Why is my Oracle Tablespace sensor showing negative values? |
Hosted probe |
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. |
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
- sqlsensor
For more information about basic sensor settings, see section Sensor Settings.
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. 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:
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:
If you have multiple databases on your Oracle server, use the SERVICE_NAME as the prefix to distinguish the tablespaces that you monitor. |
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, PRTG displays the last value of the primary channel 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 this sensor shows different channels:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. Select a unit from the list. PRTG stacks all channels with this unit 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.
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 (%) This channel has default limits:
|
Free Space |
The free space |
Free Space % |
The free space (%) This channel has default limits:
|
Online Status |
The online status
This channel is the primary channel by default. |
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?