Hi,

We are developing dimension ETL using DataMigrator, and we are using the AUTOINCREMENT option for Surrogate Keys. We have set the SK column as detailed in the following image:



But when we run the data flow, the Oracle sequence is not called and no value is generated for the field, therefore the process abort due the column doesn't allow nulls.

The Iway Datamigrator version is 8.1.

How do we must set the column correctly?

Thanks in advance.

This message has been edited. Last edited by: Tamra,

lalvarez13,

While we wait for others to reply here is a link to the Data migrator Users Manual.

DataMigrator User's Guide.

This manual is for version 8105. If another version is required then go to the Tech support site
- Technical Content Library to find the Data Migrator manuals for your version.


Technical Support Center


Thank you for participating in the Focal Point Forum.

Kindest regards,
Tamra Colangelo
Focal Point Moderator - Information Builders Inc.
* Summit 2016 – June 13-17 in Reno, Nevada  - http://www.informationbuilders.com/events/summit

quote:

dimension ETL using DataMigrator, and we are using the AUTOINCREMENT option for Surrogate Keys. We have set the SK column as detailed in the following image:

Hello,
For a better analysis of this problem we would like to ask you to open a hottrack case. Please describe the results, and add your flow and synonym files to the hottrack case; additionally please provide the DDL statement for the target synonym.

Thank you.

After you make changes to the synonym you need to recreate the table to reflect the changes in ORACLE. Right click on the synonym and select Data Management, Recreate DBMS Table. Your user id must have been granted privileges for create table, sequence and trigger. Once you have done this then it's ORACLE that assigns the value to your surrogate key.

Thanks for your responses. Finally, I was able to find the relationship between AUTOINCREMENT option and Database, because when the table is created from DMC using "Recreate to DBMS" option, it creates a TRIGGER and a Oracle Sequence linked to the SK column that is filled with the Nextval when a new row is added to the table. Problem solved.