Forums / Install & configuration / Prb with database extension oracle: headers already sent

Prb with database extension oracle: headers already sent

Author Message

Olivier Pierret

Tuesday 16 August 2005 9:35:12 am

Hello all,

I have a big issue with Database Extension for oracle: after following carefully the installation and migration procedure of Database Extension. I had been able to run ezpublish with oracle. However a small issue was triggering from time to time. But now this issue is always triggering and prevent me from running ez publish. Here it is:

When I try to log I am always redirected to the login page with the following warnings:

session_start(): Cannot send session cookie - headers already sent in C:\Program Files\Apache Group\Apache2\htdocs\ezpublish-3.6.0\lib\ezutils\classes\ezsession.php on line 250 
session_start(): Cannot send session cache limiter - headers already sent in C:\Program Files\Apache Group\Apache2\htdocs\ezpublish-3.6.0\lib\ezutils\classes\ezsession.php on line 250
Cannot modify header information - headers already sent in C:\Program Files\Apache Group\Apache2\htdocs\ezpublish-3.6.0\index.php on line 419
.
.
.

I skipped the whole list of errors which are all related to the fact that headers are already sent.

I suspect that sth is writing in response stream before the headers are all set.

This happend only when using database extension i.e.

 DatabaseImplementation=ezoracle

I am using php 4.3.9 with php_oci8.dll (Revision: 1.183.2.17) Database Extension version is 1.2 - oracle client is instant client or oracle client 9.2 - oracle database server is 9.2.

Hope someone will be able to help me

Thank you

Olivier Pierret

Olivier Pierret

Thursday 18 August 2005 8:20:43 am

Well nobody knows...
Except that I found the solution and post it FYI. I used apache 2.054 and I switched to apache 1.3.33. So my guess is there is something wrong within ezoracle - OCI8 layer (multithreading maybe ?) that prevents ez oracle connector (database extension) from working properly with Apache2.

If this is the case it would be definitely useful that ez systems writes this down in the FAQ of ezoracle.

Should I enter a bug for this ? eZ crew, any thoughts ?

Vadym Savchuk

Thursday 25 August 2005 4:05:37 am

Hello.
We know about this bug.
The next ezoracle release will include a fix for it.

Lex 007

Thursday 25 August 2005 6:35:00 am

Salut Olivier ;-)

Could you please give us a little review of the extension : install, performance, etc ...

Thanks

Olivier Pierret

Thursday 25 August 2005 9:30:24 am

I tested the patch from eZ Systems and it works: the errors have disappear with Apache 2 and I can connect to administration interface without problems.

My guess regarding the multithreading were wrong I think, eZ Systems knows better what it was.

I tested Oracle extension on several systems, here is the "biggest" one:

Version: 3.6.0 (3.6.0)
SVN revision: 11973

Biprocessors Xeon 3 GHz
Memory: 2GB
Apache/1.3.33 (Win32) PHP/4.3.9 mod_jk/1.2.14

PHP extensions standard, bcmath, calendar, ctype, com, ftp, mysql, odbc, overload, pcre, session, tokenizer, xml, wddx, zlib, apache, mbstring, oci8, Turck MMCache

Oracle: Oracle9i Release 9.2.0.4.0 - Production

How long it gets to load first admin page

Time accumulators:
 Accumulator	 Elapsed	 Percent	 Count	 Average
ini_load				
Load cache	0.0647 sec	2.4232%	12	0.0054 sec
oracle_total				
Oracle_queries	0.0080 sec	0.2995%	10	0.0008 sec
Oracle looping results	0.0044 sec	0.1651%	10	0.0004 sec
Template Total	0.2261 sec	8.5%	2	0.1130 sec
Template load	0.0309 sec	1.1569%	2	0.0154 sec
Template processing	0.1947 sec	7.2936%	2	0.0973 sec
override				
Cache load	0.0219 sec	0.8222%	2	0.0110 sec
Total script time:	2.6690 sec	

Oracle queries time is 0.0080
Mysql queries time was 1.100 (roughly)
The others figures are comparable.

I faced three issues during with this extension:
1) the bug here above
2) a small bug in the sequence updating script (I was able to fix it myself)
3) a bug related to the char encoding (I think) of MySQL and Oracle: I got Oracle TWO-TASK ERROR (ORA-03106) when exporting data from MySQL to Oracle.

For the rest everything's fine ...

well don't forget to put character in the workflow event description (if not you'll have a "cannot insert null" but that's a detail).

Hope this helps.

Frederik Holljen

Thursday 25 August 2005 10:10:42 am

The "null" problem is a bug. I've reported it here:
http://ez.no/bugs/view/7083