PROUTIL DBRESTRICT qualifier
- Last Updated: May 26, 2022
- 2 minute read
- OpenEdge
- Version 12.2
- Documentation
PROUTIL DBRESTRICT qualifier
Enables or disables write access to the database for processes other than the specified utility.
Syntax
|
Parameters
- db-name
- Specifies the database where you are controlling access.
- restrict-type
-
Specifies the operation to allow (restricting other access). Accepted values are:
-
datamove— restrict all operations, excepting PROUTIL DATAMOVE partitioncopy— restrict all operations, excepting PROUTIL PARTITIONMANAGE COPYrollforward— restrict all operations, excepting RFUTIL ROLL FORWARD
-
- restrict-action
-
Specifies starting, ending, or querying the status of the restriction. Accepted values are:
-
enable— start the restriction -
disable— end the restriction -
status— query the restriction, returning a message indicating if the restriction is enabled or disabled
-
Use DBRESTRICT to protect your database from modification by other processes during the execution of the identified utility. When enabled, access is allowed as follows:
- For DATAMOVE, the following is allowed:
- PROUTIL DATAMOVE
- Database brokers
- PROMON
- PROSHUT
- PROUTIL DBRESTRICT (to modify or disable the restriction)
- For PARTITIONCOPY, the following is allowed:
- PROUTIL PARTITIONMANAGE COPY
- PROUTIL PARTITIONMANAGE VIEW
- Database brokers
- PROMON
- PROSHUT
- PROUTIL DBRESTRICT (to modify or disable the restriction)
- For ROLL FORWARD, the following is allowed:
- RFUTIL ROLL FORWARD
- PROSTRCT ADD
- PROSTRCT LIST
- PROUTIL IDXCHECK
- PROUTIL IDXANALYS
- PROUTIL TABANALYS
- PROUTIL DBANALYS
- PROUTIL DBRESTRICT (to modify or disable the restriction)
Example
-
Datamove
restriction
The DATAMOVE utility requires restricted access to the database. The following example shows how to enable restricted access on a database named
mydb:proutil mydb -C dbrestrict datamove enableOnce you have completed the data move, remove the access restriction as shown:
proutil mydb -C dbrestrict datamove disable - Migrating a restriction from rollforward to
datamove
If you first restrict access to your database for roll forward, you can migrate the restriction to data move without first disabling the roll forward restriction.
1. Verify that the database is in rollforward restricted mode, as shown:
proutil mydb -C dbrestrict rollforward status2. The following status is returned:
Restricted Access Mode is enabled for RollForward (17073)3. Migrate the restriction:
proutil mydb -C dbrestrict datamove enable4. The following status is returned:
Database Restricted Access mode has been disabled for RollFoward (17039) Database Restrict Access has been enabled for DataMove (17037)
Notes
- You must truncate the BI of your database prior to enabling DBRESTRICT.
- Your database must be offline when you run DBRESTRICT.
- Your database restriction status is shown in the PROMON Database Status displays.
- The Restricted Modes status is available in the read only
_dbStatusVST, in the field named_DbStatus-RestrictMode. The field label is Restricted Access Mode, and supported field values are: DataMove, Rollforward, and disabled. - If you run DBRESTRICT on a Replication source database, you must still supply all your replication parameters to start a broker, however, the replication server will not start until you have disabled the restriction.