I'm trying to study query optimization using SQL command line. When I'm about to connect to the database, I got this error. It's my first time to use the SQL command line. Ive installed Oracle database 11g express edition. The database I'm trying to access is also installed on my computer. I have a proxy network settings in my computer, which I already removed and the same error occurred. I'm using a desktop PC with W7 - 64bit OS. I'm using a wireless USB adapter to connect to the internet. I tried tnsping on my machine and returned the following lines:
Used HOSTNAME adapter to resolve the alias
Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTO
COL=TCP)(HOST=192.168.0.20)(PORT=1521)))
OK (70 msec)
Also can you have a check to see if you have set up a loopback adapter if your os is windows. Check and follow this link
http://www.oracledistilled.com/windows/configuring-the-loopback-adapter-on-microsoft-windows/
Related
I use oracle DB Developer on VirtualBox to create databases using SQLDeveloper. I use VirtualBox since I can't download SQL Developer on MacBook. I'm writing a Java code on eclipse with an SQL connection on the host machine. How can I connect establish a connection between the guest machine and the host machine?
I've tried to do the port forward option through VB's network adapter setting. When I tried localhost:8000, the page wasn't accessible. I'm honestly not sure if this is even a valid solution for my problem.
Anyone has a suggestion on how to connect my host machine to the database on the guest machine?
I have a Red HAT system on oracle virtual box that I've been trying to set a mssql server up.
-Also tried doing everything on SUSE vm but I've been probably doing the same thing wrong on that one aswell.-
I have the server up but was unable to connect the mssql server in linux from windows terminal or SSMS.
Get this as a terminal response on windows
ODBC Driver 13 for SQL Server does not support connections to SQL Server
2000 or earlier versions.
and below one on SSMS
Not associated with a trusted server connection
Not sure if I have some network configuration info wrong on vbox myb?
Might be using the wrong ip addr trying to connect aswell.
I use localhost to connect on virtual box.
Tried to connect by localhost ip, public ip and
sudo ip addr show eth0 | grep "inet"
command as well.
Any idea what could be the issue since I am quite sure both the sql server versions are up to date.
Solved upon changing network attached to on virtual box settings to bridged adapter with promiscuous mode on.
In case anyone gets stuck on this
I have Installed sql-developer on Lubuntu and I want to connect sql-developer to oracle 11g, oracle 11g installed in another system(Centos)and sql-developer installed(Lubuntu) while testing the connectivity from sql-developer via tns service name its showing error as "Status -Test Failed: IO Error The Network Adapter Couldn't establish the connection". TNSPING is working for service names and ping ip-address is also working in destination sever where we have installed oracle 11g database.
Please let me know to resolve this issue.
Thanks,
Ranjithkumar
Could you please provide your TNS-Names File or the configuration of your SQL-Developer? The Error seems to occur because of a false Host-Definition. Be sure that you put in the right SID or Service name.
If you assume that your configuration must be right, please Check your DNS- and firewall-Settings. Further you can change into the Oracle-Bin Folder and execute the "tnsping" binary with the Host as Parameter.
Has anyone accomplished pushing files to a BOE server using SSIS? I am trying to develop a SQL Server 2008 SSIS package that will push report (Excel) files to our Business Objects Enterprise (BO XI 3.1) server. Via a Script Task, I am using the Business Objects .NET SDK components to authenticate and connect to the BOE Server.
I have a copy of the package deployed to a local instance of SQL Server 2008 running on my Windows XP desktop. The package executes successfully (via a SQL Agent Job) and delivers the file to the designated location on the BOE server.
When I deploy the package to our development SQL server (SQL Server 2008 on Windows Server 2008 64-bit) and attempt to execute the package via a SQL Agent job, I receive the error message "File Repository Server Input is down" when the script task attempts to "Commit" the file to the BOE server. The package is able to open a session with the BOE Server, create a new info object, but fails on the infoStore.Commit command.
I have another SSIS package that executes successfully from our development SQL server - it communicates with the BOE server and searches for user sessions. It does not communicate with the Input File Repository - that seems to be the key distinction.
I have found limited information related to this error that indicates firewalls and ports between the SQL Server and BOE server may be the cause. I have reviewed the BOE Administrator's Guide to no avail (most likely due to my lack of understanding related to firewalls and ports). Both servers are within the same subnet and neither server has the firewall turned on. The ports for the BOE CMS servers and the Input/Output File Repository servers have been set to static port ids. Our network guy indicates there should be nothing preventing communication between the servers based on firewall or port settings.
Any help would be greatly appreciated!
Have you tried all the usual 'run as 32 bit' solutions? I guess yuor SDK is a 32 bit one, not a 64 bit one.
http://www.bidn.com/blogs/ShawnHarrison/ssis/2362/ssis-basics-running-a-package-in-32-bit-mode
However the fact the the SDK works for different services implies that it runs OK in 64 bit. So if you want to troubleshoot ports, I found this link http://scn.sap.com/thread/2027785 which indicates that the BOE ports are 6400 to 6411. To check that a given port is open, you go to a DOS prompt and type
TELNET hostname port
So if your BOE server is BOESERVER then you'd try this:
TELNET BOESERVER 6400
to test port 6400. You should get a black screen to indicate it's connected.
However, again, the fact that you seem to be able to connect and operate but not commit implies there is not a port problem as you can connect, just can't commit.
Are there any logs in the BOE side to give you a better idea of the issue?
A resolution to this issue has been identified and verified. The Windows AD account used by the proxy the SQL Agent job uses to execute the SSIS package did not have sufficient privileges on the network. Our DBA gave the account local Windows administrator privileges on the SQL server and this resolved the "File Repository Server Input is down" error I was receiving.
Thanks to those who responded and gave me other ideas to investigate.
I am not able to connect to a SQL Server 2005 hosted on a Win7 virtual machine. I am new to VM, can someone help me locate the problem?
I am able to connect another SQL server which is installed on the local machine.
When you say you can't connect - that can mean a lot of things - really you need to be much more specific.
In addition to the comments and answers already here - If you're having trouble connecting to it in Sql Server Management Studio - you should open Configuration Manager on the VM itself and make sure that Shared Memory and Named Pipes are enabled (open the SQL Server Network Configuration node in the tree).
For example, SQL Server Express instances are configured by default to reject the kind of remote connection that SSMS wants to open by default.
first of all check your connection string (for reference):
http://www.connectionstrings.com/
Second you need to add an exception in the guest machine firewall or completely disable it (port 1433 is for sql tcp/ip access).
this works fine for me:
SQLConn.ConnectionString = "Network Library=DBMSSOCN; Data Source=xxx.xxx.xxx.xxx,1433;
Initial Catalog=mySQLServerDBName; User ID=myUsername;Password=myPassword"
good luck