ODBC table definition issue

dnat · Post by **dnat** » Wed Nov 14, 2007 7:38 am

We imported a table definition of a table through ODBC. When we changed the column width for one table and tried to import it again with the same name(i.e replaced the table definition), the length of the column did not change.It shows the same definition as it had earlier. We tried many times, but there is no change.Any thoughts about what the reason could be and how to rectify it.

chulett · Post by **chulett** » Wed Nov 14, 2007 7:48 am

You could simply update the definition manually. Or delete the old one and reimport but that would hork your metadata linkage, I would think.

dnat · Post by **dnat** » Thu Nov 15, 2007 2:15 am

I tried to re-import the definition, but it still shows up the same old column length. If i manually change it , still i am not able to insert the data in that particular column as it still refers to the old one.

dnat · Post by **dnat** » Thu Nov 15, 2007 2:16 am

I tried to re-import the definition, but it still shows up the same old column length. If i manually change it , still i am not able to insert the data in that particular column as it still refers to the old one.

chulett · Post by **chulett** » Thu Nov 15, 2007 7:41 am

Then it doesn't sound like you've actually changed the table you are importing.

You would obviously have to manually change the metadata not only in the Manager / repository but in the job(s) where you've used it as well.

dnat · Post by **dnat** » Thu Dec 06, 2007 10:11 pm

This turned out to be an issue with the table that was created. We found out that We had not changed the field value in the table, and no issues with datastage.