Re-export Unacknowledged Messages (Data Management)

Summary

Creates an output delta file containing unacknowledged replica updates from a one-way or two-way replica geodatabase.

Usage

  • Use this tool when synchronizing a replica while disconnected. First run the Export Data Change Message tool, which creates a delta file with changes to synchronize. Then copy and import the delta file to the relative replica using the Import Message tool. If the delta file gets lost and you want to resend, use the Re-Export Unacknowledged Messages tool to regenerate the delta file. After the changes are imported, you can export an acknowledgment file from the relative replica using the Export Acknowledgement Message tool. Copy and import the acknowledgment file using the Import Message tool. If the acknowledgment is not received, the next time changes are sent, they will include the new changes and the previously sent changes.

  • The output delta file can be a delta file geodatabase (.gdb) or a delta XML file (.xml). When specifying the output delta file, you must include the appropriate suffix (.gdb or .xml).

  • This tool cannot be used for checkout replicas.

  • To synchronize replicas in a connected mode, see the Synchronize Changes tool.

Parameters

LabelExplanationData Type
Export from Replica Geodatabase

The replica geodatabase from which the unacknowledged messages will be reexported. The geodatabase can be a local geodatabase or a geodata service.

Workspace; GeoDataServer
Output Delta File

The delta file to which data changes will be reexported.

File
Replica

The replica from which the unacknowledged messages will be reexported.

String
Export options

Specifies the changes that will be reexported.

  • All unacknowledgedAll changes with unacknowledged messages will be reexported.
  • Most recentOnly those changes made since the last set of exported changes was sent will be reexported.
String

arcpy.management.ReExportUnacknowledgedMessages(in_geodatabase, output_delta_file, in_replica, in_export_option)
NameExplanationData Type
in_geodatabase

The replica geodatabase from which the unacknowledged messages will be reexported. The geodatabase can be a local geodatabase or a geodata service.

Workspace; GeoDataServer
output_delta_file

The delta file to which data changes will be reexported.

File
in_replica

The replica from which the unacknowledged messages will be reexported.

String
in_export_option

Specifies the changes that will be reexported.

  • ALL_UNACKNOWLEDGEDAll changes with unacknowledged messages will be reexported.
  • MOST_RECENTOnly those changes made since the last set of exported changes was sent will be reexported.
String

Code sample

ReExportUnacknowledgedMessages example 1 (Python window)

The following Python window example demonstrates how to use the ReExportUnacknowledgedMessages function.

import arcpy
arcpy.env.workspace = "C:/Data"
arcpy.management.ReExportUnacknowledgedMessages("MySDEdata.sde", "dataChanges2.gdb", 
                                                "MyReplica1", "ALL_UNACKNOWLEDGED")
ReExportUnacknowledgedMessages example 2 (stand-alone script)

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

# Name: ReExportUnacknowledgedMessages_Example2.py
# Description: Reexport all unacknowledged messages from an SDE replica workspace.
# Changes are exported to a delta geodatabase

# Import system modules
import arcpy

# Set workspace
arcpy.env.workspace = "C:/Data"

# Set local variables
replica_gdb = "MySDEdata.sde"
output_file = "dataChanges2.gdb"
replica_name = "MyReplica1"
export_option = "ALL_UNACKNOWLEDGED"

# Run ReExportUnacknowledgedMessages
arcpy.management.ReExportUnacknowledgedMessages(replica_gdb, output_file, 
                                                replica_name, export_option)

Licensing information

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

Related topics