This seems to be new behaviour since we have applied the EBF 4239 to 10.0.1 because we have not seen it before. We are seeing various connections that do not respond to either a DROP CONNECTION xxxxxx or a disconnect from Sybase Central.
If we try to shut the database down from Sybase Central it just hangs and the service never disappears from task manager but won't accept any more connections. Eventually we have to resort to ending the dbsrv10 task.
For the startup parameters we use: -x tcpip(dobroadcast=no;serverport=2638) -ti 600 -tl 0 -c 25P -ch 25P -zl From sa_conn_info for the problem connection: LastReqTime "2011-09-14 08:56:50.015" (a few weeks ago now!) and ReqType "Open" From sa_locks on that connection: lock_class "Schema", lock_duration "Transaction", lock_type "Shared" on vrious tables.
All I can think of is going back to our previous EBF because with 42 databases it's a problem when we want to alter a table that is blocked by the connection we cannot drop.
Any help appreciated. Regards, Adrian.
There is a known issue (CR #702733 - 188.8.131.5286, 184.108.40.20613) which allows connections to be 'undroppable' in rare circumstances (usually involving a parallelized query that makes use of a HashFilter). Unfortunately, this fix has not been backported to the 10.0.1 codeline due to 10.0.1's "Archived" or "End-of-Life" status. Setting the connection option 'MAX_QUERY_TASKS' to '1' or restarting the database server is a workaround for the issue in 10.0.1.
For more information about this issue, see my response to this question here: http://sqlanywhere-forum.sap.com/questions/6164/connections-that-cannot-be-dropped/6197