|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #37963 odbc_result w/ IBM DB2 fails trying to allocate huge memory chunk (>500MB)
Submitted: 2006-06-29 18:44 UTC Modified: 2007-07-31 01:00 UTC
Avg. Score:4.5 ± 0.5
Reproduced:4 of 4 (100.0%)
Same Version:1 (25.0%)
Same OS:1 (25.0%)
From: ed at supergeek dot com Assigned:
Status: No Feedback Package: ODBC related
PHP Version: 5.1.4 OS: Debian GNU/Linux 3.1 (sarge)
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: ed at supergeek dot com
New email:
PHP Version: OS:


 [2006-06-29 18:44 UTC] ed at supergeek dot com
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.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2006-06-29 19:13 UTC] 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 19:38 UTC]
> 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.
 [2006-06-30 21:40 UTC] ed at supergeek dot com

A test script which drives the problem is included below. You must modify the script to supply credentials for accessing your own IBM DB2 database. REMINDER: This bug only started happening after our iSeries DB2 database host was upgraded to the latest release (V5R4).

The script references the table SYSIBM.SQLTYPEINFO which I believe should be a standard system table in the IBM DB2 database. If this table does not exist in your installation, you should be able to adapt the script to use virtually any table that does. The choice of table does not seem to have a bearing on whether or not the bug occurs.

The following error message is produced when the script is run:

"PHP Fatal error:  Allowed memory size of 524288000 bytes exhausted (tried to allocate 1835295024 bytes) in /home/www-devel/htdocs/admin/db2test.php on line 40"

Note that the test script below *does* work under PHP 4.1.2 on a Debian 3.0 (potato) box with DB2 V7.1 installed and which talks to the same iSeries DB2 database server.

***** Start of test script *****
// Script to drive excessive memory allocation bug when using ODBC 
// (--with-ibm-db2) to talk to DB2 database.

// Init error messages
$errmsg = "";
$odbc_errmsg = "";

// Open database connection
$db2_dsn = "<your_dsn>";
$db2_user = "<your_username>";
$db2_passwd = "<your_password>";

$db2_conn = odbc_connect($db2_dsn, $db2_user, $db2_passwd);
if (!$db2_conn) {
  $errmsg = "Connection to database failed!";

// Start building SQL SELECT query based on input parameters
$db2_query = "select * from sysibm.sqltypeinfo";

// Do query for selecting matching records.
if ($errmsg == "") {
  user_error("About to do query: [$db2_query]"); // DEBUG!!!!!
  $db2_result = odbc_exec($db2_conn, $db2_query);

  if (!$db2_result) {
    $errmsg = "<h2>Database query failed!</h2>\n";
    $odbc_errmsg = odbc_errormsg($db2_conn);
    if ($odbc_errmsg) {
      $errmsg .= "<p>$odbc_errmsg";

while (odbc_fetch_row($db2_result)) {
  $col1 = odbc_result($db2_result, 1);
  $col2 = odbc_result($db2_result, 2);
  $col3 = odbc_result($db2_result, 3);
  $col4 = odbc_result($db2_result, 4);
  $col5 = odbc_result($db2_result, 5);

  print "$col1, $col2, $col3, $col4, $col5<br>\n";
} // while (odbc_fetch_row(...))

// Close database connection
if ($db2_conn) {

***** End of test script *****
 [2007-07-23 12:11 UTC]
Please try using this CVS snapshot:
For Windows (zip):

For Windows (installer):

And try with the PDO ODBC driver instead.
 [2007-07-31 01:00 UTC] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Wed May 29 12:01:32 2024 UTC