Procedure: Disconnecting user sessions
- Last Updated: January 14, 2019
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
While your database is running, sometimes it may be necessary to disconnect an individual session that is currently connected to the database. Note that user sessions include background processes, PROMONs, and online backups.
For example, a session might be locking records that are required by other users, but the person who started the session has left for the day. Disconnecting a session terminates any active transactions that the session is incurring as well as releasing any record locks.
Another scenario is that you might have launched multiple APWs at database startup and over time found out that fewer APWs were actually required. In such a case, you could disconnect one or more APW instances to improve performance.
To disconnect a session, you first identify the user ID associated with the session, and then terminate the session using the user ID.
Follow these steps to disconnect a session using PROMON:
|
Step |
Action |
|---|---|
| 1 |
Invoke PROMON on your running database:
|
| 2 |
At the “Enter your selection:” prompt, enter 1 (for User Control). |
| 3 |
At the next “Enter your selection:” prompt, enter 1 (for Display all entries). Information about different database sessions such as user ID, user name, type, and login time, is displayed. Make a note of the user ID of the session you want to disconnect. |
| 4 |
Enter q to return to the main PROMON prompt. |
| 5 |
At the “Enter your selection:” prompt, enter 8 (for Shut Down Database). |
| 6 |
At the “Enter choice>” prompt, enter 1 (for Disconnect a User). |
| 7 |
At the “Enter the user number which is to be disconnected:” prompt, enter the user ID found in Step 3. The session is terminated. |
| 8 |
At the “Enter choice>” prompt, enter x to return to the main PROMON prompt. |
| 9 |
At the “Enter your selection:” prompt, enter q to exit PROMON. |
Note: In UNIX, do not disconnect a user session with the command kill –9 because it could shut down and possibly damage the database.