ID: 19213 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: ODBC related Operating System: SuSE Linux 8.0 PHP Version: 4.3.0-dev New Comment:
today i've tested the whole day. after logging the sql statements i found out, that sometimes 2 requests are coming up, the first without the needed parameters and the second with. And that is related by a bug in our select script. Now I'm really shamed. :-( Next time you are near by Ludwigshafen, Germany send me a mail you will get some free drinks by me. A lot of thanks for your great work. with best regards Albert Steckenborn Previous Comments: ------------------------------------------------------------------------ [2002-10-27 10:18:19] [EMAIL PROTECTED] updated version and summary. ------------------------------------------------------------------------ [2002-10-27 04:08:25] [EMAIL PROTECTED] Nothing has changed with the latest snapshot php4-200210270000 with a second ODBC-connect to the SAPDB database within 10 sec. the PHP-error occours like before --------snip----- [27-Oct-2002 11:06:55] PHP Warning: SQL error: [SAP AG][LIBSQLOD SO][SAP DB]Syntax error or access violation;-3014 POS(272) Invalid end of SQL statement., SQL state 37000 in SQLPrepare in /www/kunden/reisenetz/web/show.phtml on line 151 [27-Oct-2002 11:06:55] PHP Warning: odbc_execute(): supplied argument is not a valid ODBC result resource in /www/kunden/reisenetz/web/show.phtml on line 152 [27-Oct-2002 11:07:05] PHP Warning: SQL error: [SAP AG][LIBSQLOD SO][SAP DB]Syntax error or access violation;-3014 POS(272) Invalid end of SQL statement., SQL state 37000 in SQLPrepare in /www/kunden/reisenetz/web/show.phtml on line 151 [27-Oct-2002 11:07:05] PHP Warning: odbc_execute(): supplied argument is not a valid ODBC result resource in /www/kunden/reisenetz/web/show.phtml on line 152 --------snip------------- but the ODBC_Result is ok. The Memory-Usage looks very better with SAPDB, PHP4.2.3 and Apache1.3.27 It seems as if my Memory-Leak is fixed. Thanks a lot to all that are working at these problems with best regards Albert Steckenborn ------------------------------------------------------------------------ [2002-10-26 16:25:29] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-10-26 10:07:09] [EMAIL PROTECTED] Hi again, now we have converted to SAPDB 7.3.00.25 (working better) PHP 4.2.3 Apache 1.3.27 But one Error holds on. If i'm requesting the database the first time no Error occurs but when i'm closing the result window and start a new request within around 10seconds the following PHP Warning shows up in the Error log -----snip--------- [26-Oct-2002 11:28:03] PHP Warning: SQL error: [SAP AG][LIBSQLOD SO][SAP DB]Syntax error or access violation; -3014 POS(260) Invalid end of SQL statement., SQL state 37000 in SQLExecDirect in /www/kunden/reisenetz/web/show.phtml on line 153 -------snip------------- The results of the second request are ok. When i'm using ODBC_prepare following Warning comes up: odbc_execute() supplied argument is not a valid ODBC result resource The results are ok too. It looks as if the ODBC_Close($conn) dont't work It is the same Error as in ADABAS D 11 Hope that this will help. With best regards Albert Steckenborn ------------------------------------------------------------------------ [2002-10-07 03:48:24] [EMAIL PROTECTED] hi, i'm changing now from ADABAS D to SAPDB. Meanwhile i'm thinking that this bug is a bug in the ADABAS ODBC Driver and not PHP related. I need one week more for the migration and then wee will see if it's ADABAS D or PHP related. The reason to migrate to SAPDB is that we can use the most of our sripts anymore and the support (for a free software)is much better. Some of the scripts that are running on ADABAS D with errors so that we have to create db-Procedures, are running on SAPDB without any errors. That's the reason that i'm shure we can close our bug with the migration. A lot of thanks to Kalowsky and everybody else for the help. I will post the result of the migration around the 20021020. With best regards Albert Steckenborn ------------------------------------------------------------------------ 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/19213 -- Edit this bug report at http://bugs.php.net/?id=19213&edit=1
