Connection on DB that can't be dropped

[Former Member]

We have an old connection (last request: last Friday) floating around on our primary database (in a high availability cluster) that we can't drop. Neither right clicking in Sybase Central and saying "disconnect", nor calling "drop connection" actually drop the connection. We also have a "The number of requests waiting to be fulfilled: 1" message in Health and Statistics. We strongly suspect that that message is caused by that connection.

SQL Anywhere 11.0.1.2436. Connection ID 9273. Connection Name SQL_DBC_2eb4bf0. Last request type is a fetch.

How do we get rid of this connection without restarting the database?

[Breck_Carter]

Some more information please: What is the version and build? connection number? connection name?

[Former Member]

SQL Anywhere 11.0.1.2436 Connection ID 9273 Connection Name SQL_DBC_2eb4bf0 Last request type is a fetch

When I connect to the secondary database I don't see any indication that anything is wrong.

[VolkerBarth]

Are there any locks related to this connection (cf. sa_locks(), or the "BlockedOn" column of sa_conn_info())? (Just guessing...)

[jeff_albion]

There is a known issue (CR #702733 - 11.0.1.2786, 12.0.1.3713) which allows connections to be 'undroppable' in rare circumstances (usually involving a parallelized query that makes use of a HashFilter). Setting the connection option 'MAX_QUERY_TASKS' to '1' or restarting the database server is a workaround for the issue.

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

[MCMartin]

To identify which programm used the connection you can use sybase central go to the connected user tab and look at the properties of the connection. In the tab Extended Information you will see first the AppInfo which tells you from which machine and which programm the connection was initiated. Maybe with this information you get a better understanding if it is still a valid connection or what might have happened to it.

[VolkerBarth]

Just for completeness: I guess the same info can be found with ISQL and the query "select connection_property('AppInfo', 9273)".