Re: [PHP4BETA] Redhat 6.2, PHP4RC1, Oracle 8.1.5?
| From: | Kevin Hendrix | Date: | Thu, 27 Apr 2000 16:10:40 +0000 |
| Subject: | Re: [PHP4BETA] Redhat 6.2, PHP4RC1, Oracle 8.1.5? | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-14088@lists.php.net to get a copy of this message | ||
Hi.
It seemed that the root of the problem was in linking the libclntsh.so oracle
library into PHP ... this was not actually the case as I discovered when I
attempted to add mod_auth_ora8 into apache. There is actually some fatal
interaction between apache (1.3.12) and DSOs using the oracle 8.1.5 libraries
on RedHat.
So far, with the help of Benjamin Peikes and Stephan Bauer, multiple solutions
have been found to the PHP/Oracle problem.
Complex Solution (using oracle 8.1.5 libraries):
- Compile and install PHP as a DSO to apache without any oracle support.
- Alter the php config header (php_config.h for php4) to add oracle and/or
oci support:
HAVE_ORACLE 1
HAVE_OCI8 1
- Compile the oracle.c and oci8.c php functions as stand-alone php
extensions.
- Alter the php.ini file to load the oracle extensions as necessary.
I never finished testing this solution since it became obvious it would not
help me solve the mod_auth_ora8 problem. This solution did, however, produce
a running apache web server with php DSO and oracle extensions ... database
connectivity was not tested.
Simple Solution:
- Use Oracle 8.0.5 libraries for all your apache related modules.
With this solution, you can build your oracle routines directly into PHP (no
funky extensions), and you can build other DSOs for apache (mod_auth_ora8)
with no problem. This one is verified working and is actively connecting
to an Oracle 8.1.5 server.
kevin
khendrix@pennypi.com
Kevin Hendrix wrote:
>
> Hi.
>
> Is there a known issue between Redhat 6.2, PHP4, and Oracle 8.1.5? All I
> get are segmentation faults ... no core file, nothing in any log file ... in
> essence, no useful information whatsoever. When run through gdb, I get
> Cannot access memory at address 0x40a8fb14
>
> I've seen references to people falling back to Oracle 8.0.x to fix similar
> problems ... is that the only answer available currently?
>
> Any help would be appreciated. Thanks!
> kevin
> khendrix@pennypi.com
>