Their documentation indicates that they support unicode character sets and nationalized strings - https://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5.0/com.ibm.db2.luw.sql.ref.doc/doc/r0057004.html It also says that it essentially maps NCHAR -> CHAR, NVARCHAR -> VARCHAR, ... - though it was unclear whether that only happens for databases created for unicode. Curious what the reason for the failure is then |