Hi,
Could you please paste the error log.
Please check 1> the column size in netezza and in Oracle.
2> Check the data type of the column is same or not.
3>You asked the string size is increasing ; so check the i$ table column size- How its created.
4> If you are doing by interface then try ding the same using ODI procedure once.
Thanks,
ODI-1217: Session TEST (34803) fails with return code 12899.
ODI-1226: Step TEST fails after 1 attempt(s).
ODI-1240: Flow TEST fails while performing a Loading operation. This flow loads target table ABC
ODI-1228: Task SrcSet0 (Loading) fails on the target ORACLE connection Oracle.
Caused By: java.sql.BatchUpdateException: ORA-12899: value too large for column "ODI"."C$_0ABC"."C8_TERM" (actual: 119, maximum: 100)
at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:13349)
at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:248)
at oracle.odi.runtime.agent.execution.sql.BatchSQLCommand.execute(BatchSQLCommand.java:44)
at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:102)
at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:1)
at oracle.odi.runtime.agent.execution.DataMovementTaskExecutionHandler.handleTask(DataMovementTaskExecutionHandler.java:87)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:558)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:464)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300)
at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292)
at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
at java.lang.Thread.run(Thread.java:722)
Hi,
Please check the column(TERM column) length(logical lenth) in source and target tables. Modify the length to 125. Try re-executing the interface.
Thanks
Hi,
Increasing the column size will solve the problem for this particular scenario. But, what if the data load exceeds this size too.. So, I am looking for a generic solution(constraint, filter, case statement,etc).. thanks for your reply...
