Hi there,
I assume I have a pretty naughty case .
I have a dimension table with a secondary unique index (COUNTRY_ISO_A2 ,CITY_TXT ,ZIP_CODE) from columns with datatype
VARCHAR() CHARACTER SET UNICODE NOT CASESPECIFIC
and for a while this table was fed with not properly converted utf-8 string since the feeding apps driver did not support utf-8, now the feeding apps driver is utf-8 compatible and I get (on first run) the error above when loading my dimension table.
I have like a first guess that the the index representation might not be the same as the "restituted" representation of the column´s value and that in CITY_TXT the earlier value ???????? (on Target) and the new ΠΕΙΡΑΙΑΣ (InFLow) when comparing on COUNTRY_ISO_A2 , ZIP_CODE would have the same index representation
How can I check that?
Any other suggestion welcome since I do not see after "functional" control not other reason
thanks
Rgds
JL D
Tags:
Forums: