Unfortunately, simply adding something to 'correct_mismatch' will not fix the problem because, as far as I can tell, the representation of the class did not change: 'control' is still and INTEGER. Thus, mismatch correction will not be triggered for non-compliant classes.

In my present case, my stored system uses a class which inherits from HASH_TABLE, so I may be able to accommodate the problem by changing that class to trigger mismatch correction. However, customers who have stored HASH_TABLE objects directly are going to be impacted. This might include me, as I have not worked through everything yet.