Updating References into a Reconfigured Database
- Last UpdatedMar 18, 2022
- 2 minute read
While a Database (DB) is being reconfigured without the SAMEREF option, the RECONFIGURER builds up an index of the reference numbers of all elements in the source DB versus their corresponding new reference numbers in the destination DB. The RCFUPDATE command uses this index to check reference pointers in other DBs and update them to point to the correct elements in the reconfigured DB.
Example: |
|---|
|
RCFUPDATE DB MASTER/DESIGN Updates references to the reconfigured DB from DB MASTER/DESIGN. |
|
RCFUPDATE DB MASTER/DESIGN INTERNAL Updates references in DB MASTER/DESIGN for any elements that have been copied with RCFCOPY ALL CONNECTIONS. Use this option with care because it is possible to update a reference that has already been changed by the RECONFIGURE command. |
|
RCFUPDATE MDB /USERA Updates all references to the reconfigured DB from DBs in MDB /USERA. |
|
RCFUPDATE TEAM USER Updates all references to the reconfigured DB from DBs owned by TEAM USER. |
Note:
The RCFUPDATE command must be given immediately following a RECONFIGURE operation.
As the RCFUPDATE command may cause a DB to be written to, the administrator must have read-write access to all relevant DBs. The DBs must not be in active use by any other user of the Project.
Care should be taken when reconfiguring to the same DB Number. If the administrator updates a DB twice, the resulting reference numbers could be wrong. For example:
|
Old reference |
New reference |
|
|
/VESS1 |
=123/456 |
=123/457 |
|
/VESS2 |
=123/457 |
=123/458 |
Thus, giving the RCFUPDATE command twice results in the reference =123/456 being reset to =123/458.
The RECONFIGURER knows which types of DB can be pointed to by reference attributes in other types of DB, and so does not attempt to update DBs which could not possibly point to the latest reconfigured copy. A report is output which lists which DBs were and which were not updated.
The table of references is maintained across multiple reconfigurations, as long as the administrator does not exit from AVEVA Administration.