ArcMap

Create Replica

Summary

Creates a replica to a geodatabase from a specified list of feature classes, layers, datasets, and/or tables in an enterprise geodatabase.

Usage

  • All datasets must be from the same enterprise geodatabase.

  • The data that you wish to replicate must be versioned, but not with the option to move edits to base. The database user who is connected must also have write permissions to the data. For two-way and both types of one-way replicas, all datasets must have a globalid column and have a high-precision spatial reference.

  • For check-out and one-way replicas, the child replica geodatabase can be an enterprise, file, or personal geodatabase.

  • For two-way and one-way, child-to-parent replicas the child geodatabase must be an enterprise geodatabase.

  • To use archiving for one-way replicas, the parent workspace must be connected to the Default version. For one-way, child-to-parent replicas the child workspace must be connected to the Default version.

  • In ArcMap the definition query and selection properties set on a layer or table determine what data gets replicated.

  • For tables the default filter is Schema Only; only the schema for the table will be replicated. To apply a filter to a table you must first create a table view setting desired filters. You can then use this as input into the Create Replica tool. See the Make Table View for more information. For more information on filters and replication see Preparing data for replication.

  • Replica Geometry Features can be used to define the replica geometry. You can also use the Extent environment setting to define the replica geometry.

    • If only the Replica Geometry Features are set, only data intersecting the Replica Geometry Features will be replicated.
    • If only the Extent environment setting is set, only data intersecting the extent will be replicated.
    • If both the Replica Geometry Features and the Extent environment are set, the Replica Geometry Features will be used.
    • If neither the Replica Geometry Features nor the Extent environment is specified, the full extent of the data is used.

  • The replica geometry features can be points, lines, or polygons.

  • A feature layer used for the replica geometry features can contain one or more features. If there are more than one, the geometries are merged, and only data that intersects the merged geometries will be replicated.

  • If filters (such as spatial, selection, or definition query) have been defined on the replica geometry features, only features that satisfy these filters will be used to define the replica geometry. See Preparing data for replication for more information.

  • The Re-use Schema parameter options are only available for checkout replicas.

Syntax

CreateReplica(in_data, in_type, out_geodatabase, out_name, {access_type}, {initial_data_sender}, {expand_feature_classes_and_tables}, {reuse_schema}, {get_related_data}, {geometry_features}, archiving)
ParameterExplanationData Type
in_data
[in_data,...]

The data to be replicated. This list consists of layers and tables referencing versioned, editable data from an enterprise geodatabase.

Layer; Table View; Dataset
in_type

The kind of replica to create.

  • TWO_WAY_REPLICA — Changes can be sent between child and parent replicas in both directions.
  • ONE_WAY_REPLICA —Changes are sent from the parent replica to the child replica only.
  • CHECK_OUT —Data is replicated, edited, and checked back in one time.
  • ONE_WAY_CHILD_TO_PARENT_REPLICA —Changes are sent from the child replica to the parent replica only.
String
out_geodatabase

The local geodatabase or geodata service that will host the child replica. Geodata services are used to represent remote geodatabases. The geodatabase can be an enterprise, file, or personal geodatabase. For two-way replicas the child geodatabase must be an enterprise geodatabase. For one-way and check-out replicas the geodatabase can be personal, file, or enterprise geodatabase. Personal or file geodatabases must already exist before running this tool.

Workspace ; GeoDataServer
out_name

The name that identifies the replica.

String
access_type
(Optional)

The type of access you want:

  • FULL —Supports complex types (topologies and geometric networks) and requires the data to be versioned.
  • SIMPLE —The data on the child is not versioned and must be simple. This allows the replica to be interoperable. Nonsimple features in the parent (for example, features in geometric networks and topologies) are converted to simple features (for example, point, line, and polygon feature classes).
String
initial_data_sender
(Optional)

Used by replication to determine which replica can send changes when in disconnected mode. If you are working in a connected mode, this parameter is inconsequential. This ensures that the relative replica doesn't send updates until the changes are first received from the initial data sender.

  • CHILD_DATA_SENDER
  • PARENT_DATA_SENDER
String
expand_feature_classes_and_tables
(Optional)

Specifies whether you will include expanded feature classes and tables, such as those found in geometric networks, topologies, or relationship classes.

  • USE_DEFAULTS —Adds the expanded feature classes and tables related to the feature classes and tables in the replica. The default for feature classes is to replicate all features; the default for tables is to replicate the schema only. If a spatial filter has been defined it will be applied to feature classes.
  • ADD_WITH_SCHEMA_ONLY —Adds only the schema for the expanded feature classes and tables.
  • ALL_ROWS —Adds all rows for expanded feature classes and tables.
  • DO_NOT_ADD —Doesn't add expanded feature classes and tables.
String
reuse_schema
(Optional)

Indicates whether to reuse a geodatabase that contains the schema of the data you want to replicate. This reduces the amount of time required to replicate the data. This option is only available for check-out replicas.

  • DO_NOT_REUSE —Do not reuse schema. This is the default.
  • REUSE —Reuse schema.
String
get_related_data
(Optional)

Specifies whether to replicate rows related to rows already in the replica. For example, consider a feature (f1) inside the replication filter and a related feature (f2) from another class outside the filter. Feature f2 is included in the replica if you choose to get related data.

  • DO_NOT_GET_RELATED —Do not replicate related rows.
  • GET_RELATED —Replicate related data. This is the default.
String
geometry_features
(Optional)

The features used to define the area to replicate.

Feature Layer
archiving

Specifies whether to use the archive class to track changes instead of using the versioning delta tables. This is only available for one-way replicas.

  • ARCHIVING —Uses archiving to track changes.
  • DO_NOT_USE_ARCHIVING —Does not use archiving to track changes. This is the default.
Boolean

Code sample

CreateReplica example 1 (Python window)

The following Python Window script demonstrates how to use the CreateReplica function in the Python window.

import arcpy
from arcpy import env
env.workspace = "C:/Data/MySDEdata.sde"
arcpy.CreateReplica_management("roads", "ONE_WAY_REPLICA", "C:\Data\MyTargetGDB.gdb", "MyReplica", "FULL", \
"PARENT_DATA_SENDER", "USE_DEFAULTS", "DO_NOT_REUSE", "TRUE")
CreateReplica example 2 (stand-alone Python script)

The following Python script demonstrates how to use the CreateReplica function in a stand-alone Python script.

# Name: CreateReplica_Example2.py
# Description: Create a one-way replica of a Feature Dataset to a file geodatabase. 

# Import system modules
import arcpy
from arcpy import env

# Set workspace
env.workspace = "C:/Data/MySDEdata.sde"

# Set local variables
in_data = "Parks" # a feature dataset
replica_type = "ONE_WAY_REPLICA"
output_workspace = "C:\Data\MyTargetGDB.gdb"
replica_name = "MyReplica"
access_type = "FULL"
initial_sender = "PARENT_DATA_SENDER"
expand = "USE_DEFAULTS"
reuse_schema = "DO_NOT_REUSE"
get_related = "GET_RELATED"
replica_geometry = "LA_County"
archiving = "DO_NOT_USE_ARCHIVING"

# Execute CreateReplica
arcpy.CreateReplica_management(in_data, replica_type, output_workspace, replica_name, access_type, \
initial_sender, expand, reuse_schema, get_related, replica_geometry, archiving)

Environments

Licensing information

  • Basic: No
  • Standard: Yes
  • Advanced: Yes

Related topics