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.
Is it the same flow? If not it could be many things such as a much longer record length or the number of key columns.
However the most common reasons is load type. Are you using "insert/update?" Are there duplicate keys? If so rejected record logging could be the cause. If you are using 7.7 you can view log while the flow is still running to see what's going on.
If there are no duplicate keys, then using "Insert from memory" or "Bulk load via disk file" are considerably faster, which one depends on the database and other factors.
N/A
Posts: 397 | Location: New York City | Registered: May 03, 2007