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.
Detailed Requirements
Requirement
Description
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.
.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.
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?
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 ().
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.
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.
Tablespace Specific
Tablespace Specific
Setting
Description
Tablespaces
The tablespace that this sensor monitors.
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.
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 select Stack channels on top of each other above.
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 under the corresponding setting name to disable the inheritance and to display its options.
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.
Schedules, Dependencies, and Maintenance Window
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
Access Rights
Access Rights
For more information, see section Root Group Settings, section Access Rights.
Channel Unit Configuration
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.
Channel Unit Configuration
For more information, see section Root Group Settings, section Channel Unit Configuration.
Channel List
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
Lower error limit: 5%
Lower warning limit: 10%
Free Space
The free space
Free Space %
The free space (%)
This channel has default limits
Lower error limit: 5%
Lower warning limit: 10%
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
More
KNOWLEDGE BASE
Why is my Oracle Tablespace sensor showing negative values?