I’m using Data Integrator XI R2 (11.5.2). I’m reading data from a file. I need to send this data to tables that have primary and foreign key dependencies.
Looking around by myself and by the forum I came to the conclusion that I must use “include in transaction” and “transaction order”.
First when i tried with transaction order 1,2,3,4,5 I had an error saying that there was a duplicate transaction order. So I went using 51,52,53,54,55. I had then a strange error saying something like like (sorry but it was in French) “function sequence order error” from theSQL SERVER ODBC driver.
Now I get it. It is not an error inside DI, the error is raised by the database!
What does the message “function sequence error” in SQL server mean??? Anybody?
The guy at the support told me that my job design was the worst he has ever seen and that I must redesign it. What’s surprising is that my case of use of the transactionnal loading of tables it described in the manual. But the guy clearly has nothing to do whith my problem due to his product. He even didn’t acknowledged as a bug. Yes because it IS a bug, upgrading to version 11.7.2.2 didn’t change anything to my problem.
Two things.
First, support told that you should not load all your dimension tables in one dataflow, rather use one dataflow per dimension table. Loading with transactions enabled has downsides of its own, performance, usability, memory consumption. So it should be avoided.
Second, either way, you got an error from the database we do not understand and is (was?) probably a bug. Until it is confirmed it is not a DI problem and does not effect the “include in transaction” functionality it should get fixed.
(BOB member since 2004-12-17)
(BOB member since 2007-07-19)
(BOB member since 2004-11-30)