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.
Many of us asking how to incorporate Data Migrator with Oracle Sequence Generator when loading Fact Tables.
This will be fully supported in DM 7.7, but meanwhile, here is one way that will help you.
Make the Surrogate_Key field of the Fact table in the Metadata "Read Only". You will ignore this field in the target transformation.
Create an Oracle Seq Generator for this field;
CREATE SEQUENCE seq_name INCREMENT BY 5 START WITH 10 ;
Create an INSERT trigger on the Fact table;
CREATE OR REPLACE TRIGGER trigger_name BEFORE INSERT ON fact_table_name FOR EACH ROW BEGIN SELECT seq_name.NETXVAL INTO :NEW."surrogate_key_col_name" FROM DUAL; END;
------ This is very similar to Microsoft Sql Server IDENTETY field type, when the database engine automatically updates the field of new records with a new sequence number.This message has been edited. Last edited by: Kerry,