DSD.BCIOpenW results of SQLColAttributes(finAttDedAmt) gave MetaData mismatch
COLUMN.TYPE Expected = BigInt Actual = Numeric
where finAttDedAmt is the column name in the source and the destination tables. In the database we see that the datatype of the column is defined as BigInt and same is used in the job as well but still this warning is generated and it is happening for all the columns which have BigInt datatype.
I'm not sure if the ODBC interface supports BigInt as a datatype. Are values in the BigInt range (i.e. greater than what an Int can handle, for example 2147483649 ) correctly loaded?
ArndW wrote:I'm not sure if the ODBC interface supports BigInt as a datatype. Are values in the BigInt range (i.e. greater than what an Int can handle, for example 2147483649 ) correctly loaded? ...
Are you referring to the values that the field can hold. I looked into the database and there are some values as 5000000000, 16000000000 . If that is the case then what should be the solution, because we have also tried Integer datatype and it again gives warning
Bigint support 8 byte so the vlues you have specified can be fit into that, problem is why it is giving the warning, please wether the MS SQL server supports the bigint datatype if not convert it the required datatype supported by MS SQL database and then use datatype conversion functions if required (see the datatype conversion map from help).
Regards
Suresh Angadi
pravin1581 wrote:Hi All,
We are trying to load data from Db2 into SQL server 2005. But we are getting the following warning
DSD.BCIOpenW results of SQLColAttributes(finAttDedAmt) gave MetaData mismatch
COLUMN.TYPE Expected = BigInt Actual = Numeric
where finAttDedAmt is the column name in the source and the destination tables. In the database we see that the datatype of the column is defined as BigInt and same is used in the job as well but still this warning is generated and it is happening for all the columns which have BigInt datatype.