Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
Figure out if we can kill process via db2 sql. Attempt to use : FORCE APPLICATION(<session id>) to kill sessions in db2 luw via GUI.
Note that this command works in an async fashion.
I've added script drop to the tree menu. Also added kill process to the session manager. Both will use the "CALL SYSPROC.ADMIN_CMD( 'FORCE APPLICATION(<???>)')" syntax. Wether the session is killed or not is determined by the database and could take place over a long period of time. The sysproc.admin_cmd procedure was introduced in version 9.x and above so support is only for db2 9.x and above.
I've added script drop to the tree menu. Also added kill process to the session manager. Both will use the "CALL SYSPROC.ADMIN_CMD( 'FORCE APPLICATION(<???>)')" syntax. Wether the session is killed or not is determined by the database and could take place over a long period of time. The sysproc.admin_cmd procedure was introduced in version 9.x and above so support is only for db2 9.x and above.
Issue #8423 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
1 issue link |
relates to #14957
Issue #14957Drop Connection Info->Exception in view log and incorrect script in SQL Log. |
http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.sql.rtn.doc%2Fdoc%2Fr0023574.html
Note that this command works in an async fashion.