asked 19 Nov '12, 02:46
If you happen to be using Powerbuilder for your client software:
We saw a similar problem when moving from SQL Anywhere 9 to 12, which turned out to be a bug in Powerbuilder (http://search.sybase.com/kbx/changerequests?bug_id=639236). This was fixed in Powerbuilder EBF 220.127.116.1143.
answered 22 Nov '12, 09:01
The SQL Anywhere ODBC client never automatically reconnects a dropped connection, nor has it ever done so. As far as I am aware, none of the SQL Anywhere client interfaces reconnect automatically on a dropped connection.
I know that Interactive SQL can reconnect after a dropped connection, but that is not done at the client API level.
I believe the reconnect that you are seeing must be being done by something higher up that the ODBC driver. That could be the driver manager (although I am not aware of driver managers that reconnect), your application, or your application development tool.
If you can reproduce this you can enable ODBC tracing in the driver manager. In the trace I am pretty sure you will see additional ODBC calls that are reconnecting - demonstrating that the ODBC driver itself is not doing the reconnecting.