Hi I have this warning:

Warning: PDOStatement::fetchAll() [pdostatement.fetchall]: column 2 data was too large for buffer and was truncated to fit it en DatabaseStatement_oracle->execute() (línea 708 de C:\wamp\www\web\includes\database\oracle\database.inc).

My sql, at column 2 only returns 30 chars in the max case. I don't know what it's the problem.

Any help?

Comments

aaaristo’s picture

aaaristo commented
Status: Active » Postponed (maintainer needs more info)

which query you where running???

agoradesign’s picture

agoradesign commented

I've ran into the same problems in my recent project. I've found this bug report on php.net: https://bugs.php.net/bug.php?id=35003

The workaround as mentioned by [2013-03-12 19:05 UTC] wilbert dot j at gmail dot com helped me to get rid of the warnings.

UPDATE:

found another issue on php.net: https://bugs.php.net/bug.php?id=54379&edit=1 (which also leads to: https://github.com/php/php-src/pull/59 )

quick summary: different character encodings of connection and data are incorrectly handled. I can confirm that because all of my truncated values contained german umlauts.

Anonymous’s picture

Anonymous (not verified) commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)

It's a PHP bug with OCI

agoradesign’s picture

agoradesign commented

Well, it is - but I think, it would be worth a thought, if the "charset" parameter in the connection string should be made configurable. In my case, it helped changing it to WE8MSWIN1252 instead.

But this change also triggered the next problem: I had to take care of run a utf8_encode() for every string that may contain special characters. We only use the Oracle connection for reading data and store it in a Drupal site running on a MySql database. I don't know, if changing the charset of the connection would cause problems when running the whole Drupal site on Oracle

agoradesign’s picture

agoradesign commented
Status: Closed (won't fix) » Active
bohart’s picture

bohart
Location Lutsk, Ukraine
commented
Version: 7.x-1.12 » 7.x-1.x-dev
Status: Active » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Everyone can apply the patches/suggestions above (not tested by the maintainers, tested by the community) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.