New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Monitoring Oracle Database with different credentials

Votes:

0

Your Vote:

Up

Down

Our Oracle Database (12g) is under the same IP-Adress with different credentials for every tablespace. For the correct running of the Sensor "Oracle SQL" we need for every tablespace a DEVICE - is there annother posibility?

The Oracle SQL-Sensor works correct with this configuration. When we clone the same SENSOR under another DEVICE (for example an application server with another IP-Adress) and define the same credentials for Oracle Databases, it will not work. We receive the error message "Netzwerktransport: Verbindungsfehler bei TCP-Transportadresse" - what's wrong?

We are using the latest release of PRTG, Installed last week, Trailversion for 30 Days. Thanks for your help.

oracle oracle-sql prtg

Created on Oct 25, 2017 9:36:25 AM by  Urs Buess (10) 1



4 Replies

Votes:

0

Your Vote:

Up

Down

Hi Urs,

You could also use the ADO SQL v2 sensor with the corresponding connection string. This allows you to specify the credentials on a per-sensor basis. Note that you can use %dbloginuser and %dbloginpassword to insert the credentials into the string.


Kind regards,
Stephan Linke, Tech Support Team

Created on Oct 25, 2017 9:59:53 AM by  Stephan Linke [Paessler Support]



Votes:

1

Your Vote:

Up

Down

Hi Stephan,
Thanks fo your suggestion. We've implemented the ADO SQL v2 - Sensor instead of Oracle SQL and it works fine.

Connection string is:

Provider=msdaora;Data Source=<DataSourceName>;User Id=%dbloginuser;Password=%dbloginpassword;

replace <DataSourceName> with your corresponding datasource.

Created on Oct 26, 2017 7:16:15 AM by  Urs Buess (10) 1

Last change on Oct 26, 2017 8:19:21 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

To avoid future problems with updates (microsoft or oracle) we have changed our provider in the connection string to the one from oracle itself "OraOLEDB.Oracle".

New Connection string: Provider=OraOLEDB.Oracle;Data Source=<datasource>;User Id=%dbloginuser;Password=%dbloginpassword;

Created on Nov 9, 2017 10:35:17 AM by  Urs Buess (10) 1



Votes:

0

Your Vote:

Up

Down

Thanks for sharing!


Kind regards,
Stephan Linke, Tech Support Team

Created on Nov 9, 2017 11:04:09 AM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.