I am connecting to Oracle tables via an MS Access DB (Access 2000 format) on Win 10 (likely same issue on Win 7). My 32-bit ODBC driver is configured and is functioning. This particular Access DB is used by 2 or 3 people on a network drive.
The issue is that whenever I reopen the Access DB, the connection is 'broken' and I must reenter my password each time.
This all started to miraculously appear when I got a new computer.
Any insight is appreciated.
Looks like I solved my own issue.
What worked for me is to delete all existing linked Oracle tables within the Access DB and then re-establish the linked tables.
When the Oracle table selection box pops up, select your tables and ensure the 'save password' is selected. Confirm settings with OK and a 'save password' dialog will pop up to warn you the "..password will not be encrypted before it is saved to the file...". I was OK with this warning. Now, each time I open the Access DB, I no longer need to reenter the credentials.
Related
I have a Mac M1 processor so I had to work around in order to even get the SQL Developer onto my computer. I tried using the credentials provided to me to access the HR Schema but it keeps saying that there cannot be a connection established. I have scoured the internet for any sort of answer and nothing has helped. Here is a screenshot of what it shows. enter image description here
I have a LOCAL Oracle 19c database. I am trying to get ADO to connect to it. The first step is to get ODBC working. I have one PDB container called orclpdb, which is what I want to use. I can connect from SQL*Plus...
Y:\INSTALL_UNZIP\bin\sqlplus.exe acs/<Password>#localhost:1521/orclpdb
I go into the 64-bit ODBC Administrator, and had to fight a little bit (adding OCI_LIB32 and TNS_ADMIN paths), but finally got the ODBC Admin tool to connect, but ONLY to the root/system database. My root question is 'How do I get ODBC administrator to connect to a specific container DB?
Within the ODBC Administrator, the TNS Service Name field dropdown only shows ORCL, not orclpdb. Again, I can connect using ORCL, but as system/.
UPDATE: Due to issues such as this, I switched most apps to Devart's Oracle Data Access components to Delphi. They have a DIRECT mode, which does not need SQL*Net or TNS stuff
.
Make sure your TNS_ADMIN/tnsnames.ora file has an entry for the PDB (orclpdb).
I have already installed sqldeveloper and i can launch SQLdeveloper client on my Linux Ubuntu 16.04 system.
The problem occurs during the first attempt of the new oracle connection from the client.
Error returned:
"I/O: The Network Adapter could not establish the connection"
I have already tryed several times to connect at the database but i still missing the username and password.
Is it possible to configure username and password for SYS/SYSTEM(or who else) user after installation?
Full stop.
You don't have a database.
Installing SQL Developer is just giving you a client you can use to work with an existing Oracle Database, which we often refer to as the 'server.'
SQL Developer is not a database.
So you need to get one.
Then you can use SQL Developer.
You have a few options. I talk about them in detail here.
SQL developer is just like the Key for Safe lock. And Database is the Safe.
So right now you have the key for Safe but doesn't have Safe.
Please get the safe first.
SQL Developer is not the Database. So Installing SQL developer will not give access to DB
Instead SQL Developer is the client side tool to retrieve the data or to do the modification on Database.
To get the database you need to download oracle DB from below link
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/oracle12c-windows-3633015.html
I'm having problems accessing an Oracle database via ODBC in Access and hope someone has some advice. I've spent a fair time trying to find a solution, but nothing useful has come up.
I have a connection setup in ODBC that access an Oracle 9 database. I can use the Test option on ODBC administrator and receive a Test Successful message. I can also connect to the DB using SQL*PLUS. However, when I try to create a new linked table in Access 2007 and use the ODBC option, I get the following error when it tries to connect:
ODBC--Call failed.
[Oracle][ODBC][Ora]ORA-12154: TNS:could not resolve service name
(#12154)[Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAttr failed IM006 0 [Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAttr failed (#0)
I know the TNS lookup is working because ODBC Admin tool works as does tnsping. The question is, why does it work outside Access but Access can't do it?
EDIT (2012-02-22 15:05): Just tried on a different PC and the same thing occurs, although another user logged in and the connection worked for them, so it appears to be linked to my WinXP profile. Does this help any?
Any advice would be greatly appreciated.
BBz
I think I've resolved the issue, but it took some digging. Using Process Monitor from Sysinternals, I discovered that Access had found a sqlnet.ora file in the "My Documents" folder of my profile and was using this in preference to the global tnsnames.ora file.
We had previously disabled sqlnet.ora (renamed the file in the Oracle folder) but Access obvisouly checks other locations for it. I've renamed the file and can now access the DB as expected via ODBC.
Interesting what you can learn!
Hope somebody finds this useful one day.
Thanks for reading
BBz
I have a VS2010 DB Project migrated form VS2008 and a couple of schema comparisons created.
I get the following error:
Error 1 An error was received from SQL Server while attempting to reverse engineer elements of type Microsoft.Data.Schema.Sql.SchemaModel.ISqlUser: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Error 2 ExecuteReader requires an open and available Connection. The connection's current state is closed.
I am using VS2010 Premium and SQL Server 20008 R2 on my dev machine.
My database is hosted on local instance of SQL server.
When I use the same schema comparision with a remote server and use the sa login it works. On my dev machine, I tried with sa login as well. but no luck!
Has anyone encountered such an issue and was able to resolve?
Well cracked it! (not sure if that is the solution, at least it now works for me)
The local databases I was using for schema comparison were restored from backups of production databases. The users in the databases will loose their SID (probably) with the ones mapped on the production server.
I simply deleted the database users and recreated them and the schema comparison started working again.