Character Set Conversions
- Last Updated: May 12, 2026
- 1 minute read
- OpenAccess SDK
- Version 8.1
- Documentation
When you export data from a database to a CSV file, the CSV file uses the same code page as the table from which the data was exported. If the CSV file and the target table use different code pages, performance for bulk load operations can suffer because the driver must perform a character set conversion.
To avoid character set conversions, your application can specify which code page to use for the CSV file when exporting data. You can specify any of the following code pages:
| US_ASCII ISO_8859_1 ISO_8859_2 ISO_8859_3 ISO_8859_4 ISO_8859_5 ISO_8859_6 ISO_8859_7 ISO_8859_8 ISO_8859_9 JIS_Encoding Shift_JIS EUC_JP KS_C_5601 ISO_2022_KR EUC_KR ISO_2022_JP GB2312 ISO_8859_13 ISO_8859_15 GBK IBM850 IBM852 IBM437 IBM862 Big5 MACINTOSH IBM037 |
IBM273 IBM277 IBM278 IBM280 IBM284 IBM285 IBM290 IBM297 IBM420 IBM424 IBM500 IBM851 IBM855 IBM857 IBM860 IBM861 IBM863 IBM864 IBM865 IBM869 IBM870 IBM871 IBM1026 KOI8_R HZ_GB_2312 IBM866 IBM775 IBM00858 |
IBM01140 IBM01141 IBM01142 IBM01143 IBM01144 IBM01145 IBM01146 IBM01147 IBM01148 IBM01149 WINDOWS-1250 WINDOWS-1251 WINDOWS-1252 WINDOWS-1253 WINDOWS-1254 WINDOWS-1255 WINDOWS-1256 WINDOWS-1257 WINDOWS-1258 WINDOWS-854 IBM-939 IBM-943_P14A-2000 IBM-4396 IBM-5026 IBM-5035 UTF-8 UTF-16LE UTF-16BE |
For example, if the source database table uses a SHIFT-JIS code page and the target table uses a EUC-JP code page, specify setCodePage("EUC_JP") to ensure that the CSV file will use the same code page as the target table. If the code page you need to use is not listed, contact Technical Support to request support for that code page.