Focal Point Banner

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 for further assistance. Reference the community FAQ to learn more about the community.

Read-Only Read-Only Topic
[CLOSED] DataFlow Error
Platinum Member

I getting the below errow when i run the data flow.I did research and it got to know that i can be due to field length issues.I gave enough length in the target but still same issue.
SQLCODE IS 8152 (HEX: 00001FD8) XOPEN: 22001
:   (8152) [22001] String or binary data would be truncated.

Since the error is not pointing to any particular column ,i am not sure where to check.
Has anyone encountered same issue?

This message has been edited. Last edited by: FP Mod Chuck,

WF8206,Windows 7,8,10
Posts: 229 | Location: MI | Registered: September 13, 2017Report This Post
posted Hide Post
That's an error from MS SQL Server and it does generally indicate the length of the target column is insufficient; it could also be a data type mismatch or a problem with [NOT] NULL specification. Please check your target transformations to ensure all the source/target formats are compatible.

You could also try to running with traces which may contain more details but if the MS SQL Server error message doesn't have the column name then the trace won't have it.

If you still have difficulties please open a case with IRL and upload the source and target synonyms and the flow so that they can reproduce the problem.

Posts: 397 | Location: New York City | Registered: May 03, 2007Report This Post
Platinum Member
posted Hide Post
Okay.I will try all these possibilities and will update this post.

WF8206,Windows 7,8,10
Posts: 229 | Location: MI | Registered: September 13, 2017Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Copyright © 1996-2020 Information Builders