So, there is no private tnsnames.ora nor $TNS_ADMIN defined on the server (or in httpd.conf) at all? I ask again, because if either of these situations exists, that would explain the problem.
BTW - Having Apache in the same group as the oracle software might be a gaping security hole. Just a thought. rr -----Original Message----- From: Angus McIntyre [mailto:[EMAIL PROTECTED] Sent: Friday, August 18, 2006 12:07 PM To: [email protected] Subject: RE: ORA-01017 ... but only when script is run as CGI On Fri, August 18, 2006 1:21 pm, Reidy, Ron wrote: > What happens if you try to connect to that same DB instance using > SQL*plus? sqlplus connects without problems, using the same username and password as the script (as mentioned, the script runs fine from the command line, but fails to connect when run as a CGI). > Does your CGI have use the same tnsnames.ora file as the > command line user? As far as I know, yes. It's using the same $ORACLE_HOME. The 'tnsnames.ora' file is world-readable (and in any case, the 'apache' user has been added to the 'oracle' group that owns all the files in the Oracle install). Thanks for your help, Angus > -- > Ron Reidy > Lead DBA > Array BioPharma, Inc. > > -----Original Message----- > From: Angus McIntyre [mailto:[EMAIL PROTECTED] > Sent: Friday, August 18, 2006 10:39 AM > To: [email protected] > Subject: ORA-01017 ... but only when script is run as CGI > > I'm using current versions of DBI and DBD::Oracle in a CGI script, > Oracle > 10.2 client talking to an Oracle 9 database, RedHat Linux. The script > previously ran successfully on a similar machine with the Oracle 9 > client. > > I have a simple test script, in which the username, password and SID are > hardcoded. If I run this script from the command line, it connects > without > problems. > > If I call the script as a CGI script, I get ORA-01017 in > OCISessionBegin, > which is the bad username or password error. > > As far as I can tell, environment variables are the same in both > contexts, > the same tnsnames.ora file is used, and so forth. I have identified and > resolved permissions errors, so I think that isn't the problem. > > Has anyone encountered something similar, or does anyone have any > suggestions for other things that I should check in order to resolve > this? > > Thanks, > > Angus > > > This electronic message transmission is a PRIVATE communication which > contains > information which may be confidential or privileged. The information is > intended > to be for the use of the individual or entity named above. If you are not > the > intended recipient, please be aware that any disclosure, copying, > distribution > or use of the contents of this information is prohibited. Please notify > the > sender of the delivery error by replying to this message, or notify us by > telephone (877-633-2436, ext. 0), and then delete it from your system. > > >
