This content has been marked as final. Show 1 reply
It seems that the problem was somehow because the server was installed in a 32-bit VM, and migrated onto a newer host capable of running the 64-bit VMs, so Solaris switched to that. While there were no actual problems with database files, source architecture seems to have got recorded there and confused some verifier routines?
I tested that a newly-made DS instance works as expected. Its start/stop scripts referenced "amd64" in the paths, but changing original dsins scripts accordingly did not help.
Ultimately, data and configs were exported from original instance, which was then destroyed. New instance remade in its place and data reimported again and replications reconfigured and customizations (plugins, acls) reapplied, and all works like it should now. Rinse and repeat for siblings in the MMR cluster.