964818 wrote:That's probably a safe assumption. Potentially, if you can figure out exactly where it got changed, and assuming that the changes weren't lossy, it should be possible to work out how to write a data slam that would fix the issue. But that is almost certainly way more work than simply re-exporting and/ or re-importing depending on where the character set conversion took place.
Our DBA is out of the office today, but I will get copies of both imp/exp logs when he returns (I'm unsure of their location).
You are correct though, the data is stored in varchar2. I knew as soon as I checked that it would be.
Can I assume that the data is unrecoverable without restoring or reimporting?