SYNCHRONISE (Global Project Administration)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : SYNCHRONISE (Global Project Administration)

Updates databases with the changes from another location.

This command updates one, all or a set of databases at an on-line Location with the changes in the corresponding databases at another location. The set of databases 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 neighbour of the Location requiring the updates.

Unlike UPDATE, the transfer is one-way only: the synchronising 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 that if the more up-to-date database has been compacted, that is, sessions have been merged, or if it has been backtracked, the entire database will be transferred.

Updates for offline Locations can only come from the Hub.

Examples of synchronisation of constructor databases:


SYNCHRONISE STEELN/STEELN Synchronise given database at current location with its Primary location. SYNCHRONISE ALL Synchronise all databases at current location with their Primary locations.
SYNCHRONISE STEELN/STEELN AT LON Synchronise given database at location LON with its Primary location. SYNCHRONISE ALL AT LON Synchronise all databases at location LON with their Primary locations.
SYNCHRONISE STEELN/STEELN WITH LON Synchronise given database at current location with location LON. SYNCHRONISE STEELN/DRAWINGS DRAWINGS/ONLY (FORCE/PICFD) Synchronise drawing-files for a Drawings database (PADD or SCHE). This command allows the drawing-files to be transferred without a database update. This can be useful if a database update has been succeeded without updating its drawings. If the FORCE/PICFD option is specified, then the PICFD attribute of the database is ignored and all drawings will be synchronised. This command can only be used on individual databases, and not with the DBLIST option.
SYNCHRONISE ALL WITH LON Synchronise all databases at current location with location LON. SYNCHRONISE STEELN/STEELN AT LON WITH CAM Synchronise single database at location LON with location CAM.

Examples of synchronisation of system databases:


SYNCHRONISE SYSTEM WITH CAM Synchronise the System Database for the current Location with location CAM SYNCHRONISE SYSTEM AT LON WITH CAM Synchronise the System Database for the current location at location LON with location CAM SYNCHRONISE SYSTEM FOR OXF AT LON WITH CAM Synchronise the System Database for OXF at location LON with location CAM

Examples of synchronisation of the global database:


SYNCHRONISE GLOBAL WITH CAM Synchronise the Global Database at the current Location with location CAM SYNCHRONISE GLOBAL AT LON WITH CAM Synchronise the Global Database at location LON with location CAM SYNCHRONISE GLOBAL AT OXF Synchronise the Global Database at OXF with the current location.

Examples of synchronisation of the global database using DBLIST:

SYNCHRONISE DBLIST <update-list> <synchronise-options>

To SYNCHRONISE a set of databases use a lists of DBs, MDBs, or DBSETs.

These are passed to the daemon as a list of DB element names:

•

Where <update-list> may contain one or more of the following –

•

DB <dbnam>

•

GLOBAL/DB

•

SYSTEM/DB FOR <locnam>

•

<element-id>

Valid elements include MDB, DBSET, DB or LOC elements;

SYNCHRONISE DBLIST MDB/ATEST AT OXF;

Synchronise all the databases in MDB/ATEST that are allocated but not primary at OXF

SYNCHRONISE DBLIST DBSET /FRED WITH CAM;

Synchronise all the databases in DBSET/ FRED that are allocated but not primary at CAM

SYNCHRONISE DBLIST GLOBAL SYSTEM FOR LON AT CAM;

Synchronise the Global database and the LON System database at CAM

SYNCHRONISE DBLIST STEELN/STEEL PIPEN/PIPE AT OXF

Synchronise the STEELN/STEEL and PIPEN/PIPE databases at OXF. The Primary location must not be OXF

Examples of synchronisation of the global database using linked document propagation:


For a DESIgn database: SYNCHRONISE DBNAME LINKDOCUMENTS {FORCE\|NOFORCE} (AT <Locname>)
For DRAFT or SCHE databases 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 databases, 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 --------------------. \| \| \| .------<-------. \| \| / \| \| \|-- DBLIST --<update-list>-+- -\| \| \| \|--- SYSTEM -+- FOR -+-- LOCAL -\| \| \| \| \| \| \| ‘-- <loc> -\| \| \| \| \| ‘------------------\| \| \| \|--- GLOBAL --------------------\| \| \| ‘- ALL -------------------------+- AT <loc> --. \| \| ‘-------------+- WITH <loc> -. \| \| ‘--------------+--->

The <linkdoc> can be as follows:-


>-SYNCHRONISE-+-dbname-+-LINKDOC/UMENTS---. \| \| +- DRAWINGS/ONLY --+-+-FORCE-. ‘------------------\|---------\| ‘---------+-AT <loc>-. \| \| ‘----------+-WITH <loc>-. \| \| ‘-------------+-->

The <update-list> can be as follows:-


<update-list>--+--GLOBALdb --------------------. \| \| \|--SYSTEM-- --\|-- FOR ---<loc>--\| \| `-----------------\| \|-- DB ---<dbname>--------------\| \| \| `-- <element-id>----------------+--->

The <element-id> may be an MDB, DBSET, DB or LOC.

Related Commands:

UPDATE, RECOVER