On 07/14/2010 03:34 AM, John Scoles wrote: <<--gone-->>
>> httpd: symbol lookup error: /nfs/private/user/sns/tech-stack/ >> 10.06.28.03/linux/lib/perl5/site_perl/5.8.8/i686-linux-64int/auto/DBD/Oracle/Oracle.so: >> undefined symbol: ora_sql_error >> httpd: symbol lookup error: /nfs/private/user/sns/tech-stack/ >> 10.06.28.03/linux/lib/perl5/site_perl/5.8.8/i686-linux-64int/auto/DBD/Oracle/Oracle.so: >> undefined symbol: ora_db_commit >> >> The OS is >> >> % cat /etc/redhat-release >> Red Hat Enterprise Linux AS release 4 (Nahant Update 8) >> >> >> But the same works on machine with following Red Hat release >> >> Red Hat Enterprise Linux AS release 3 (Taroon Update 8) >> >> Server version: Apache/2.2.9 (Unix) >> >> perl is v5.8.8 built for i686-linux-64int >> >> mod_perl is 2.0.4 >> >> Oracle client and Server : 10.2.0.4.0 >> >> I have rebuilt Oracle Home/perl(with and without thread >> enabled)/Apache/Mod_Perl >> >> And it seems to be working from stand alone process and when called from >> Apache child process we are getting undefined symbol error >> >> I have attached log files of build , also perl Makefile.PL -s ora_db_commit >> doesn't return me anything interesting >> >> --Shibi Ns-- I had seen the original earlier but hadn't taken a close look until I saw John's response. I wonder if this is a security or file permissions issue? The path given for the error indicates the file being accessed is an NFS mount (/nfs/...). You state that when you, a regular user, run the command as a "stand alone process", it works, but when run under Apache, it fails. Since Apache runs as user 'apache', it wouldn't necessarily have access to the directory '/nfs/private/user/sns/', which I presume is your home directory on the remote system, while you certainly have access. Access to this directory could be controlled in several ways. First, the file/directory permissions may not allow access for 'others' (world). Or, since access appears to be OK for one OS and not the other, there may be some higher level security setup on RHEL AS 4 that does not allow NFS file access for system daemons. Another possibility is that all the files are locally available on the RHEL AS 3 system. I would suggest getting everything onto the RHEL AS 4 system, in "standard" locations, and try again. I hope this helps;) -- Bob McGowan
