Re-export Unacknowledged Messages (Data Management Tools)
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 (.gdbor.xml).This tool cannot be used for checkout replicas.
To synchronize replicas in a connected mode, see the Synchronize Changes tool.
Parameters
| Label | Explanation | Data 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.
|
String |
Environments
Current Workspace, Scratch Workspace
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes