This content has been marked as final. Show 2 replies
You need to debug the issue to see what statement is actually failing and for what data. I do not see any reason why migration from UTF8 to AL32UTF8 would cause such error provided the data is the same. So this it either an issue caused by a new data pattern and not really related to the migration or some very rare circumstance.