SYNCHRONISE (Global Project Administration)
- Last UpdatedMar 22, 2022
- 4 minute read
Function:
Updates Databases (DBs) with the changes from another Location.
Description:
This command updates one, all, or a Set of DBs at an online Location with the changes in the corresponding DBs at another Location. The set of DBs may be specified by DBSET or MDB elements as well as by an explicit list.
By default, the updates will be taken from the Primary Location, but the Hub administrator can specify that they will be taken from another Location which is an immediate neighbor of the Location requiring the updates.
Unlike UPDATE, the transfer is one-way only: the synchronizing Location only receives updates, it does not send them. All Locations in the communications network between the two Locations being synchronised will also be updated.
Note:
If the more up-to-date DB has been compacted, that is, sessions have been merged,
or if it has been backtracked, the entire DB will be transferred.
Updates for offline Locations can only come from the Hub.
Examples of synchronization of constructor DBs:
|
SYNCHRONISE STEELN/STEELN Synchronizes the given DB at current Location with its Primary Location. SYNCHRONISE ALL Synchronizes all DBs at current Location with their Primary Locations. |
|
SYNCHRONISE STEELN/STEELN AT LON Synchronizes the given DB at Location LON with its Primary Location. SYNCHRONISE ALL AT LON Synchronizes all DBs at Location LON with their Primary Locations. |
|
SYNCHRONISE STEELN/STEELN WITH LON Synchronizes the given DB at current Location with Location LON. SYNCHRONISE STEELN/DRAWINGS DRAWINGS/ONLY (FORCE/PICFD) Synchronizes drawing-files for a Drawings DB (PADD or SCHE). This command allows the drawing-files to be transferred without a DB update. This can be useful if a DB update has been succeeded without updating its drawings. If the FORCE/PICFD option is specified, then the PICFD attribute of the DB is ignored and all drawings will be synchronized. This command can only be used on individual DBs, and not with the DBLIST option. |
|
SYNCHRONISE ALL WITH LON Synchronizes all DBs at current Location with Location LON. SYNCHRONISE STEELN/STEELN AT LON WITH CAM Synchronizes a single DB at Location LON with Location CAM. |
Examples of synchronization of System DBs:
|
SYNCHRONISE SYSTEM WITH CAM Synchronizes the System DB for the current Location with Location CAM. SYNCHRONISE SYSTEM AT LON WITH CAM Synchronizes the System DB for the current Location at Location LON with Location CAM. SYNCHRONISE SYSTEM FOR OXF AT LON WITH CAM Synchronizes the System DB for OXF at Location LON with Location CAM. |
Examples of synchronization of the Global DB:
|
SYNCHRONISE GLOBAL WITH CAM Synchronizes the Global DB at the current Location with Location CAM. SYNCHRONISE GLOBAL AT LON WITH CAM Synchronizes the Global DB at Location LON with Location CAM. SYNCHRONISE GLOBAL AT OXF Synchronizes the Global DB at OXF with the current Location. |
Examples of synchronization of the Global DB using DBLIST:
|
SYNCHRONISE DBLIST <update-list> <synchronise-options> To SYNCHRONIZE a set of DBs use a list of DBs, MDBs, or DBSETs. These are passed to the daemon as a list of DB element names:
|
|
Valid elements include MDB, DBSET, DB or LOC elements; SYNCHRONISE DBLIST MDB/ATEST AT OXF; Synchronizes all the DBs in MDB/ATEST that are allocated but not Primary at OXF. SYNCHRONISE DBLIST DBSET /FRED WITH CAM; Synchronizes all the DBs in DBSET/ FRED that are allocated but not Primary at CAM. |
|
SYNCHRONISE DBLIST GLOBAL SYSTEM FOR LON AT CAM; Synchronizes the Global DB and the LON System DB at CAM. SYNCHRONISE DBLIST STEELN/STEEL PIPEN/PIPE AT OXF Synchronizes the STEELN/STEEL and PIPEN/PIPE DBs at OXF. The Primary Location must not be OXF. |
Examples of synchronization of the Global DB using linked document propagation:
|
For a DESIgn DB: SYNCHRONISE DBNAME LINKDOCUMENTS {FORCE|NOFORCE} (AT <Locname>) |
|
For DRAFT or SCHE DBs: SYNCHRONISE DBNAME DRAWINGS/ONLY {FORCE|NOFORCE} (AT <Locname>) (WITH <Locname>) For example: SYNCHR CTBATEST/DESI LINKDOC AT CAM SYNCHR CTBATEST/PADD DRAWINGS FORCE The keyword FORCE has a slightly different meaning for the two cases: For drawing DBs, FORCE will copy non-propagating drawings such as picture files even if their propagation has been disabled. For linked documents, the files will be transferred to the Secondary Location even if they already exist, thus updating them. |
Command Syntax:
|
>- SYNCHronise -+- dbname --------------------. |
The <linkdoc> can be as follows:
|
>-SYNCHRONISE-+-dbname-+-LINKDOC/UMENTS---. |
The <update-list> can be as follows:
|
<update-list>--+--GLOBALdb --------------------. |
The <element-id> may be an MDB, DBSET, DB or LOC.
Related Commands: