I have a very regular table that is loaded from a SQL Datasource. The table has a little over 3 million records and the following definition:
Nothing out of the ordinary as you can see. The table is loaded with the ODX with an incremental selection rule on te mut_dt column. The ODX load works fine; loading the table full or incremental is no problem and the data is stored in the container as expected within 1 or 2 minutes.
However, when I drag the table to the DSA data area and load it there, something strange happens. Loading the table to the DSA hangs after 900.000 records are inserted into the raw table. We have tried waiting for several hours, but it just hangs there and nothing happens.
Other tables from the same source load fine to the DSA.
Data source version is TimeXtender SQL Source v 19.1.1.0 (but load from source to ODX works fine) ODX and TX version is 6590.1 .
Best answer by wouter.goslinga
All, thank you for all the responses. I have finally managed to solve the problem, but not in a very convenient/easy way. As it turns out, one of the varchar columns was too small. I have enlarged this column in the DSA table from a varchar(50) to a varchar(100) and after that, everything runs smooth.
This is however a bit strange because in the ODX (and the source system table) the column is a varchar(50). So in order to fix the problem I had to unsync the datatype with the ODX which should not be necessary IMHO. I didn't have the time to figure out what specific column value actually caused the problem, I will do that later. Probably some weird/special characters in a column value.
I think if you load a table from ODX to DSA with all the same datatypes (so everything in sync) this should always work, it should not be necessary to change datatypes just to make the load happen. Or at least, it should break off with an error and not hang :).
All, thank you for all the responses. I have finally managed to solve the problem, but not in a very convenient/easy way. As it turns out, one of the varchar columns was too small. I have enlarged this column in the DSA table from a varchar(50) to a varchar(100) and after that, everything runs smooth.
This is however a bit strange because in the ODX (and the source system table) the column is a varchar(50). So in order to fix the problem I had to unsync the datatype with the ODX which should not be necessary IMHO. I didn't have the time to figure out what specific column value actually caused the problem, I will do that later. Probably some weird/special characters in a column value.
I think if you load a table from ODX to DSA with all the same datatypes (so everything in sync) this should always work, it should not be necessary to change datatypes just to make the load happen. Or at least, it should break off with an error and not hang :).
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
