Sounds like the tuner is updating a field definition from a CHAR to an INT - much preferable from a design and performance perspective, but requires a lookup table {parent table} as well as converting existing data.
I wonder if they have mapped U [Unknown?] to an INT in the conversion code ....