Oracle ODBC Connection - need some help!
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
asked Nov 1 '17 at 18:49
sydneysydney
213
bumped to the homepage by Community♦ 18 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
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
asked Nov 1 '17 at 18:49
sydneysydney
213
bumped to the homepage by Community♦ 18 mins 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
asked Nov 1 '17 at 18:49
sydneysydney
213
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
oracle
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
asked Nov 1 '17 at 18:49
sydneysydney
213
asked Nov 1 '17 at 18:49
sydneysydney
213
213
bumped to the homepage by Community♦ 18 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 18 mins 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 |
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
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
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
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
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 |
1 Answer
1
active
oldest
votes
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.
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
});
}
});
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
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
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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.
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.
answered Nov 2 '17 at 15:13
cdb_dbacdb_dba
1364
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.
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
answered Nov 2 '17 at 15:13
cdb_dbacdb_dba
1364
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 |
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
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
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
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 |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
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