That looks like an UTF-8 encoding error (which is what the exception is reporting).
<< 160 >> is ISO8859 encoding for a non breaking space. For UTF-8 the encoding is << 0xc2, 160 >> (or << 0xc2, 0xa0 >>). The exception isn’t showing the full binary I know, but I assume that the previous byte to the referenced binary is not << 0xc2 >>.
I wonder if your database connection is set to ISO8859 instead of UTF-8?
