Sfrgttk

insert EOF statement before the last line of file

Why avoid shared user accounts?

Grade 10 Analytic Geometry Question 23- Incredibly hard

Why did this image turn out darker?

Can a hotel cancel a confirmed reservation?

What is the wife of a henpecked husband called?

Contest math problem about crossing out numbers in the table

How to prevent cleaner from hanging my lock screen in Ubuntu 16.04

How should I handle players who ignore the session zero agreement?

Word or phrase for showing great skill at something without formal training in it

Why do neural networks need so many training examples to perform?

How do I say "Brexit" in Latin?

The effects of magnetism in radio transmissions

Broken patches on a road

Compress command output by piping to bzip2

What is the purpose of easy combat scenarios that don't need resource expenditure?

Does Windows 10's telemetry include sending *.doc files if Word crashed?

Is it a fallacy if someone claims they need an explanation for every word of your argument to the point where they don't understand common terms?

Why Smart Plugs don't require setting port forwarding on router and how to accomplish this with NodeMCU (ESP8266)

Cryptic with missing capitals

Do authors have to be politically correct in article-writing?

Why did other German political parties disband so fast when Hitler was appointed chancellor?

Is a debit card dangerous for an account with low balance and no overdraft protection?

How would one buy a used TIE Fighter or X-Wing?

Oracle ODBC Connection - need some help!

SQL Developer cannot connect to Oracle database, yet sqlplus can!Testing an Oracle DB connection before it is made - ERROR?How to start running queries in Oracle?“ORA-01017: invalid username/password” while connecting to an instance remotely as sysdbalocal login from DBA group member (as sysdba) not workingmac os - virtualbox - oracle connection error - invalid username/password; logon deniedTNS Time out Error ORA-12170ORA-01017 connecting to example schemas on Oracle VM appliance from Windows hostOracle 12c connection configuration errorsConnect Ms Access to Oracle via LDAP

0

I am experiencing a very strange issue when creating a Windows7 x32 ODBC to connect to Oracle 12c.

I keep getting this error when I click the "Test Connect" button in the Windows ODBC Applet "ORA-01017: invalid
useranme/password; logon denied". However I am able to connect using sqlplus and Oracle SQL Developer using
the same TNS name and same exact credential. If I pick another TNS name (say Production), the connection
is successful but I having trouble connecting to this non-prod instance.

Does anyone have any idea or suggestion?

Thank you.

oracle

share|improve this question

asked Nov 1 '17 at 18:49

sydneysydney

213

bumped to the homepage by Community♦ 1 min ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oracle is too dumb to lie about that. If you are getting an ORA-01017 you are either not supplying the credentials you think you are, or you are not connecting to the database you think you are. Do you happen to have multiple tnsnames.ora files lurking on the client machine? Don't say "no" until you actually check.
  
  – EdStevens
  Nov 1 '17 at 21:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I just scanned my desktop. I have two tnsnames.ora and it's located in these two directories: C:apporacleproduct11.2.0client_1networkadmin and C:apporacleproduct12.1.0dbhome_1NETWORKADMIN. The first contains the 11gR2 client install while the latter is the actual Oracle 12c database. When I make a change to the tnsnames.ora under the client directory, it gets reflected in the Windows ODBC screens. The ODBC screen does not look at the other tnsnames.ora.
  
  – sydney
  Nov 1 '17 at 23:16
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just for the purpose of this troubleshooting, I even deleted the tnsnames.ora under my 12c directory and I still get the ORA-01017.
  
  – sydney
  Nov 1 '17 at 23:22
  

  
  
  
  

add a comment | 

0

I am experiencing a very strange issue when creating a Windows7 x32 ODBC to connect to Oracle 12c.

I keep getting this error when I click the "Test Connect" button in the Windows ODBC Applet "ORA-01017: invalid
useranme/password; logon denied". However I am able to connect using sqlplus and Oracle SQL Developer using
the same TNS name and same exact credential. If I pick another TNS name (say Production), the connection
is successful but I having trouble connecting to this non-prod instance.

Does anyone have any idea or suggestion?

Thank you.

oracle

share|improve this question

asked Nov 1 '17 at 18:49

sydneysydney

213

bumped to the homepage by Community♦ 1 min ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oracle is too dumb to lie about that. If you are getting an ORA-01017 you are either not supplying the credentials you think you are, or you are not connecting to the database you think you are. Do you happen to have multiple tnsnames.ora files lurking on the client machine? Don't say "no" until you actually check.
  
  – EdStevens
  Nov 1 '17 at 21:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I just scanned my desktop. I have two tnsnames.ora and it's located in these two directories: C:apporacleproduct11.2.0client_1networkadmin and C:apporacleproduct12.1.0dbhome_1NETWORKADMIN. The first contains the 11gR2 client install while the latter is the actual Oracle 12c database. When I make a change to the tnsnames.ora under the client directory, it gets reflected in the Windows ODBC screens. The ODBC screen does not look at the other tnsnames.ora.
  
  – sydney
  Nov 1 '17 at 23:16
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just for the purpose of this troubleshooting, I even deleted the tnsnames.ora under my 12c directory and I still get the ORA-01017.
  
  – sydney
  Nov 1 '17 at 23:22
  

  
  
  
  

add a comment | 

I am experiencing a very strange issue when creating a Windows7 x32 ODBC to connect to Oracle 12c.

I keep getting this error when I click the "Test Connect" button in the Windows ODBC Applet "ORA-01017: invalid
useranme/password; logon denied". However I am able to connect using sqlplus and Oracle SQL Developer using
the same TNS name and same exact credential. If I pick another TNS name (say Production), the connection
is successful but I having trouble connecting to this non-prod instance.

Does anyone have any idea or suggestion?

Thank you.

oracle

share|improve this question

asked Nov 1 '17 at 18:49

sydneysydney

213

share|improve this question

asked Nov 1 '17 at 18:49

sydneysydney

213

share|improve this question

asked Nov 1 '17 at 18:49

sydneysydney

213

asked Nov 1 '17 at 18:49

sydneysydney

213

asked Nov 1 '17 at 18:49

sydneysydney

213

1 Answer
1

active

oldest

votes

0

You say that you have two clients installed - the 11g client and the 12c client. Are you certain that you are using the 12c client? Because if you deleted your tnsnames.ora file under the 12c client directory, your error message should have changed. This leads me to believe that you are likely not using the correct client. In a comment you said:

C:apporacleproduct11.2.0client_1networkadmin and
C:apporacleproduct12.1.0dbhome_1NETWORKADMIN. The first
contains the 11gR2 client install while the latter is the actual
Oracle 12c database. When I make a change to the tnsnames.ora under
the client directory, it gets reflected in the Windows ODBC screens.

This makes me think that my suspicion about multiple client issue is correct. To test this, open a new command prompt window and issue the following command.

tnsping [DATABASE]

Where [DATABASE] is the TNS entry you would like to test. This will tell you which client your system is defaulting to. If you are in fact using the 12c client, you should see something similar to this immediately following the tnsping command:

TNS Ping Utility for 64-bit Windows: Version 12.1.0.2.0

If you do not see Version 12, you are using the 11g client. To fix this, you can modify your PATH system variable but you will need administrative access. Search "view advanced system settings" in the windows search bar, go to the "Advanced" tab, then navigate to Environment Variables. Scroll down the System Variables list, find PATH, and then modify the string so that the reference to the 12c client appears BEFORE the reference to the 11g client.

To make sure it's configured correctly, try another tnsping command.

share|improve this answer

answered Nov 2 '17 at 15:13

cdb_dbacdb_dba

1364

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Problem solved. This has nothing to do with me (or my desktop actually). It has to do with the way how the password is being restored by the script the Oracle DBA runs at night. I was told something about the encrypted password. They created a brand new user account as a test and I had no problem connecting via odbc. solllodolllo: just FYI. my desktop IS USING the 11g ORA.
  
  – sydney
  Nov 2 '17 at 19:53
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just to clarify ... My 12c directory contains the actual Oracle database and not the 12c client install. Well I guess if you install the 12c database you indirectly get the client binaries as well.
  
  – sydney
  Nov 2 '17 at 19:56
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f189882%2foracle-odbc-connection-need-some-help%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

You say that you have two clients installed - the 11g client and the 12c client. Are you certain that you are using the 12c client? Because if you deleted your tnsnames.ora file under the 12c client directory, your error message should have changed. This leads me to believe that you are likely not using the correct client. In a comment you said:

C:apporacleproduct11.2.0client_1networkadmin and
C:apporacleproduct12.1.0dbhome_1NETWORKADMIN. The first
contains the 11gR2 client install while the latter is the actual
Oracle 12c database. When I make a change to the tnsnames.ora under
the client directory, it gets reflected in the Windows ODBC screens.

This makes me think that my suspicion about multiple client issue is correct. To test this, open a new command prompt window and issue the following command.

tnsping [DATABASE]

Where [DATABASE] is the TNS entry you would like to test. This will tell you which client your system is defaulting to. If you are in fact using the 12c client, you should see something similar to this immediately following the tnsping command:

TNS Ping Utility for 64-bit Windows: Version 12.1.0.2.0

If you do not see Version 12, you are using the 11g client. To fix this, you can modify your PATH system variable but you will need administrative access. Search "view advanced system settings" in the windows search bar, go to the "Advanced" tab, then navigate to Environment Variables. Scroll down the System Variables list, find PATH, and then modify the string so that the reference to the 12c client appears BEFORE the reference to the 11g client.

To make sure it's configured correctly, try another tnsping command.

share|improve this answer

answered Nov 2 '17 at 15:13

cdb_dbacdb_dba

1364

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Problem solved. This has nothing to do with me (or my desktop actually). It has to do with the way how the password is being restored by the script the Oracle DBA runs at night. I was told something about the encrypted password. They created a brand new user account as a test and I had no problem connecting via odbc. solllodolllo: just FYI. my desktop IS USING the 11g ORA.
  
  – sydney
  Nov 2 '17 at 19:53
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just to clarify ... My 12c directory contains the actual Oracle database and not the 12c client install. Well I guess if you install the 12c database you indirectly get the client binaries as well.
  
  – sydney
  Nov 2 '17 at 19:56
  

  
  
  
  

add a comment | 

0

You say that you have two clients installed - the 11g client and the 12c client. Are you certain that you are using the 12c client? Because if you deleted your tnsnames.ora file under the 12c client directory, your error message should have changed. This leads me to believe that you are likely not using the correct client. In a comment you said:

C:apporacleproduct11.2.0client_1networkadmin and
C:apporacleproduct12.1.0dbhome_1NETWORKADMIN. The first
contains the 11gR2 client install while the latter is the actual
Oracle 12c database. When I make a change to the tnsnames.ora under
the client directory, it gets reflected in the Windows ODBC screens.

This makes me think that my suspicion about multiple client issue is correct. To test this, open a new command prompt window and issue the following command.

tnsping [DATABASE]

Where [DATABASE] is the TNS entry you would like to test. This will tell you which client your system is defaulting to. If you are in fact using the 12c client, you should see something similar to this immediately following the tnsping command:

TNS Ping Utility for 64-bit Windows: Version 12.1.0.2.0

If you do not see Version 12, you are using the 11g client. To fix this, you can modify your PATH system variable but you will need administrative access. Search "view advanced system settings" in the windows search bar, go to the "Advanced" tab, then navigate to Environment Variables. Scroll down the System Variables list, find PATH, and then modify the string so that the reference to the 12c client appears BEFORE the reference to the 11g client.

To make sure it's configured correctly, try another tnsping command.

share|improve this answer

answered Nov 2 '17 at 15:13

cdb_dbacdb_dba

1364

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Problem solved. This has nothing to do with me (or my desktop actually). It has to do with the way how the password is being restored by the script the Oracle DBA runs at night. I was told something about the encrypted password. They created a brand new user account as a test and I had no problem connecting via odbc. solllodolllo: just FYI. my desktop IS USING the 11g ORA.
  
  – sydney
  Nov 2 '17 at 19:53
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just to clarify ... My 12c directory contains the actual Oracle database and not the 12c client install. Well I guess if you install the 12c database you indirectly get the client binaries as well.
  
  – sydney
  Nov 2 '17 at 19:56
  

  
  
  
  

add a comment | 

You say that you have two clients installed - the 11g client and the 12c client. Are you certain that you are using the 12c client? Because if you deleted your tnsnames.ora file under the 12c client directory, your error message should have changed. This leads me to believe that you are likely not using the correct client. In a comment you said:

C:apporacleproduct11.2.0client_1networkadmin and
C:apporacleproduct12.1.0dbhome_1NETWORKADMIN. The first
contains the 11gR2 client install while the latter is the actual
Oracle 12c database. When I make a change to the tnsnames.ora under
the client directory, it gets reflected in the Windows ODBC screens.

This makes me think that my suspicion about multiple client issue is correct. To test this, open a new command prompt window and issue the following command.

tnsping [DATABASE]

Where [DATABASE] is the TNS entry you would like to test. This will tell you which client your system is defaulting to. If you are in fact using the 12c client, you should see something similar to this immediately following the tnsping command:

TNS Ping Utility for 64-bit Windows: Version 12.1.0.2.0

If you do not see Version 12, you are using the 11g client. To fix this, you can modify your PATH system variable but you will need administrative access. Search "view advanced system settings" in the windows search bar, go to the "Advanced" tab, then navigate to Environment Variables. Scroll down the System Variables list, find PATH, and then modify the string so that the reference to the 12c client appears BEFORE the reference to the 11g client.

To make sure it's configured correctly, try another tnsping command.

share|improve this answer

answered Nov 2 '17 at 15:13

cdb_dbacdb_dba

1364

tnsping [DATABASE]

TNS Ping Utility for 64-bit Windows: Version 12.1.0.2.0

share|improve this answer

answered Nov 2 '17 at 15:13

cdb_dbacdb_dba

1364

answered Nov 2 '17 at 15:13

cdb_dbacdb_dba

1364

answered Nov 2 '17 at 15:13

cdb_dbacdb_dba

1364