Had some spooky moments with the dude myself ... you made quite a step from 6.45.2 to 6.47.1 ...
Migrating a database between software-versions is probably not the most beloved homework for a developer.
Not shure whether the amount of the data is worth the effort and if you have a db-backup ?
I would always include at least the first and last release from every inbetween-release-train in my upgrade-path. ... Just my opinion, couldn't give a reasonable cause ... I call it best practice.
But maybe you can try to change some db-items in your migrated DB, when you were able to connect after the session to the "native" 6.47.1-DB ... this may rectify things, if there are odds ... maybe.
The golden way (again: in my opinion) would be to switch back to 6.45.2 -> 6.45.9 -> somewhat 6.46.x -> last of 6.46 -> 6.47.
Every release comes with fancy new features ... also for the dude ... maybe with a new column in a table or a brand new table ... such stuff !? ... you see my point !?
You skipping releases, can have quirky results ( ... and you have such ... that may or may not be related ... to this fairy-tale)
Just test the writing thing ... it isn't helpfull & and you have a backup: try yoda's soft.migration ... or just build your dude from scratch
Let us know what have worked for you ( ... and if you liked it ... or not : )