While performing database maintenance operations such as database restore and database backup, the Database Administrator needs a clean environment that is free of any interruptions from the users that might modify the existing state of the database.

OpenEdge restricted online mode allows you to do maintenance operations while keeping the buffer pool and helper processes running, thereby enhancing performance. You can also run the tasks offline in the restricted mode. When the restricted mode is enabled, only the database utilities with -dbrestrict permission can connect to the database.

To restrict access, use the PROUTIL DBRESTRICT DBADMIN ENABLE qualifier. You can run it while online or offline. The command defaults to a ten-minute wait period, then prompts you to confirm before disconnecting database clients. You can specify your own timeout using the DISCONNTIMEOUT argument. For example:
proutil Source/source -C dbrestrict dbadmin enable disconntimeout 500
OpenEdge Release 12.4 as of Fri Dec 11 18:31:28 EST 2020

Will start to disconnect active users in 500 seconds. (20188)
Use CTRL-C to interupt the timeout.
^C
There are still 1 users connected to the database. Enter your option:
  1.  Continue to wait for another 500 seconds
  2.  Immediately disconnect all active users
  3.  Abort the operation
2
Start to disconnect all active users.
User 2 disconnect initiated. (6796)
When the command succeeds:
  • All existing users without -dbrestrict permissions are logged out.
  • No live transactions remain.
  • Before-image and after-image logs are flushed.
  • Database utilities with -dbrestrict permission can log in.

For more information, see PROUTIL DBRESTRICT qualifier.

You can also enable restricted access to the database by adding the -dbrestrict parameter to the PROREST command while performing both the partition data recovery and the tenant data recovery. For details on restrictions applied during the partition data recovery, see Step 1: Restoring your database backup, and for the tenant data recovery, see Step 1: Restore your database backup.