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.
I'm working a job for data quality analysis where I need to copy 10% of the records from a DB2 data source to and "identical" structure in SQL*Server. This is thousands of fields across hundreds of tables.
So I've created very simple transforms that move DB2's Field_1 into SQL*Server's Field_1, DB2's Field_2 into SQL*Server's Field_2, etc.
Here's the thing. About one out of every 100 fields don't copy, because Data Migrator sees the name Field_1 and interprets it to mean SQL*Server's Field_1 instead of DB2's Field_1. It self-references the target field instead of taking the field of the same name from the source, and the result is that the field doesn't fill.
I fix this by aliasing the field coming from the source so that the names are no longer the same, but when you're doing hundreds of tables and thousands of fields this makes the process of creating the load far more tedious and time-consuming, and not doing it means you have to test and review every table and field.
Is there a button I can check somewhere that says "hide the target fields" when doing the data assignment?This message has been edited. Last edited by: Tamra,
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
I'm dealing with it in 81M at the moment, but this has occurred from 7.7 forward if my recollection is correct. I address it when it occurs by adding an alias to the inbound data fields, generally appending "incoming_" to the field name.
Sorry, but I can't provide source code where you can duplicate the problem because I can't provide you the data. It's not a consistent problem by any means.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007