ID: 37963 Updated by: [EMAIL PROTECTED] Reported By: ed at supergeek dot com -Status: Open +Status: Feedback -Bug Type: *Database Functions +Bug Type: ODBC related Operating System: Debian GNU/Linux 3.1 (sarge) PHP Version: 5.1.4 New Comment:
> Source code unlikely to be useful Well, just "something goes wrong here" is unlikely to be useful either. We need to know at least how to reproduce it, as we cannot fix something that we don't see. So please provide short and complete reproduce script (that doesn't require any non-existent tables, stored procedures etc.), i.e. we should be able to copy/paste it and reproduce your problem. Previous Comments: ------------------------------------------------------------------------ [2006-06-29 19:13:33] ed at supergeek dot com Note also that this same exact script continues to run without problems under PHP 4.1.2 on a Debian 3.0 (potato) box. This box has DB2 V7.1 installed. ------------------------------------------------------------------------ [2006-06-29 18:44:34] ed at supergeek dot com Description: ------------ PHP 5.1.4 compiled with --with-ibm-db2. IBM DB2 Version 8.2 FixPak 4 (equivalent to Version 8.1 FixPak 11) is installed on machine running Debian GNU/Linux 3.1 (sarge). The IBM DB2 Connect client piece is used to communicate over TCP/IP to a DB2 database running on an AS400 iSeries machine. When odbc_result() is called after simple SELECT statement, the script fails after trying to allocate 544498534 bytes (memory_limit = 500MB). Script seg faults at same location if memory_limit is increased to 600MB. When the same SELECT statement is run using the IBM 'db2' utility on the same client machine, itproduces about 350 records containing a total of less that 350KB of information. The same PHP code that produces this error previously worked under PHP 4.3.4 running on the same machine, but *stopped* working with the same type of error immediately after the iSeries DB2 host machine was upgraded to V5R4. It was this error that prompted the upgrade to PHP5 in the hopes the problem would be solved. No luck! Reproduce code: --------------- Source code unlikely to be useful do to unique nature of our database environment, but can be provided if desired. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=37963&edit=1
