What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Using sysdba account for SQL Sensor v2 queries

Votes:

0

Hi, I'm trying to setup a Oracle query from the PRTG Core server. I have successfully ran some queries via Oracle DB but there's a couple of commands that I need to run using the sysdba account. However when I use the username "sys as sysdba" with password to the same database, I get the following message:-

ORA-01017:invalid username/password; logon denied

So what is the supported way to run commands as sysdba?

Thanks.

invalid-username prtg sysdba

Created on Nov 17, 2017 1:47:51 AM



9 Replies

Votes:

0

Hello hugoti,

Thank you very much for your contact.
Do I understand you correctly, that the username within the device's "Settings" tab that has the affected sensor is "sys as sysdba"? Or is it just "sysdba"?
Please note that the username must be a string, spaces are obviously not possible inside the username.

Does it work then?

Sebastian

Created on Nov 17, 2017 7:16:55 AM by Sebastian Kniege [Paessler Support]



Votes:

0

I've tried both with and without quotes and both got same result - ORA-01017

I've tried it using the SQLv2.exe tool.

Created on Nov 17, 2017 7:25:55 AM



Votes:

0

The username has to be entered without quotes, but the question is if the username is "sysdba" or "sys as sysdba"?

Created on Nov 17, 2017 7:59:37 AM by Sebastian Kniege [Paessler Support]



Votes:

0

I tried both. If I use a local account is works fine, but some queries require sysdba privileges hence will need to log in as sysdba. If I run SQLPLUS using sysdba on the said Oracle server it works fine (see below) :-

C:\Documents and Settings\Administrator>sqlplus sys as sysdba

SQL*Plus: Release 10.2.0.3.0 - Production on Fri Nov 17 16:11:43 2017

Copyright (c) 1982, 2006, Oracle. All Rights Reserved.

Enter password:

Connected to: Oracle Database 10g Release 10.2.0.3.0 - Production

Created on Nov 17, 2017 8:12:37 AM



Votes:

0

Hi hugoti,

Please test the connection using the ADO SQL v2 sensor.

While the sensor creation, you can define a Connection String. Please use the following which I found here: Data Source=myOracleDB;User Id=SYS;Password=SYS;DBA Privilege=SYSDBA; User (SYS) and Password (SYS) can be replaced with the PRTG placeholders %dbusername and %dbpassword. The placeholders will refer to the username and password that you defined within the device settings under CREDENTIALS FOR DATABASE MANAGEMENT SYSTEMS.

Does it work then?

Sebastian

Created on Nov 17, 2017 8:54:15 AM by Sebastian Kniege [Paessler Support]

Last change on Nov 17, 2017 8:55:37 AM by Sebastian Kniege [Paessler Support]



Votes:

0

I get the following error:

An OLE DB Provider was not specified in the ConnectionString. An example would be, 'Provider=SQLOLEDB;'

I'm not sure what this means?

Created on Nov 20, 2017 12:24:58 AM



Votes:

0

Hello hugoti,

I'm not very familiar with Oracle but this (redirects to Stackoverflow.com) link might help to understand the error message shown.

What's the result?

Sebastian

Created on Nov 21, 2017 2:59:20 PM by Sebastian Kniege [Paessler Support]



Votes:

0

Unfortunately I still couldn't get this to work even with using the above link. Guess it's a limitation with PRTG as it cannot use sysdba login credentials?

Created on Nov 30, 2017 4:46:37 AM



Votes:

0

Dear hugoti,

According to our developers which I just asked about that issue, it appears as there is also an option which has to be changed within the connection driver and it can't be achieved by editing the connection string only, so your assumption is - sorry to say - somewhat correct. PRTG does not support this.

Best regards,
Sebastian

Created on Nov 30, 2017 1:11:36 PM by Sebastian Kniege [Paessler Support]




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.