This is weired problem that I am facing, I am unable to create a DSN for oracle.
I am currently using windows 64bit OS is windows7 ultimate, and oracle which I am using is oracle 10.2. But the issues is when I go to ODBC data source administrator I am not able to find Oracle in XE server. The strange behaviour..
When Open the same data source administrator from the path I am able to see Oracle XE server and set it. unfortunately I am not able to connect it to the database using this. I guessed that It had to do with permission settings, so I reinstalled oracle as administrator but that did not work. I read that we need to download an external odbc interface, even that did not work.
unable to create System DSN for oracle
How do I fix this? what is the issues here is it with the permission, envirnment variables etc?
Related
I have an Access DB that I migrated to SQL server recently. The SQL server is on a Windows server. Now I can work normally with the SQL database but when others log into the same windows server with their credentials they are not able to access the database. As soon as they open Access frontend they get an error saying failed connection. Now I created an ODBC connection string(File DNS) and gave it to the other users in the network but they still are not able to connect to the database. They get an error stating "SQL server connection failed. The server rejected the connection: Access to the selected database has been denied". Can someone please help me to solve this issue so that multiple users can connect to the SQL DB without any issues? Thanks
Hard to know with the limited information. Are you using windows authentication to sql server, or are you using SQL logons? Either should work fine. The other issue to watch out for is what sql driver did you use to link with?
If you link say using the native 17 ODBC driver, then that is not installed on workstations by default - you have to download and install that driver.
Or, maybe you linked using the long time "legacy" sql driver - that is by default installed on all workstations.
So, it not clear if you using SQL logons, or using Windows authentication for the connection to the database????
If your using windows authentication, then all those other users will require permissions to be granted to the database.
If you using a SQL logon, then that logon would have been saved when you link the table(s), and again it should work for all users. Its quite common to create ONE logon on SQL server, link using that logon, and thus all users will be connecting to the database using the one same logon id/password.
And, if you linked using a FILE dsn, then zero configeration should be required, since access converts FILE dsn's into what are called dsn-less connections. (the origonal file is not required anymore once you link - you can even delete that FILE dsn, and it will still work).
So, FILE dsn is the best choice, since that dsn is NOT required to be setup on each workstation.
And if you using sql logon's, then make sure you checked the box to remember the password during linking of the tables. That is this check box:
And note during a re-link the above box does not appear - only on first time linking of table(s).
The replicate server is installed on Linux and i am trying to connect to a oracle database as source which is on a different server. While testing the connection i am getting the attached error message. The libclntsh.so is already defined in the oracle server machine. Kindly let me know the root cause of this.
You need to install the oracle client (you can download the rpm from technet) on the attunity replicate server and set the environment variable LD_LIBRARY_PATH.
I am tyring to create a scanner application and this requires going into my database and fetching a upc code. However I don't know how to accomplish this in visual studio. Essentially when a person clicks a button a database connection should open from the smart device which will allow the user to see the price of an item. However I was struggling trying to create a a database connection so I tried doing it by my odbc driver which is how I use it for my access programs. This worked and I can see all my tables on my server explorer. However I don't know if I have to explicitly establish a connection pragmatically as well in order to run a select statement....
I forgot to mention I decided to go with an ODBC connection because when I tried sing Microsoft Sql Server (SQLCLient) I got an error saying "The server version is not supported only servers up to Microsoft Sql Server 2005 are supported"
So I decided to go with the odbc driver but I don't even know if using an odbc driver will work while using the application on the scanner device
I haven't programming with VS nor vb.net so this is all pretty new to me, so any pointers at all help
I've had a frustrating time attempting to connect to an Oracle DB as a destination via SSIS so I can export some data into it.
I have Oracle ODAC components installed, tnsnames.ora set up properly, TNSNAMES in the NAMES.DIRECTORY_PATH attribute in sqlnet.ora, Attunity installed on my computer etc. I have even managed to connect to the database in question in the SSIS server explorer, and am able to access all its tables etc.
However I can't seem to find out how to actually connect to that Oracle DB as a destination in an SSIS Project. I started a new package, switched to data flow, selected 'OLE DB Destination' and attempted to create a new connection with either 'Oracle Provider for OLE DB' or 'Microsoft OLE DB Provider for Oracle'. Both only let me cite the server name and user name + password, and when I enter the same ones I used to establish the SSIS server explorer connection I get an 'ORA-12154: TNS: could not resolve the connect identifier specified' error.
I have spent a lot of time trying to fix this but keep running into a brick wall. Any idea what I'm doing wrong or what I could do to establish a connection?
Are you using 32 or 64 bit Windows? I've struggled with some Oracle connections in the past and I made the mistake with mixing up 32 and 64 bit Oracle drivers and settings. Visual Studio is 32 bit and uses those drivers by default, you can go to project properties and change the VS to use 64 bit runtime if necessary.
This could be helpful also: https://stackoverflow.com/a/18098573/5605866
My Problem is that I cannot connect to an SQL Server Express 2008 64bit Database via an Access Runtime 32bit, neither by Windows authentification nor by SQL auth.
On the Windows 2011 Small Business Server runs a Virtual machine with Windows 7 Prof. 32 bit. From this Windows I tested my Access App. using a (32bit) SQL Driver 11, which works fine.
The same Access App used from a 64 bit Windows 7 Prof. Client using a 64bit SQL Driver 11 fails with SQLState 08001 error.
The Thing which I do not understand is, that ODBC Connection test is successful, a data link (UDL) is successful, but not my Access App.
When starting the app, the first Thing is to run a stored procedure through a passthrougquery and grab data from a certain tbl in the SQL-Database. This SP brings the Connection error, but not an runtime error from Access (I removed even an error handler!).
So, how can I find the reason or any error in the Access app (if there is one)?
I am helpless as anything I know to test or to do I already tried out to make the app run. As I cannot even install the SQL Driver 11 in 32bit, it should not be a Driver related error.
Does anyone know a test-app, where I cannot only connect but retrieve data from an SQL-Database or any other tricks to check the Access to the database?
Thanks your help!
Access usually is installed as a 32bit Application. So on 64bit computers it will use the 32bit subsystem. On Windows 7 all the default shortcuts to the ODBC Data Source Administrator utility will lead to the 64bit version of it. Whatever you see or configure there is completely irrelevant, as your 32bit Access is not going to see it.
Solution:
You need to explicitely open the 32bit version of the ODBC Admin utility and configure the data source there.
To make sure you get the right version, use Windows Explorer and open this file: C:\WINDOWS\syswow64\odbcad32.exe
Well, what I found out meanwhile is, that the Connection Fails when trying to use a Connection like this "ODBC; DSN=MyDSN;....." but it works, when I make a Connection DNS-less, by connecting with "ODBC;DRIVER=SQL Server Native Client 11; SErver=myServer;....".
Maybe this is exactly that what you are talking aout. When I just use a DSN it takes the wrong bit Version.
So I will try this: delete the DSN I have, open odbcad32.exe and create the same DSN again.
If I understand you correct, then Win 7 provides the correct Driver and stores it in the DSN. Calling this DSN by Access would lead to the correct Settings.
Further Problem is, that my SSQL-Server instance is not at port 1434, and the SQL Server Native Client 11 Driver has no more Clientconfiguartion to set the static port. So I found a string solution for that "MyServer\Myinstance, 15999".
I hope that this port Setting will be accepted in the DSN, otherwise I really have to Change to DSN-less which is more complicated due to different Servers for the development and the production.
Thanks yr. reply.