Help

Re-Export Unacknowledged Messages

Summary

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

Usage

  • This tool is used when synchronizing replica while disconnected. This is done by first running the Export Data Change Message tool which creates a delta file with changes to synchronize. The delta file is then copied to the relative replica and imported using the Import Message tool. If a delta file gets lost and you want to resend, you can use the Re-Export Unacknowledged Messages tool to regenerate the delta file. After the changes are imported, the relative replica can export an acknowledgment file using the Export Acknowledgement Message tool. The acknowledgment file is copied to the replica and imported using the Import Message tool. If an acknowledgment is not received, the next time changes are sent they will include the new changes plus the previously sent changes.

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

  • This tool cannot be used for checkout replicas.

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

Syntax

ReExportUnacknowledgedMessages_management (in_geodatabase, output_delta_file, in_replica, in_export_option)
ParameterExplanationData Type
in_geodatabase

Specifies the replica geodatabase from which to reexport the unacknowledged messages. The geodatabase may be a local geodatabase or a geodata service.

Workspace; GeoDataServer
output_delta_file

Specifies the delta file in which to reexport data changes.

File
in_replica

The replica from which the unacknowledgment messages will be reexported.

String
in_export_option
  • ALL_UNACKNOWLEDGED —Reexports all changes for which there has been no acknowledgment message received.
  • MOST_RECENT —Reexports only those changes since the last set of exported changes was sent.
String

Code sample

ReExportUnacknowledgedMessages example 1 (Python window)

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

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

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

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


# Import system modules
import arcpy
from arcpy import env

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

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

# Execute ReExportUnacknowledgedMessages
arcpy.ReExportUnacknowledgedMessages_management(replica_gdb, output_file, replica_name, export_option)

Environments

Licensing information

  • ArcGIS for Desktop Basic: No
  • ArcGIS for Desktop Standard: Yes
  • ArcGIS for Desktop Advanced: Yes

Related topics