Running Global Projects
Off-line Locations : Working Practices with Off-line Locations
Working Practices with Off-line Locations
The following list highlights practices that should be observed:
•
All users must exit before the TRANSFER TO command is initiated. Otherwise, the command may fail.
•
To make sure that the database file is copied to the satellite when a new database is allocated to an off-line location, the TRANSFER TO command must be used at the Hub after the ALLOCATE command. The TRANSFER FROM command is then used at the satellite. The TRANSFER should precede a CHANGE PRIMARY command.
•
Before a CHANGE PRIMARY command to or from an off-line location is initiated, all users of that database should exit. TRANSFER TO (at the old primary location) and TRANSFER FROM (at the new primary location) must be used to make sure the database is up-to-date. The CHANGE PRIMARY command may then be issued. This should be followed by a TRANSFER TO command (at the Hub) and a TRANSFER FROM command (at the off-line location).
•
Extract hierarchies must never be partially off-line. An entire hierarchy must be on-line or off-line.
•
Working extracts cannot be created for off-line locations, unless they are self-administered. (The file for the working extract cannot be created if the Hub administers the off-line location.)
•
Transfer of other data, such as ISODRAFT files, external PLOT files and MODEL manager files, must be done manually to an off-line location and from it.
•
To change a satellite from on-line to off-line, shut down its daemon and change ICONN to 0. Manually copy the Global database to the off-line location. The TRANSFER command will then work.
•
Picture Files and DWG files are transferred to Offline Locations and should be copied on CD/through ftp when they reside in the locations Transfer area.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo