#42496 [Com]: cursor is not closed when using 2 clobs in a select query

ID: 42496 Comment by: ghosh at q-one dot com Reported By: iddekingej at lycos dot com Status: Open Bug Type: OCI8 related Operating System: win 2000 PHP Version: 5.2.4 New Comment: I'm using OCI8 1.2.4 with Oracle 11g. A previous version doesnt seem to work, so I cannot test with 1.2.3. It also says so in the changelog for 1.2.4: Add Oracle 11g support. Now, whenever I select (c)lobs (even with only 1 lob column),, the table v$temporary_lobs keeps filling up and UGA memory is consumed for each row that's being read until the server aborts with an out-of-memory error. This does not happen when I run my statements directly via SQLplus, so it seems to be an OCI8/PHP bug. So, is this related to this bug or should I file a new one? Previous Comments: ------------------------------------------------------------------------ [2007-11-15 13:55:42] markus dot knecht at psi dot ch What i see after upgrading to PHP 5.2.5: NOT Working: oci8 1.2.4,$Revision: 1.269.2.16.2.38 $ Working : oci8 1.2.3,$Revision: 1.269.2.16.2.29 $ ------------------------------------------------------------------------ [2007-11-13 21:38:44] iarenuno at eteo dot mondragon dot edu I can confirm that 1.2.4 has the bug, but 1.2.3 ($Revision: 1.269.2.16.2.30 $) doesn't have it. Saludos. Iñaki. ------------------------------------------------------------------------ [2007-11-09 11:28:26] br at absb dot de We can reproduce the problem with OCI8 versions before 1.2.4: Version 1.2.3, $Revision: 1.269.2.16.2.32 $ ------------------------------------------------------------------------ [2007-11-09 03:21:13] martin at catalyst dot net dot nz > Does setting oci8.statement_cache_size = 0 change the behavior? It does not in our tests, unfortunately. ------------------------------------------------------------------------ [2007-11-09 01:52:04] sixd@php.net Does setting oci8.statement_cache_size = 0 change the behavior? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/42496 -- Edit this bug report at http://bugs.php.net/?id=42496&edit=1