Fixes: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in position 105: invalid start byte #1015#1018
Merged
bimalkjha merged 1 commit intoibmdb:masterfrom Jul 2, 2025
Conversation
…#1015 Signed-off-by: Balram Choudhary <bchoudhary@rocketsoftware.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses issue #1015.
The UnicodeDecodeError occurred due to special (non-ASCII) characters in the error message returned by the CLI driver, such as:
"[IBM][CLI Driver][DB2/AIX64] SQL0420N In einem Zeichenfolgeargument der Funktion "INTEGER" wurde ein ungültiges Zeichen gefunden. SQLSTATE=22018"
The code now correctly handles error messages containing special characters. It works with both localized and English messages, including:
"[IBM][CLI Driver][DB2/AIX64] SQL0420N Invalid character found in a character string argument of the function "INTEGER". SQLSTATE=22018"