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.
Before run the flow set the target properties - Set Prior to Load Option as Truncate Table and Set Load Type as Insert record from memory. While set the target properties like this Before inserting, it will truncate the data's in the target table then it will insert the data.
I agree, for a database that supports TRUNCATE it's a better choice than DELETE rows because there's no database logging. So there's no chance of the database log filling up and cuasing the delete rows to fail. It's also faster.
N/A
Posts: 397 | Location: New York City | Registered: May 03, 2007
Actually there are several processes with the same issue. Since they were implemented by different developers, some of them use truncate and some of them use delete all rows. But they all have the same issue.
The weird thing is that on SQL server side there is no errors and looks like working properly. On the iway side, it's the same.
If we leave database alone assuming it works properly, do you think the SQL server adapter has a problem?
It seems the error handling of the data migrator process is so bad. I don't know underlying how it handles commit or rollbank in case there is an error on database side.
iWay adapter manager SAP Adapter Web Services SAP BASIS, Java Core
I think the error handling is quite good. You can see all kind off messages and you can even decide what kind of messages you want to see. All logging is turned off by default though, you just have to put it on.
If you choose truncate in the target options, and it doesn't work, then I would definitely open a case at IBI, this is a simple process and should work OK.
Meanwhile you can use this in a stored procedure to be sure the truncate is done before your process:
SQL SQLMSS TRUNCATE TABLE [some target table] END SQL SQLMSS COMMIT WORK -RUN