Connect to Oracle DB using Oracle SQL Developer [message #681787] |
Mon, 31 August 2020 10:53 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](http://www.gravatar.com/avatar/330ea79a00fe6ff5635fde100be3b46f?s=64&d=mm&r=g) |
rerichards
Messages: 9 Registered: August 2020
|
Junior Member |
|
|
From a Windows 10 box I am using using Oracle SQL Developer, attempting to connect to an Oracle DB running Redhat.
The tnsnames.ora file contains the following (the actual has been modified):
orcl =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 11.222.3.4)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = hevy.rodsvr.tvr.com)
(INSTANCE_NAME = hevy)
)
)
When I attempt to connect to the Oracle DB using Oracle SQL Developer, I have the following:
Connect Type: Basic
Hostname: 11.222.3.4
Port: 1521
SID: orcl
I get the following connection error message: "Status : Failure -Test failed: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor"
Any idea why it is failing?
|
|
|
|
|
|
Re: Connect to Oracle DB using Oracle SQL Developer [message #681794 is a reply to message #681793] |
Mon, 31 August 2020 14:22 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
John Watson
Messages: 8944 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
You would use PuTTY or WinSCP to logon to a machine running Unix. You use SQL Developer to logon to an Oracle database. Not the same thing at all! And probably not the same username/password, either. You had better describe what you are trying to do in greater detail.
|
|
|
Re: Connect to Oracle DB using Oracle SQL Developer [message #681795 is a reply to message #681793] |
Mon, 31 August 2020 14:58 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](http://www.gravatar.com/avatar/d29f577f753cb4b873212fd5ed0da4cd?s=64&d=mm&r=g) |
EdStevens
Messages: 1376 Registered: September 2013
|
Senior Member |
|
|
As an aside, version 10.2.0.4.0 is long obsolete. And out of support unless you are paying through the nose for extended support. Waaayyy past time to upgrade.
As for "ORA-01017:invalid username/password", oracle is too dumb to lie about that, and it is very definitive. First it means you actually reached a database (as opposed to getting rejected by the listener or the OS network routing), and you very much did supply a usename/password that is invalid for the database you reached. If you had "success" usign the same credentials with something else, then that "somthing else" was NOT the database that rejected this request.
You said it worked with SSH. I suspect, as does John Watson, that your are talking about os credentials there, not database credentials. You could actually use copy and paste to show us a 'successful' connection, and we could then diagnose further.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|