Manage the OpenEdge Database

Roll-forward recovery with more than 100 rekey operations

Save PDF

Roll-forward recovery with more than 100 rekey operations

Save PDF

Last Updated: February 11, 2026
2 minute read

OpenEdge
Version 13.0
Documentation

If more than 100 TDE DB Policy Rekey operations occur after backing up the hot standby database, users cannot use the latest copy of keystore of the source database to start roll-forward process. They cannot use the latest copy of the keystore because the oldest DMK needed to open the target database no longer exists in this copy of the keystore. Users need to use the OS copy of the keystore that contains the DMK at the point when RFUTIL roll-forward had started.

Note: Please note that each time users run TDE DB Policy Rekey that creates a new DMK and retire the old one,they are asked to make an OS copy of the keystore. As a good practice, save the OS copy and mark it with timestamp or sequence number.

Users need the OS copy in the roll-forward process if the keystore on the source database has reached the 100 rekey operation limit and no longer keeps the oldest DMK.

Follow the steps in this example when more than 100 rekey operations are involved in the roll-forward process:

Back up the source database sourceDB using PROBKUP, for example:
```
probkup sourceDB sourceDB.bck
```
Note that PROBKUP does not back up the keystore, users need to copy and save it. If there are over 100 TDE DB Policy rekey operations after this point, the latest version of keystore on the source database no longer keeps the DMK needed by the target database. You can use this copy to open the target database and perform AI roll-forward.
Start after-imaging on the source database:
```
rfutil sourceDB -C aimage begin
```
Perform some database activities on the source database that fill some AI extents, including TDE DB Policy Rekey options up to 100 times, for example:
```
...
```
```
backup keystore to ks.save.1
```
Perform a DB Policy rekey (#1)
```
...
```
```
backup keystore to ks.save.2
```
Perform a DB Policy rekey (#2)
```
...
```
```
backup keystore to ks.save.100
```
Perform a DB Policy rekey (#100)
```
...
```
```
backup keystore to ks.save.110
```
Perform a DB Policy rekey (#110)
Users decide to roll forward after-imaging on the hot standby database. To roll forward:
1. Restore the hot standby database from the backup of the source database:
```
prorest targetDB sourceDB.bck
```
2. Perform roll-forward recovery on the hot standby database with one of two parameters – -a or -ailist.. For example, for -a:
```
cp ks.save.100 targetDB.ks
```
```
rfutil targetDB -C roll forward -a sourceDB.a1
```
```
rfutil targetDB -C roll forward -a sourceDB.a2
```
```
...
```
  Alternatively, use -ailist, as follows:
```
rfutil targetDB -C roll forward -ailist listFile
```
  Now, fewer than 100 DB policy rekey operations are left in the remaining AI extents.
3. Copy the latest keystore from the source database and continue the roll-foward process:
```
cp sourceDB.ks targetDB.ks
```
```
rfutil targetDB -C roll forward -a sourceDB.aN
```
  Note:
  If you prefer to use -ailist, use commands such as the following to copy the keystore then continue the roll-forward process:
```
cp ks.save.1 targetDB.ks
```
```
rfutil targetDB -C roll forward -ailist listFile
```
Make sure that the keystore is up to date:
```
cp sourceDB.ks targetDB.ks
```