As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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.
WF 7.6.8, Windows Any output format: HTML, Excel, PDF, XML, etc.
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.
N/A
Posts: 397 | Location: New York City | Registered: May 03, 2007
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.