Bug #79277 [Opn]: pdo_odbc accessing SAP 16.0 ASE Fatal error: Allowed memory size ...

Edit report at https://bugs.php.net/bug.php?id=79277&edit=1 ID: 79277 User updated by: khleung at isfactory dot com Reported by: khleung at isfactory dot com Summary: pdo_odbc accessing SAP 16.0 ASE Fatal error: Allowed memory size ... Status: Open Type: Bug Package: PDO ODBC Operating System: CentOS 7 PHP Version: 7.4.2 Block user comment: N Private report: N New Comment: Yes, the symbolic was built by SAP ASE SDK installation. [sybase@rhase02 lib]$ ls -l total 21352 -rwxr-xr-x. 1 sybase sybase 5185504 Nov 7 2018 libsapcrypto.so -rwxr-xr-x. 1 sybase sybase 5413262 Nov 7 2018 libsapssfs.so -rwxr-xr-x. 1 sybase sybase 499679 Nov 7 2018 libslcryptokernel.so -rwxr-xr-x. 1 sybase sybase 166 Nov 7 2018 libslcryptokernel.so.sha256 -rwxr-xr-x. 1 sybase sybase 3644274 Nov 7 2018 libsybdrvodb-sqllen4.so -rwxr-xr-x. 1 sybase sybase 3453367 Nov 7 2018 libsybdrvodb-sqllen4.so.fbo -rwxr-xr-x. 1 sybase sybase 3654515 Nov 7 2018 libsybdrvodb-sqllen8.so lrwxrwxrwx. 1 sybase sybase 25 Feb 25 2019 libsybdrvodb.000 -> ./libsybdrvodb-sqllen4.so lrwxrwxrwx. 1 sybase sybase 25 Apr 18 2019 libsybdrvodb.so -> ./libsybdrvodb-sqllen4.so drwxrwxr-x. 5 sybase sybase 55 Feb 25 2019 locales [sybase@rhase02 lib]$ Previous Comments: ------------------------------------------------------------------------ [2021-09-01 18:20:36] dbccjob at gmail dot com Is your SAP odbc library symlinked to the SQLLEN8 library version ? The issue you are facing makes think of it. make sure the library points to the sqllen8 one, unless you run on an old linux. libsybdrvodb.so -> libsybdrvodb-sqllen8.so see http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc20155.1600/doc/html/san1361915533650.html ------------------------------------------------------------------------ [2020-09-29 14:12:56] cmb@php.net > It appears that the issue can be reproduced 100% of the time if > a nullable varchar column getting selected actually contains a > null value. I cannot reproduce this with either the ODBC Driver for SQL Server or the MySQL ODBC 8.0 Unicode driver on Windows, so this is apparently driver (manager) specific. Anyhow, after having another look at this issue, I still have no idea where this excessive memory allocation would occur. I think that addressing the unitialized displaysize issue, and also the -Wpointer-sign warnings is appropriate, but unless that resolves this issue, targeting the "master" branch seems to be more reasonable. ------------------------------------------------------------------------ [2020-08-10 17:40:02] khleung at isfactory dot com net_surfer is right! Please advise any quick fix for that. ------------------------------------------------------------------------ [2020-07-01 19:52:29] net_surfer at mail dot com It appears that the issue can be reproduced 100% of the time if a nullable varchar column getting selected actually contains a null value. ------------------------------------------------------------------------ [2020-03-22 12:31:23] cmb@php.net Indeed, apparently there are no negative display sizes. I'm at a loss; that probably needs to be debugged with a Sybase DB. ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=79277 -- Edit this bug report at https://bugs.php.net/bug.php?id=79277&edit=1