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


Can't connect to Oracle database

Votes:

0

Your Vote:

Up

Down

I'm trying to monitor three databases on a single Oracle server, each with a different SID (call them SID1, SID2, and SID3). I'm using the Oracle SQL v2 sensor. (Previously I had been monitoring all three databases with older sensor, but a recent Oracle upgrade broke those sensors.)

Two of the sensors, monitoring SID1 and SID2, work fine. The third one, monitoring SID3, fails with:

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

But this SID worked previously with the old sensor, before the upgrade. The tnsnames.ora file correctly lists the SID as SID3. So what could be wrong with this setup?

I'm running PRTG 15.1.15.2022+.

listener oracle prtg sid

Created on Aug 10, 2015 8:30:47 PM by  David Guertin (30) 1



7 Replies

Votes:

0

Your Vote:

Up

Down

Hello David,

Please update to the latest version of PRTG and readd the Oracle v2 Sensors in order to see if the issue still remains, using the Auto-Update. Alternatively you can download the software from our Paessler Service Center using your registered email and password:

Once you have downloaded the latest version, you can install it directly over the version currently running. The configuration and database will not be affected by installing the newer version over the old and the configuration is automatically backed up before this process.

Created on Aug 12, 2015 12:07:07 PM by  Jochen Greger [Paessler Support]

Last change on Aug 12, 2015 12:17:51 PM by  Jochen Greger [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks for the reply. I upgraded to 15.2.17.2804 and re-added the sensor, but unfortunately it still does the same thing:

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

Created on Aug 12, 2015 4:23:04 PM by  David Guertin (30) 1



Votes:

0

Your Vote:

Up

Down

Hello David,

Are the SID´s using the same Port and user account? Is there something different (Encryption, protocol, etc.) between the third SID and the others? Please verify that in the SID name a special character is used. Can you please reenter the System ID in the sensors settings again to avoid invisible characters?

Created on Aug 13, 2015 12:46:43 PM by  Jochen Greger [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Yes, some port and user account. As far as I can find, there's nothing different between the three SIDs, but something has got to be! There are no special characters in any of the SIDs. Outside of PRTG, I can log in with sqlplus and query any of the SIDs with the same user and password.

Here are two examples, both of which are accessible with sqlplus. Both examples show the correct SID and the correct username (which is the same for both). Both hostnames are CNAME records for the same database server:

1. $ sqlplus sns_q@prct.foo.com

SQL> select sys_context('userenv','instance_name') from dual;

SYS_CONTEXT('USERENV','INSTANCE_NAME')

--------------------------------------------------------------------------------

PRCT

SQL> select user from dual;

USER

------------------------------

SNS_Q

2. $ sqlplus sns_q@pprd.foo.com

SQL> select sys_context('userenv','instance_name') from dual;

SYS_CONTEXT('USERENV','INSTANCE_NAME')

--------------------------------------------------------------------------------

PPRD

SQL> select user from dual;

USER ------------------------------ SNS_Q

But in PRTG, I set up two identical Oracle SQL v2 BETA sensors, but only the first one works:

1. DNS Name: prct.foo.com

System ID: PRCT

SQL Query FIle: test.sql

Result: sensor OK

2. DNS Name: pprd.foo.com

System ID: PPRD

SQL Query File: test.sql

Result: ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

I get the same results whether I set up the sensors on different devices (as I've shown here) or on the same device (which used to work). Both SIDs are actually on the same device.

Created on Aug 14, 2015 8:46:11 PM by  David Guertin (30) 1



Votes:

0

Your Vote:

Up

Down

Hello,

Please use the Utility tool TNSping (included with Oracle Client) and check if all three SID´s are connectable. (Run it on the PRTG Host (or host of the Remote Probe))

Use the following command to test connectivity tnsping <server>:<port>/<sid>

Which results do you get?

Created on Aug 18, 2015 2:08:51 PM by  Jochen Greger [Paessler Support]



Votes:

0

Your Vote:

Up

Down

tnsping connects successfully to all three SIDs:

D:\>tnsping bandev:1521/pprd

TNS Ping Utility for 64-bit Windows: Version 11.2.0.1.0 - Production on 24-AUG-2 015 12:01:53

Copyright (c) 1997, 2010, Oracle. All rights reserved.

Used parameter files: D:\sqlnet.ora

Used EZCONNECT adapter to resolve the alias Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=pprd))(ADDRESS=(P ROTOCOL=TCP)(HOST=xxx.xxx.xxx.xxx)(PORT=1521))) OK (30 msec)

Created on Aug 24, 2015 4:19:07 PM by  David Guertin (30) 1



Votes:

0

Your Vote:

Up

Down

Hello David,

in the tnsping result we can see that the service name was used and not the SID´s. Could you please forward us the results using the SID in the tnsping to support@paessler.com. Please refer to this article.

Created on Aug 27, 2015 7:47:50 AM by  Jochen Greger [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.