Use LDAP for name look up with Oracle Instant Client
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Partly as a result of having problems with conflicting versions or bitness with the full installation of Oracle client, my development team (of which I'm a member) has been moving towards using Oracle Instant Client and avoiding the installation on our development machines for most new projects. This has worked out pretty well, even to the point that we deploy to production with this setup. Since we're mostly a .NET shop, we're using the native client (with .NET wrappers), rather than the Java one.
Now a client is requiring that we register the database service with an LDAP server and use the LDAP server for name look up. They have provided sqlnet.ora and ldap.ora files (and an accompanying encryption config file) that appear to be correct. In particular, the sqlnet.ora file does specify LDAP as a possible source for looking up net service names:
names.directory_path=(tnsnames,ldap)
I am confident that the machine I'm working with can use LDAP to access the service since I was able to do so using SQL Developer (which allowed me to input the LDAP information directly). Assuming they are correct, how can I get Instant Client to recognize this configuration and use LDAP for the name look up?
What I've tried so far
I have tried setting the TNS_ADMIN environment variable to the directory that contains the provided files, and while this works fine for making Instant Client recognize a tnsnames.ora file, it doesn't seem to be enough to get it to start looking at LDAP. Here are the results (with paths, usernames, and passwords changed):
(The following commands happen to be Windows Command Prompt, but I imagine something similar is doable on Linux. The sqlplus seen here is the Instant version as well, with accompanying Instant Client binaries in the same directory.)
C:TEMP>SET TNS_ADMIN=C:pathtosqlnetldapandtnsnamesorafiles
C:TEMP>echo %TNS_ADMIN%
C:pathtosqlnetldapandtnsnamesorafiles
C:TEMP>sqlplus.exe USERNAME/PASSWORD@LOCALTNSNAME
SQL*Plus: Release 11.2.0.2.0 Production on Mon Jul 7 10:22:25 2014
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Produ
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
C:TEMP>sqlplus.exe USERNAME/PASSWORD@LDAPTNSNAME
SQL*Plus: Release 11.2.0.2.0 Production on Mon Jul 7 10:24:21 2014
Copyright (c) 1982, 2010, Oracle. All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified
Side note
Are there tags for TNS, LDAP, or Instant Client (or even just normal Oracle Client) that could be added to this question? I couldn't locate any.
oracle
bumped to the homepage by Community♦ 14 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 4 more comments
Partly as a result of having problems with conflicting versions or bitness with the full installation of Oracle client, my development team (of which I'm a member) has been moving towards using Oracle Instant Client and avoiding the installation on our development machines for most new projects. This has worked out pretty well, even to the point that we deploy to production with this setup. Since we're mostly a .NET shop, we're using the native client (with .NET wrappers), rather than the Java one.
Now a client is requiring that we register the database service with an LDAP server and use the LDAP server for name look up. They have provided sqlnet.ora and ldap.ora files (and an accompanying encryption config file) that appear to be correct. In particular, the sqlnet.ora file does specify LDAP as a possible source for looking up net service names:
names.directory_path=(tnsnames,ldap)
I am confident that the machine I'm working with can use LDAP to access the service since I was able to do so using SQL Developer (which allowed me to input the LDAP information directly). Assuming they are correct, how can I get Instant Client to recognize this configuration and use LDAP for the name look up?
What I've tried so far
I have tried setting the TNS_ADMIN environment variable to the directory that contains the provided files, and while this works fine for making Instant Client recognize a tnsnames.ora file, it doesn't seem to be enough to get it to start looking at LDAP. Here are the results (with paths, usernames, and passwords changed):
(The following commands happen to be Windows Command Prompt, but I imagine something similar is doable on Linux. The sqlplus seen here is the Instant version as well, with accompanying Instant Client binaries in the same directory.)
C:TEMP>SET TNS_ADMIN=C:pathtosqlnetldapandtnsnamesorafiles
C:TEMP>echo %TNS_ADMIN%
C:pathtosqlnetldapandtnsnamesorafiles
C:TEMP>sqlplus.exe USERNAME/PASSWORD@LOCALTNSNAME
SQL*Plus: Release 11.2.0.2.0 Production on Mon Jul 7 10:22:25 2014
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Produ
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
C:TEMP>sqlplus.exe USERNAME/PASSWORD@LDAPTNSNAME
SQL*Plus: Release 11.2.0.2.0 Production on Mon Jul 7 10:24:21 2014
Copyright (c) 1982, 2010, Oracle. All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified
Side note
Are there tags for TNS, LDAP, or Instant Client (or even just normal Oracle Client) that could be added to this question? I couldn't locate any.
oracle
bumped to the homepage by Community♦ 14 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Is it the correct executable? "where sqlplus"
– Bjarte Brandt
Jul 7 '14 at 19:25
@BjarteBrandt Yes, it is the one I expect it to be when I runwhere(C:TEMPsqlplus.exe). To be more specific,sqlplusis not "installed" on the machine. It's just sitting in the current directory, with the client binaries beside it. It's definitely picking up on thetnsnames.orafile using theTNS_ADMINenvironment variable, since that is off in a completely different directory.
– jpmc26
Jul 7 '14 at 19:26
@BjarteBrandt To confirm it's using the right client binaries, I went ahead and ranwhere oci.dll, too. It also gives the expected result:C:TEMPoci.dll.
– jpmc26
Jul 7 '14 at 19:30
could be a domain issue. Did you also try with FQ name? (dbname_or_whatever.domainname)
– ik_zelf
Jul 7 '14 at 20:41
2
@ora-600 Sorry, I forgot about this question. It turned out to be problems with the config files themselves, which were provided to us by our client. (Possibly the Kerberos config file; I can't recall off-hand.) What's funny is that I was working in a dev environment trying to do this, it was equally problematic to get it working in staging, and it still isn't working in prod as far as I know. (We ended up using a local TNS name to get the app working.) Definitely wasted money for the project; even if/when it works in prod, the return on investment would be miniscule compared to the cost.
– jpmc26
Dec 22 '14 at 16:55
|
show 4 more comments
Partly as a result of having problems with conflicting versions or bitness with the full installation of Oracle client, my development team (of which I'm a member) has been moving towards using Oracle Instant Client and avoiding the installation on our development machines for most new projects. This has worked out pretty well, even to the point that we deploy to production with this setup. Since we're mostly a .NET shop, we're using the native client (with .NET wrappers), rather than the Java one.
Now a client is requiring that we register the database service with an LDAP server and use the LDAP server for name look up. They have provided sqlnet.ora and ldap.ora files (and an accompanying encryption config file) that appear to be correct. In particular, the sqlnet.ora file does specify LDAP as a possible source for looking up net service names:
names.directory_path=(tnsnames,ldap)
I am confident that the machine I'm working with can use LDAP to access the service since I was able to do so using SQL Developer (which allowed me to input the LDAP information directly). Assuming they are correct, how can I get Instant Client to recognize this configuration and use LDAP for the name look up?
What I've tried so far
I have tried setting the TNS_ADMIN environment variable to the directory that contains the provided files, and while this works fine for making Instant Client recognize a tnsnames.ora file, it doesn't seem to be enough to get it to start looking at LDAP. Here are the results (with paths, usernames, and passwords changed):
(The following commands happen to be Windows Command Prompt, but I imagine something similar is doable on Linux. The sqlplus seen here is the Instant version as well, with accompanying Instant Client binaries in the same directory.)
C:TEMP>SET TNS_ADMIN=C:pathtosqlnetldapandtnsnamesorafiles
C:TEMP>echo %TNS_ADMIN%
C:pathtosqlnetldapandtnsnamesorafiles
C:TEMP>sqlplus.exe USERNAME/PASSWORD@LOCALTNSNAME
SQL*Plus: Release 11.2.0.2.0 Production on Mon Jul 7 10:22:25 2014
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Produ
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
C:TEMP>sqlplus.exe USERNAME/PASSWORD@LDAPTNSNAME
SQL*Plus: Release 11.2.0.2.0 Production on Mon Jul 7 10:24:21 2014
Copyright (c) 1982, 2010, Oracle. All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified
Side note
Are there tags for TNS, LDAP, or Instant Client (or even just normal Oracle Client) that could be added to this question? I couldn't locate any.
oracle
Partly as a result of having problems with conflicting versions or bitness with the full installation of Oracle client, my development team (of which I'm a member) has been moving towards using Oracle Instant Client and avoiding the installation on our development machines for most new projects. This has worked out pretty well, even to the point that we deploy to production with this setup. Since we're mostly a .NET shop, we're using the native client (with .NET wrappers), rather than the Java one.
Now a client is requiring that we register the database service with an LDAP server and use the LDAP server for name look up. They have provided sqlnet.ora and ldap.ora files (and an accompanying encryption config file) that appear to be correct. In particular, the sqlnet.ora file does specify LDAP as a possible source for looking up net service names:
names.directory_path=(tnsnames,ldap)
I am confident that the machine I'm working with can use LDAP to access the service since I was able to do so using SQL Developer (which allowed me to input the LDAP information directly). Assuming they are correct, how can I get Instant Client to recognize this configuration and use LDAP for the name look up?
What I've tried so far
I have tried setting the TNS_ADMIN environment variable to the directory that contains the provided files, and while this works fine for making Instant Client recognize a tnsnames.ora file, it doesn't seem to be enough to get it to start looking at LDAP. Here are the results (with paths, usernames, and passwords changed):
(The following commands happen to be Windows Command Prompt, but I imagine something similar is doable on Linux. The sqlplus seen here is the Instant version as well, with accompanying Instant Client binaries in the same directory.)
C:TEMP>SET TNS_ADMIN=C:pathtosqlnetldapandtnsnamesorafiles
C:TEMP>echo %TNS_ADMIN%
C:pathtosqlnetldapandtnsnamesorafiles
C:TEMP>sqlplus.exe USERNAME/PASSWORD@LOCALTNSNAME
SQL*Plus: Release 11.2.0.2.0 Production on Mon Jul 7 10:22:25 2014
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Produ
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
C:TEMP>sqlplus.exe USERNAME/PASSWORD@LDAPTNSNAME
SQL*Plus: Release 11.2.0.2.0 Production on Mon Jul 7 10:24:21 2014
Copyright (c) 1982, 2010, Oracle. All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified
Side note
Are there tags for TNS, LDAP, or Instant Client (or even just normal Oracle Client) that could be added to this question? I couldn't locate any.
oracle
oracle
asked Jul 7 '14 at 17:58
jpmc26jpmc26
8101127
8101127
bumped to the homepage by Community♦ 14 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♦ 14 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Is it the correct executable? "where sqlplus"
– Bjarte Brandt
Jul 7 '14 at 19:25
@BjarteBrandt Yes, it is the one I expect it to be when I runwhere(C:TEMPsqlplus.exe). To be more specific,sqlplusis not "installed" on the machine. It's just sitting in the current directory, with the client binaries beside it. It's definitely picking up on thetnsnames.orafile using theTNS_ADMINenvironment variable, since that is off in a completely different directory.
– jpmc26
Jul 7 '14 at 19:26
@BjarteBrandt To confirm it's using the right client binaries, I went ahead and ranwhere oci.dll, too. It also gives the expected result:C:TEMPoci.dll.
– jpmc26
Jul 7 '14 at 19:30
could be a domain issue. Did you also try with FQ name? (dbname_or_whatever.domainname)
– ik_zelf
Jul 7 '14 at 20:41
2
@ora-600 Sorry, I forgot about this question. It turned out to be problems with the config files themselves, which were provided to us by our client. (Possibly the Kerberos config file; I can't recall off-hand.) What's funny is that I was working in a dev environment trying to do this, it was equally problematic to get it working in staging, and it still isn't working in prod as far as I know. (We ended up using a local TNS name to get the app working.) Definitely wasted money for the project; even if/when it works in prod, the return on investment would be miniscule compared to the cost.
– jpmc26
Dec 22 '14 at 16:55
|
show 4 more comments
Is it the correct executable? "where sqlplus"
– Bjarte Brandt
Jul 7 '14 at 19:25
@BjarteBrandt Yes, it is the one I expect it to be when I runwhere(C:TEMPsqlplus.exe). To be more specific,sqlplusis not "installed" on the machine. It's just sitting in the current directory, with the client binaries beside it. It's definitely picking up on thetnsnames.orafile using theTNS_ADMINenvironment variable, since that is off in a completely different directory.
– jpmc26
Jul 7 '14 at 19:26
@BjarteBrandt To confirm it's using the right client binaries, I went ahead and ranwhere oci.dll, too. It also gives the expected result:C:TEMPoci.dll.
– jpmc26
Jul 7 '14 at 19:30
could be a domain issue. Did you also try with FQ name? (dbname_or_whatever.domainname)
– ik_zelf
Jul 7 '14 at 20:41
2
@ora-600 Sorry, I forgot about this question. It turned out to be problems with the config files themselves, which were provided to us by our client. (Possibly the Kerberos config file; I can't recall off-hand.) What's funny is that I was working in a dev environment trying to do this, it was equally problematic to get it working in staging, and it still isn't working in prod as far as I know. (We ended up using a local TNS name to get the app working.) Definitely wasted money for the project; even if/when it works in prod, the return on investment would be miniscule compared to the cost.
– jpmc26
Dec 22 '14 at 16:55
Is it the correct executable? "where sqlplus"
– Bjarte Brandt
Jul 7 '14 at 19:25
Is it the correct executable? "where sqlplus"
– Bjarte Brandt
Jul 7 '14 at 19:25
@BjarteBrandt Yes, it is the one I expect it to be when I run
where (C:TEMPsqlplus.exe). To be more specific, sqlplus is not "installed" on the machine. It's just sitting in the current directory, with the client binaries beside it. It's definitely picking up on the tnsnames.ora file using the TNS_ADMIN environment variable, since that is off in a completely different directory.– jpmc26
Jul 7 '14 at 19:26
@BjarteBrandt Yes, it is the one I expect it to be when I run
where (C:TEMPsqlplus.exe). To be more specific, sqlplus is not "installed" on the machine. It's just sitting in the current directory, with the client binaries beside it. It's definitely picking up on the tnsnames.ora file using the TNS_ADMIN environment variable, since that is off in a completely different directory.– jpmc26
Jul 7 '14 at 19:26
@BjarteBrandt To confirm it's using the right client binaries, I went ahead and ran
where oci.dll, too. It also gives the expected result: C:TEMPoci.dll.– jpmc26
Jul 7 '14 at 19:30
@BjarteBrandt To confirm it's using the right client binaries, I went ahead and ran
where oci.dll, too. It also gives the expected result: C:TEMPoci.dll.– jpmc26
Jul 7 '14 at 19:30
could be a domain issue. Did you also try with FQ name? (dbname_or_whatever.domainname)
– ik_zelf
Jul 7 '14 at 20:41
could be a domain issue. Did you also try with FQ name? (dbname_or_whatever.domainname)
– ik_zelf
Jul 7 '14 at 20:41
2
2
@ora-600 Sorry, I forgot about this question. It turned out to be problems with the config files themselves, which were provided to us by our client. (Possibly the Kerberos config file; I can't recall off-hand.) What's funny is that I was working in a dev environment trying to do this, it was equally problematic to get it working in staging, and it still isn't working in prod as far as I know. (We ended up using a local TNS name to get the app working.) Definitely wasted money for the project; even if/when it works in prod, the return on investment would be miniscule compared to the cost.
– jpmc26
Dec 22 '14 at 16:55
@ora-600 Sorry, I forgot about this question. It turned out to be problems with the config files themselves, which were provided to us by our client. (Possibly the Kerberos config file; I can't recall off-hand.) What's funny is that I was working in a dev environment trying to do this, it was equally problematic to get it working in staging, and it still isn't working in prod as far as I know. (We ended up using a local TNS name to get the app working.) Definitely wasted money for the project; even if/when it works in prod, the return on investment would be miniscule compared to the cost.
– jpmc26
Dec 22 '14 at 16:55
|
show 4 more comments
1 Answer
1
active
oldest
votes
Place the sqlnet.ora and ldap.ora files in your $ORACLE_ADMIN directory and make sure to set the environment variables. I made mine the TNS_ADMIN directory
(Linux) my .bashrc
export TNS_ADMIN=/opt/oracle/instantclient_12_1/network/admin
export ORACLE_ADMIN=${TNS_ADMIN}
[ku14lts:/opt/oracle/instantclient_12_1/network/admin]
$ ls
ldap.ora sqlnet.ora tnsnames.ora
And I was able to connect to a DB not in my tnsnames.ora
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%2f69882%2fuse-ldap-for-name-look-up-with-oracle-instant-client%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
Place the sqlnet.ora and ldap.ora files in your $ORACLE_ADMIN directory and make sure to set the environment variables. I made mine the TNS_ADMIN directory
(Linux) my .bashrc
export TNS_ADMIN=/opt/oracle/instantclient_12_1/network/admin
export ORACLE_ADMIN=${TNS_ADMIN}
[ku14lts:/opt/oracle/instantclient_12_1/network/admin]
$ ls
ldap.ora sqlnet.ora tnsnames.ora
And I was able to connect to a DB not in my tnsnames.ora
add a comment |
Place the sqlnet.ora and ldap.ora files in your $ORACLE_ADMIN directory and make sure to set the environment variables. I made mine the TNS_ADMIN directory
(Linux) my .bashrc
export TNS_ADMIN=/opt/oracle/instantclient_12_1/network/admin
export ORACLE_ADMIN=${TNS_ADMIN}
[ku14lts:/opt/oracle/instantclient_12_1/network/admin]
$ ls
ldap.ora sqlnet.ora tnsnames.ora
And I was able to connect to a DB not in my tnsnames.ora
add a comment |
Place the sqlnet.ora and ldap.ora files in your $ORACLE_ADMIN directory and make sure to set the environment variables. I made mine the TNS_ADMIN directory
(Linux) my .bashrc
export TNS_ADMIN=/opt/oracle/instantclient_12_1/network/admin
export ORACLE_ADMIN=${TNS_ADMIN}
[ku14lts:/opt/oracle/instantclient_12_1/network/admin]
$ ls
ldap.ora sqlnet.ora tnsnames.ora
And I was able to connect to a DB not in my tnsnames.ora
Place the sqlnet.ora and ldap.ora files in your $ORACLE_ADMIN directory and make sure to set the environment variables. I made mine the TNS_ADMIN directory
(Linux) my .bashrc
export TNS_ADMIN=/opt/oracle/instantclient_12_1/network/admin
export ORACLE_ADMIN=${TNS_ADMIN}
[ku14lts:/opt/oracle/instantclient_12_1/network/admin]
$ ls
ldap.ora sqlnet.ora tnsnames.ora
And I was able to connect to a DB not in my tnsnames.ora
edited Feb 6 '18 at 13:57
McNets
16.4k42261
16.4k42261
answered Dec 29 '15 at 21:45
MarkMark
1
1
add a comment |
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%2f69882%2fuse-ldap-for-name-look-up-with-oracle-instant-client%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
Is it the correct executable? "where sqlplus"
– Bjarte Brandt
Jul 7 '14 at 19:25
@BjarteBrandt Yes, it is the one I expect it to be when I run
where(C:TEMPsqlplus.exe). To be more specific,sqlplusis not "installed" on the machine. It's just sitting in the current directory, with the client binaries beside it. It's definitely picking up on thetnsnames.orafile using theTNS_ADMINenvironment variable, since that is off in a completely different directory.– jpmc26
Jul 7 '14 at 19:26
@BjarteBrandt To confirm it's using the right client binaries, I went ahead and ran
where oci.dll, too. It also gives the expected result:C:TEMPoci.dll.– jpmc26
Jul 7 '14 at 19:30
could be a domain issue. Did you also try with FQ name? (dbname_or_whatever.domainname)
– ik_zelf
Jul 7 '14 at 20:41
2
@ora-600 Sorry, I forgot about this question. It turned out to be problems with the config files themselves, which were provided to us by our client. (Possibly the Kerberos config file; I can't recall off-hand.) What's funny is that I was working in a dev environment trying to do this, it was equally problematic to get it working in staging, and it still isn't working in prod as far as I know. (We ended up using a local TNS name to get the app working.) Definitely wasted money for the project; even if/when it works in prod, the return on investment would be miniscule compared to the cost.
– jpmc26
Dec 22 '14 at 16:55