ID: 9876
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Closed
Bug Type: OCI8 related
Operating System: Redhat 6.1 Linux
PHP Version: 4.0.4pl1
New Comment:
Hello,
I have same problem under
RedHat 6.1 / 7.2
Oracle 7.3.4 / 8.1.5
PHP 4.1.2 (--with-oci8)
Apache 1.3.23
I have to restart whole webserver after Database restart. I would like
to use OCIPLogon because of performance issue for very small SELECT's.
Previous Comments:
------------------------------------------------------------------------
[2001-05-04 10:35:58] [EMAIL PROTECTED]
plz try 4.0.5 - if the problem persists please reopen.
------------------------------------------------------------------------
[2001-03-20 11:55:31] [EMAIL PROTECTED]
./configure' '--prefix=/var/php' '--with-config-file-path=/var/php'
'--enable-track-vars'
'--enable-sigchild'
'--with-apache=../apache_1.3.14' '--with-ftp' '--with-xml'
'--with-mcrypt=/var/libmcrypt' '--with-pgsql=/var/postgresql'
'--with-oci8=/u01/app/oracle/product/8.1.6' '--with-mysql=/var/mysql'
When using OCIPLogon for persistent connections, I'm noticing that
after restarting Oracle, that my PHP application starts getting Oracle
errors(ORA-03113 and ORA-03114). This can be fixed by restarting the
webserver after restarting Oracle. I also notice that changing my
Oracle connections from OCIPLogon to OCILogon fixes the problem - after
making that change I get no errors after restarting Oracle, and I
*don't* have to restart the webserver.
The OCI8 interface must have a bug, right? I shouldn't have to restart
the webserver after restarting Oracle just because I'm using persistent
connections, should I?
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=9876&edit=1
