-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any CCSID other than 1208 fails to connect to database #20
Comments
Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt). Hello Kerim,
|
Original comment by Kerim Gueney (Bitbucket: KerimG, GitHub: KerimG). Hello @dmabupt, the character set mismatch issue has been resolved ( #18 ). It wasn't actually a characterset mismatch, despite the error message making it seem so, Nonetheless, shouldn't
work? Your suggestion with
on the other hand does work. Perhaps I'm confused about what the DB2CCSID environment variable is for. I assumed that it has to match whatever CCSID the database fields are defined in. |
Original comment by Xu Meng (Bitbucket: mengxumx, GitHub: dmabupt). Hello @KerimG , the DB2CCSID env var actually calls SQLOverrideCCSID400(). Ref --> https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_61/apis/pase_sqloverrideccsid400.htm Long long ago this DB2 addon ran with its job CCSID (which corresponding to CCSID = 0). But it had some problems so I overrides the default CCSID to 1208 (UTF-8) and adds this DB2CCSID env var for customization. |
Original report by Kerim Gueney (Bitbucket: KerimG, GitHub: KerimG).
I can connect just fine to the database with CCSID 1208 but can't insert data due to character set mismatch.
I set the CCSID via
but then the idb-connector won't even connect to my database printing out an unreadable error:
The text was updated successfully, but these errors were encountered: