When working with SAP IQ in Stambia DI, there are a few specificities to understand and to take into account.
Here is some useful information on these special considerations.
Implicit conversion
The sybase jdbc driver has one very particular behaviour that might cause some issues when executing even simple mappings.
By default it uses an implicit conversion between VARCHAR and INTEGER datatypes.
This means that for example if in your source database you have a VARCHAR column, and you try to load it into a VARCHAR sybase column, you might encounter the following exception:
Java.sql.BatchUpdateException: JZ0BE: BatchUpdateException : une erreur est survenue lors de l'exécution de l'instruction par batch : JZ0BE: BatchUpdateException : une erreur est survenue lors de l'exécution de l'instruction par batch : SQL Anywhere Error -1000187: Unable to implicitly convert column 'L1_TEST' to datatype (varchar) from datatype (integer). -- (db_loadengine_cvt.cxx 5744) at com.sybase.jdbc4.jdbc.ErrorMessage.raiseBatchUpdateException(Unknown Source) at com.sybase.jdbc4.jdbc.SybStatement.handleBatchException(Unknown Source) at com.sybase.jdbc4.jdbc.SybPreparedStatement.executeBatch(Unknown Source) at com.indy.engine.actionCodes.JdbcActionCodeI.executeBatch(JdbcActionCodeI.java:469) at com.indy.engine.actionCodes.JdbcActionCodeI.finalizeDirectBindedFetch(JdbcActionCodeI.java:491) at com.indy.engine.manager.ActionCodeExecutor.finallyBinded(ActionCodeExecutor.java:605) at com.indy.engine.manager.ActionCodeExecutor.executeDirectBindedCode(ActionCodeExecutor.java:490) at com.indy.engine.manager.ActionCodeExecutor.executeBindedCode(ActionCodeExecutor.java:619) at com.indy.engine.manager.ActionCodeExecutor.executeCode(ActionCodeExecutor.java:94) at com.indy.engine.manager.ActionCodeExecutor.run(ActionCodeExecutor.java:228) at java.base/java.lang.Thread.run(Thread.java:834)
You can disable the implicit conversion on your SAP IQ metadata with the following option:
