I was able to get connected to Oracle using the ManagedDataAccess (.net) connection for Oracle, but is there a way to use OracleCredential instead of the string password in the connection string?
Related
I need to connect my Microsoft Report Builder to Oracle DB but I could not seem to find the correct connection string for Oracle.
I tried:
Specifying username and password
Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;Integrated Security=no;
but it returned:
Is it saying that I need to download the Oracle driver? Or should I get the connection string for Oracle DB?
If you don't already have it, you will need the Oracle Client installed. It will include an ODBC driver. ODBC is a wrapper for the Oracle Client, not a replacement. When setting up your connection you will also need to get the connection properties from the DBA (e.g. hostname/ip address, port, service name, username and password).
See documentation here:
https://docs.oracle.com/en/database/oracle/oracle-database/19/adfns/odbc-driver.html
https://www.oracle.com/database/technologies/releasenote-odbc-ic.html
I have an Oracle database installed on my computer, and I can connect to it with both Oracle Developer and SQL*Plus. Using either of these tools, is there any way to determine the connection string used for the existing connection?
In sql*plus, it stores the safe things (not the password) in _USER, _CONNECT_IDENTIFIER and _PRIVILEGE defined variables. By default, you can access them like:
prompt &_USER.#&_CONNECT_IDENTIFIER &_PRIVILEGE
I'm trying to connect to an Oracle Server using ADO and Oracle Wallet,
First of all, my wallet IS working. I have tested it using
SQLPLUS /#DDKTEST
If I provide username and password in my connection string it works fine:
Provider=MSDAORA;Password=<my password>;User ID=<My user ID>;Data Source=DDKTEST;Persist Security Info=True
But I'm stoked when I need to make a Connection String for Oracle Waller
I've tried the following:
Provider=MSDAORA;Data Source=DDKTEST;Persist Security Info=True
But it doesn't work.
So in short: I need a connection string for ADO, in order for connection to Oracle using my Wallet.
The connection string that we are using with wallets is:
Provider=OraOLEDB.Oracle;Data Source=TNSName;OSAuthent=1;
We use this successfully with TADOConnection in Delphi (first XE5, now 10).
Where TNSName is an alias as defined in TNSNames.ora. I must note that we use a different provider (reflected in the provider name, OraOLEDB.Oracle), and I don't know if this will also work with the outdated and deprecated MSDAORA.
We did use MSDAORA before, but switched to OraOLEDB before we started using the wallets. I do remember that it was quite primitive and didn't even support BLOBs, so I'm not very confident it will support wallets at all.
As the title suggests, I am trying to connect to a remote database via VPN. When I connect using SQL Developer, the connection is fine. However when I try to connect using SQLPlus I get the below error
ERROR:
ORA-12638: Credential retrieval failed
Enter user-name:
I am using the exact same credentials for both (cannot copy the details here as they are a clients and confidential).
Any thoughts as to why SQL Developer acts differently to SQLPlus?
Thanks in advance
K.
I am working on an application that uses Oracle OCI to connect to the Oracle database server. The application allows the user to change their Oracle password and uses Alter User xxx Identified By to perform this.
However, this transmits the user's new password in clear text over the network (we cannot use Oracle SSL to encrypt network traffic). I have found that Oracle recommends using the PASSWORD command in SQLPlus rather than ALTER USER, one reason being that the new password encrypted.
Does the OCI method OCIPasswordChange also encrypt the new password when it is transmitted over the network?
This is using Oracle 10 and 11.
Yes, OCIPasswordChange does encrypt the new password sent over the network.
I have now implemented this and done a packet trace. An encrypted AUTH_NEWPASSWORD packet is transmitted to the Oracle database server.