Synchronize with the Initial Extract Version
Also referred to as "bootstrapping," this method uses the initial extract version in the SDE geodatabase to create a replica that contains all changes made to the geodatabase since the initial extract version was made.
Multiple Replicas: Reinitialization can take a large amount of time, so reinitialize only the replica(s) that failed.
- If you have multiple replicas, you will need to disable all replicas that do NOT need to be reinitialized. If you have only one replica (total), skip to step 4. Use the ArcFM Geodatabase Replication Administrator on the replication server to open ReplicationConsole.exe.config. You may save this file to another location as a backup if you wish. (It can be used later to quickly enable all replicas.)
- Select a replica that does NOT need to be reinitialized and set its Enabled field to False. Repeat this for all replicas that do NOT need replication.
- Save the configuration file. Select File | Save Configuration File from the main menu. You must save the configuration file in its current location (ArcFM Solution\Bin).
- On the Replication Server, stop Geodatabase Replication.
- In the SDE geodatabase delete the "Replica" version of your initial extract version for the replica being reinitialized. For example, if your initial extract version is named InitialExtract, then you will need to delete a version called InitialExtract_Replica.
- In the SDE geodatabase delete the "Replica_BACK" version
of your initial extract version. For example, InitialExtract_Replica_BACK. TIP: The name of your initial extract version is set in the ReplicationConsole.exe.config file. Look at the Initial Extract Version field value in the ArcFM Geodatabase Replication Administrator.
- Browse to the Base Path and select the directory for the database on which the replication failed.
- Delete all directories in this folder. For example, if
the Electric replication failed. Browse to ServerBase\Electric and
delete all "Extract" folders in this directory (all folders highlighted
in red in Figure 1). If a FullDatabases directory resides here, delete
it as well.
IMPORTANT: During this step, client machines will experience errors if they are attempting communicate with the Replication server for updates. This is expected behavior and will occur until this synchronization is complete. - Start Geodatabase Replication. Because all "Extract" subdirectories were deleted (in step 8), Geodatabase Replication is forced to use the geodatabase in the InitialExtracts directory. This means that all changes made to the SDE geodatabase since the creation of the database in this directory will be included in the replication. If this means a large number of changes, the replication will take longer.
- Once the replication in step 9 is complete, clients will need to get full database updates. Client machines will attempt and fail to get updates a set number of times. This number is determined by the Number of Retries for Full Download field in the Client Configuration File. After these tries, it will download the full database. Schneider Electric recommends that clients obtain the fastest available connection to download the full database.
- If you have only a single replica, the reinitialization is complete and you can skip the remaining steps. If you have multiple replicas, you must enable the replicas that were disabled in step 2. On the Replication Server, stop Geodatabase Replication.
- If you saved a backup of the ReplicationConsole.exe.config file in step 1, you can replace the copy in the Bin directory with your backup. Otherwise, open ReplicationConsole.exe.config on the server using the ArcFM Geodatabase Replication Administrator. Select all disabled replicas and set their Enabled fields to True.
- Save changes to the configuration file and start Geodatabase Replication.