Only the following users are able to shutdown a Progress OpenEdge database with PROMON or PROSHUT:
- The database owner or the account that created the database
- The account that started the database.
- The root account in UNIX or the Administrator account in Windows can disconnect other users but not necessarily shutdown the database.
- While Users can disconnect themselves, they cannot necessarily shutdown the database.
Use the PROSHUT command with -S and -H parameters as follows:
1) First start the PROENV script to set the appropriate environment variables:
[Windows]: "Start" button on windows taskbar > Select "Programs" > Progress icons group and Select "proenv"
or run <progress installation path>/bin/proenv.bat from a cmd shell.
[Unix/Linux]: Execute proenv script using the command line: <progress installation path>/bin/proenv
2) Shutdown the remote database:
$ proshut <dbname> -H <hostname> -S <portnumber> [-Mm <value>]Example: Assuming that the database is named "sports2000", the hostname is dbserv and the port number is 6789 and the database was started with (non default) -Mm 2048.
$ proshut sports2000 -H dbserv -S 6789 -Mm 2048This will show the list of users currently connected (if any), and then following menu:
1 Disconnect a User
2 Unconditional Shutdown
x Exit
Enter choice> _3) Option 2 "Unconditional Shutdown" will shut down the database.
After Option 2 is selected, an informational message 1613 will confirm shutdown afterwhich operating system prompt will return:
1 Disconnect a User
2 Unconditional Shutdown
x Exit
Enter choice> 2Shutdown is executing. (1613)proenv> _In order for a remote database shutdown to succeed:
- The database server must have been started with the -S startup parameter, so that the port is open for remote connections.
- The database must not be running on a cluster.
- The database must not have been started with -normtshutdown startup parameter to prevent remote proshut. (This feature is available since Progress 9.1E01 and OpenEdge 10.0B02 +)
- It may take some time before the database is actually down because of the clean up operations that the database server has to perform before actually bringing the database to a halt.
- Since OpenEdge 10.2B the parameter -shutdownTimeout can be used to limit the maximum time it takes to normally shutdown the database. The default is 10 minutes.
