(ICM18743) Starting Load
10/27/2011 16:41:43 0 WARNING.. ON MATCH INCLUDE INPUTS DUPLICATE SEGMENTS
10/27/2011 16:41:43 (FOC1400) SQLCODE IS 208 (HEX: 000000D0)
10/27/2011 16:41:43 : MTDP: EM_NOTIDLE(208): Not ready to accept new request.
10/27/2011 16:41:43 (FOC1408) SQL CLOSE CURSOR ERROR. : GABE_CLMPDFD
10/27/2011 16:41:43 (FOC1400) SQLCODE IS 208 (HEX: 000000D0)
10/27/2011 16:41:43 : MTDP: EM_NOTIDLE(208): Not ready to accept new request.
10/27/2011 16:41:43 (FOC1408) SQL CLOSE CURSOR ERROR. : GABE_CLMPDFD
10/27/2011 16:41:43 (FOC1400) SQLCODE IS 208 (HEX: 000000D0)
10/27/2011 16:41:43 : MTDP: EM_NOTIDLE(208): Not ready to accept new request.
10/27/2011 16:41:43 (FOC1408) SQL CLOSE CURSOR ERROR. : GABE_CLMPDFD
10/27/2011 16:41:43 (FOC1400) SQLCODE IS 208 (HEX: 000000D0)

Looks like you have ON MATCH INCLUDE in your MODIFY that is trying to add a duplicate record to the unique key of your relational db. You need to consult the SQL error code for the relational db to diagnose further. To remove the duplicate addition warning, change your code to ON NOMATCH INCLUDE and ON MATCH REJECT.

thanks

The message
(ICM18743) Starting Load
indicates that DataMigrator is being used, so you can change the MATCH logic that is generated from target properties by selecting for "If the record exists" from the pull-down "Reject the record."

If that's not the issue, the meessage
IMTDP: EM_NOTIDLE(208): Not ready to accept new request.
looks like it comes from Teradata.

Using ON MATCH INCLUDE:

I guess it depends on whether you want duplicate entries or not. In our case we do: sometimes we sell the same product twice on a given order with the pricing determined by whether we have the goods in stock or not. We match on ITEM_CODE:

ON MATCH INCUDE
ON NOMATCH INCLUDE

So there is a place for ON MATCH INCLUDE in certain circumstances and it isn't necessarily an error message.