Hi Tony,
I agree with Mirco opinion.
The latest build fixes the following problem.
==========(Build #1691 - Engineering Case #748170)===========
In rare timing dependent cases, a copy node that had just processed a Log
rRename could have failed assertion 200505, if its child was requesting log
pages. This has been fixed.
2255721 - SQLAnywhere 16.0 SP46 Build 2213 Release Notes Information
Thanks,
Atsushi