I'm new to working with AWS and RDS. What I'm trying to do is setup an Oracle DB instance on RDS, that part is fine but when I try to connect to it via an application I get various errors. Depending on the application I get a couple of different errors.
[Local computer trying to connect to RDS directly]
LinqPad - Connection Error: Server did not respon within the specified timeout interval. (I get this on both the Direct and OCI connection modes)
SQL Developer - IO Error: The network adapter could not establish the connection.
[EC2 instance in same VPC]
LinqPad - Connection Error: NET: Connection was refused with error ORA-12504
(I get this on both the Direct and OCI connection modes also)
I've done some research and it mostly points that the VPC isn't setup correctly, but I'm able to connect to my EC2 instance fine though.
Oddly enough, I did have one fluke incident where from my local computer it did connect, but as soon as I tried the test again I got more errors.
Any help, or new directions to look would be greatly appreciated.
Will provide more information if needed also. Wasn't sure what to post settings wise. Thanks in advance.
Related
We're currently having issues setting up a connection to oracle datasources in datafusion (via jdbc) and i'm not sure if i am missing something.
Bit of a background, we had issues connecting to any data source initially so in gcp i setup a vm instance to act as a proxy server (due to it being a private datafusion instance) and used iptables to register the connections.
After this i can successfully connect to sql server datasources, on the vm instance i can ping and telnet all oracle and sql datasources.
Network connectivity tests show datafusion can connect to the proxy and also that the proxy can hit datasources on-prem.
The following pics are of my connection to oracle under namespace admin in datafusion
The ip address is of the proxy instance and the port is what was assigned in the iptable entry
Again this works for sql server. Our datateam can connect to these datasources via bigquery using odbc, but it looks like you cannot use that connection type in datafusion.
Think we have resolved the issue. We noticed the logins being used had older password versioning for oracle 10, 11 etc. Got the oracle dba to create a new user to test and connection successful instantly :)
We are suddenly getting the error ORA-12514, TNS:listener does not currently know of service requested in connect descriptor in our application.
Googling this seems to suggest a couple of easy solutions (e.g. found here), but they don't work for us.
The perplexing thing is:
We can connect via SSH to the server running our application, and..
we can connect with SQLPlus on that server, ..
using the exact same JDBC connection parameters as the app (we can get them from a log during application startup, so we are sure they are the same).
Why could it be that we can connect to the DB with SQLPlus, but our app cannot?
Here are the two methods to connect (JDBC and SQLPlus), both consistently anonymised:
JDBC
{
jdbcDriver=oracle.jdbc.OracleDriver,
jdbcUser=THE_USER,
jdbcPassword=THE_PASSWORD,
configurationVersion=1.0.14,
jdbcURL=jdbc:oracle:thin:#(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(Host=THE_HOST)(Port=THE_PORT))(CONNECT_DATA=(SERVICE_NAME=THE_SERVICE_NAME)))
}
SQLPlus
sqlplus THE_USER/'THE_PASSWORD#'"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(Host=THE_HOST)(Port=THE_PORT))(CONNECT_DATA=(SERVICE_NAME=THE_SERVICE_NAME)))"
According to our DB specialist there were "wrong entries in Oracle Internet Directory (OID)".
They cleaned it up and now it ist working again. Sorry that this is not very helpful as an answer, but I don't know more details...
I am getting a weird problem,
I have an oracle database on amazon aws
I can connect using sql developer running on a pc but when I try to connect using the same software on a Mac It shows this error:
An error was encountered performing the requested operation:
IO Error: The Network Adapter could not establish the connection
Vendor code 17002
Are you using RDS? Have you checked if this software you're using in your mac takes use of a different port to connect to your db on aws? If that's the case you'll need to add this to your security group from your aws console.
I am currently accessing/connecting to a remote database through VPN and I have no issues querying on the remote database. I want to create a db-link to connect my local db to the remote database in order to join certain tables. Sadly, I am getting error ORA-12545.
This is my db-link code:
CREATE DATABASE LINK DB_LINK
CONNECT TO REMOTE_USER_NAME
IDENTIFIED BY PASSWORD
USING '(DESCRIPTION=(CONNECT_DATA=(SID=test_SID))(ADDRESS=(PROTOCOL=TCP)(HOST=HOST_NAME.com)(PORT=1521)))'
I don't have an Oracle client installed on my machine so I am using the full description. There are no issue accessing both our db and the remote db without an Oracle client installed so I assume this is not the problem.
My ping to the remote address returned TTL expired in transit even though the VPN is connected. This seems a bit weird but I am not entirely sure if this is the problem.
I must be missing a crucial step. Any advice is appreciated.
I have a web-application which is reciving the following while trying to connect to a database hosted on another server.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Now, there problem here is that the connection strings, and the server paths area all perfect.
The site run correctly when run via cassini, on my local machine. (Connections strings are correct.)
Other sites hosted on the same server are able to access the databse. (Server paths ara all active.)
While the error says it's been unable to connect, Activity Monitor is aware of the query, and the Server Logs show no error. (Just odd.)
Google & Bing have massively failed with this, so I guess it's time to hit the Stack!
Open the Sql Server Conifguration Manager, expand Sql Server 2005 Network Configuration, click Protocols for <Yourserverinstance>, then check TCP/IP is enabled.