DSXchange

Currently, we changed all target table names to just make sure they're a little bit different from old names. But it's not the final solution, some time the same issue still occur. For instance, in one job, if the source sequential file is empty, then the job will hang on over there and the same err...

After we replaced the DB2 UDB API stage by hashed file stage or sequential file stage, the job has no any problem. Is there anyway to trace into more detail so that I can identify what may be the root cause?

Hello ArndW, thanks for your response. I'm suspecting it's an environment issue. Maybe the installation or some component has some problem. The strange thing is that the issue will go away after I changed the target table name, for whatever change. Or after I changed the schema name, then the issue ...

Is there anyone know the root cause about the below issue? This issue happened for Information Server v8.1 on Red Hat Linux 4. Sequential file -----------------------> DB2_UDB_API The job is very simple. But when DB2 API Stage was used and the target table name was like SDS7.SDS_I_143_RAW_MATERIAL, ...