Did this article resolve your question/issue?



How to disconnect a database user with PROSHUT or PROMON

« Go Back


TitleHow to disconnect a database user with PROSHUT or PROMON
URL Name000036460
Article Number000159001
EnvironmentProduct: Progress
Product: OpenEdge
Version: All supported versions
OS: All supported platforms
Other: RDBMS, promon, proshut
Question/Problem Description
How to disconnect a database user with PROSHUT or PROMON OS-COMMANDS
Is there a way to disconnect a database user without PROSHUT or PROMON?
Can a user be disconnected from a database using the _connect vst?
How can a database user be disconnected by a client running on a remote machine that can access the database server?
The PROSHUT -C disconnect user command can only be executed on the database server itself, not from a client.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Outside running OS Kill signals to terminate the PID of the client, which can lead to dbdowns, or application code using the DISCONNECT <ldbname> statement to disconnect the current client session, PROSHUT or PROMON are the only tools available to disconnect a client from a database.

To disconnect a User from the database with PROMON or PROSHUT:
  • promon dbname > Options: 8.  Shut Down Database > 1  Disconnect a User
  • proshut dbname > Option: 1. Disconnect a User
  • proshut dbname -list > Option: 1. Disconnect a User
  • proshut dbname -C disconnect <user number>
For further information refer to Articles: A client can only be disconnected with a user who started the database or the user themselves to perform the disconnect. Refer to Article  Since OpenEdge 11.5 other PROMON sessions can also be disconnected: When there are too many user connections to manually disconnect every connected user, or users need to be disconnected from a remote client session to where the database is running, the process can be scripted by interrogating the _Connect VST and parsing the _Connect-Usr to an OS-COMMAND which runs the PROSHUT -C DISCONNECT utility. Refer to Articles: Considerations when needing to terminate a client session by disconnecting it:
References to Other Documentation:

Progress Article(s):
Considerations when upgrading from OpenEdge 11 to a later OpenEdge 11 version.
Last Modified Date9/15/2020 8:48 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.