RENEW (Global Project Administration)
- Last UpdatedJan 30, 2025
- 2 minute read
Function:
Deletes a transaction Database (DB) and creates a fresh version.
Description:
If a transaction DB becomes corrupt, it may be necessary to delete it and then re-create it. Existing commands in the DB may be retained by RECONFIGURING to file before the RENEW, and from file after the RENEW.
This daemon command is available with two options, namely DELETE and AT. It deletes an existing transaction DB file at a Location and creates a fresh version.
The RENEW DELETE <DB> command is the preferred method of re-creating the transaction DB file, as it works even when the DB is too corrupt for the daemon to run.
Note:
<DB> must be the transaction DB for the current Location, as the command cannot be executed
remotely.
When this command is used, AVEVA Administration checks that all Users have left the AVEVA base product and that the daemon has been shut down.
Note:
The check on the daemon takes up to 3 minutes.
AVEVA Administration then deletes the file for the transaction DB (not its DB entry) and prompts the User to leave the AVEVA base product and restart the daemon. When the daemon is restarted, it will automatically recreate the transaction DB file.
The RENEW <DB> AT <loc> command may be used to renew a transaction DB remotely.
Note:
This command may fail if the DB corruption is severe and the daemon at <loc> cannot be started. All Users must be out of the AVEVA base product for the command
to run.
Alternatively, the administrator can renew the transaction DB by stopping the daemon and deleting its file outside the AVEVA base product (not its DB definition). The daemon will automatically create a new transaction DB file when it is restarted.
It is recommended that, after renewing, the System administrator should recover the transaction DB at all Secondary Locations. This will prevent reverse propagation.
For further information about reconfiguring or renewing a transaction DB, refer to Running Global Projects.
The RENEW command is not recorded in the transaction DB.
Examples:
|
RENEW DELETE <db> Renews the transaction DB at the current Location. RENEW TRANSACTION/LON AT LON Renews the transaction DB for London at Location London. |
Command Syntax:
|
>--- RENEW ---+-- DELETE ----- dbname -----. |
Related Commands: