Could this be perhaps the wrong dialect being used here? For DB2, it appears to be a problem with the driver's inability to use `setNString` which is necessary for nationalized strings. If the driver / database doesn't support that, I can certainly add a @SkipDialect clause for DB2 to bypass this test if that makes sense here. For the Sybase use case, this seems like the driver does not support `getClob` which the SybaseDialect mentions and points to HHH-7889 Closed . Another option for this (at least temporarily) is to disable this test for that dialect. What do you think? |