Are there a way to have oracle client connect to an other db/service on the serverside not changing tnsnames files on client's?
Unless you are running the server on a VM and you swap out one VM for another at the same network address there is no way to handle what you are describing on the server side. DB connect strings on the client must be unique, and database-specific.
Related
I have a Windows application running locally on a Windows 10 PC that connects to a SQL Server Express database that is also installed locally on the PC. The PC also has a VPN client on it. Whenever the VPN client is logged onto a network, the Windows application cannot connect to the SQL Server database. So, I have to go into SQL Server Configuration Manager and change the setup from using TCP/IP to use Shared Memory. Then everything works fine. So, I assume both programs are using the TCP/IP stack and are conflicting with each other. The VPN client is typically connected continuously all day. Would anyone know why there would be a conflict here? Thanks.
I couldn't find an answer so I'm posting it here.
I want to know if it's possible to connect from Visual Studio to SQL Server based only on IP address when the two servers are not in the same domain or workgroup?
I've allowed remote connections and opened port 1433 on both servers with no luck. One server is 2008r2 and the second is 2012r2. The SQL Server version is 2012.
Thank you
It's certainly possible. Since they aren't in the same domain, you won't be able to use windows authentication. But you can use a SQL login.
I believe this is a duplicate question of:
Connect to SQL Server through IP address
That shows you other steps to check for answering by IP address only.
I am attempting to create a new Database Project in VS2010 via the New Project Wizard, and via this article: http://msdn.microsoft.com/en-us/library/aa833432(v=vs.100).aspx
I am on the 'Configure Build/Deploy' step, and am attempting to connect to a named instance of SQL Server 2008R2 that I just installed, called DEVELOPMENT. Assuming the server name is DB-01, I am using DB-01\DEVELOPMENT as the Server name in the dialog in the screenshot below. I'm also using the remaining settings in the dialog, but it keeps giving me the following error:
A network-related or instance-specific error occurred while
establishing a connection to the 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:
TCP Provider, error: 0 - A connection attempt failed because the
connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to
respond.)
DEV is the name of a database I created on the DEVELOPMENT instance. If I use DB-01 as the server name, which is the default instance, it connects. In the past, we've been developing from a database on the default instance, with no issues, but I'm trying to move to local, source-controlled databases. What am I missing with this not connecting?
EDIT: As a little more context, it's not the username/pw combination, or the existence of the DEV db on the instance, because I receive different errors if either of those are incorrect. It's simply not able to connect once I give it the named instance.
Figured it out:
The default instance of SQL Server (called MSSQLSERVER in some places) uses port 1433 by default for incoming connections, which was opened in Windows Firewall. This is why I was able to connect to the default instance (DB-01). If you've created a named instance of SQL Server, by default these instances use port 1434 for incoming connections. These are TCP ports for each case. Well, I have to admit that I opened TCP port 1434 in Windows Firewall and still was not able to connect to the named instance remotely, and still am not sure why this was the case. So instead, I opened up a random port (6969) in Windows Firewall, and configured the DEVELOPMENT (named) instance to accept incoming connecting over that port only. For instructions on how to configure specific SQL Server instances to use ports other than the default, see this article:
Configure a Server to Listen on a Specific TCP Port
Once I configured the instance to use port 6969, I was able to connect with no issue. Hope this helps others that are having a similar/same issue.
I have the Oracle client, weblogic and the SOA suite 11g installed on a Win 7 machine. The Oracle DB is on a server 2008.
I have the hardest time connecting to it. The server name is S2008 on port 1521. I used the RCU to install the schema.
I am able to ping the server. Could someone please help me out in getting this connected? I have not done this configuration before.
Thank you.
This is more of a database concern, not WebLogic.
The simplest thing to do is to confirm you can telnet to port 1521 from the WebLogicmachine (telnet 1521). If this cannot connect, it is either a firewall issue or the TNS listener is not running on port 1521. Check to make sure that port 1521 is opened on the Database host and then try again.
Also, try connecting outside of WebLogic to remove a variable from the problem. This would be easier/faster anyway. Try using SQL developer to connect to the host/port where the database is running. This will show you the ORA-????? error(s) for the connection attempts without having to go through the connection wizard in the weblogic console
I have a multi tier application that want to use a RAC to improve the availability of the server.
What we have now is, the client side sending a transaction data to the server side through a webservice. At client level, we need to specify the url address (IP address) as a path to send a data.
As for now, there are 2 oracle instance installed as a RAC at a server.
1. 133.38.52.101
2. 133.38.52.102
Both of the server are connect to same Oracle Database (SAN storage).
Let say, the client side is pointing to .101. Suddenly the .101 machine is down, how can I possible to use the .102 without changing the point URL at the client side. Is there any configuration can be done at RAC or Windows Server 2008 for this type of problem?
Use a load balancer between client machine and application server machines.
Use Oracle's transparent application failover functionality in OCI to achieve redundancy and load balancing between application server machines and RAC instances. DML transactions will be rolled back but selects will be transparently failed over.