Troubleshoot replication features
- Last UpdatedApr 24, 2025
- 3 minute read
Troubleshooting information is presented here for the following topics:
-
Data inconsistent at destination site.
Data Inconsistent at Destination System
If you suspect that the data at one system differs from the data at another system, use the DPResync (datapump synchronization) utility to compare the tables and, optionally, to correct the data differences between the two systems. The syntax is as follows:
DPResync -S <source service> -D <destination service>
-b <begin date> [-e <end date>][-y <level>][-j <level>]
[-f <datafile>] [-T] [-h]
Where the mandatory parameters are:
|
Parameter |
Description |
|---|---|
|
-S <source service> |
Uses the same format as the DPutil -S option: -S system[:userid/passwd[@service]]. Typically, only the service name is specified, such as the RTDB server name. For full description, execute DPutil -h. |
|
-D <destination service> |
Uses the same format as the -S option. |
|
-b <begin date> |
date in seconds Greenwich Mean Time (GMT) or as a time string in the format: mm/dd/yyyy hh:mm:ss |
Where the optional parameters are:
|
Parameter |
Description |
|---|---|
|
-B |
Run in background; the default is to run in the foreground. |
|
-e <end date> |
Date in seconds GMT or as a time sting in the format: mm/dd/yyyy hh:mm:ss. Defaults to now (current time). |
|
-y <level> |
Defaults to -y1 If<level> =1. Check for differences in the keys between the source and the destination. If <level>=2 but DPFill is called to resolve differences. If <level>=3 Check for differences in all columns. |
|
-j <level> |
Perform an integrity update between the source and destination. If <level>=0 do inserts only. If <level> =1 do inserts and deletes. If <level>=2 do inserts, updates, and deletes. If <level>=3 do inserts, updates (if required) and deletes. |
|
-f <datafile> |
Name of file that describes the tables to synchronize. Defaults to: <DataDirectory>\log\datapump_resync.log |
|
-T |
Run in test mode; do not actually execute against the source or destination. |
|
-h |
Display usage message. |
Example comparing keys on source and destination
DPResync -S NYCXIS -D NECXIS -b 1012539600 -e 1012626000 -f DPResyncData_NYC_to_NEC.txt -y 1
DPResync -S NYCXIS -D NECXIS -b "02/27/2002 00:00:00" -e "02/28/2002 00:00:00" -y 1
DPResync -S NYCXIS -D NECXIS -b "Feb/27/2002 00:00:00" -e "now" -y 1
Example resynchronizing in reverse time order
DPResync -f datapump_resync_filelist.txt -S TGLHIS1 -D TGLDSS1 -j 1 - b "05/24/2003 00:00:00" -e "05/17/2003 00:00:00"
Note: To prevent comparison and synchronization activities during times that may already have high system activity, DPResync halts processing at 5 minutes before the top of hour, and then continues processing again at 15 minutes past the top of hour.
The DPResync utility uses other utilities to perform the synchronization or comparisons in the background. A log file is produced to record the output of these utilities. Upon completion, the <DataDirectory>\log\datapump_resync.log file contains a record of the operations that were performed and their success or failure status. The last line in the log file is always Done.
The DPCreateResyncDatafile utility creates the data file used by DPResync. The data file that is created, includes information such as table names, whether the table contains a time field and, if so, how many seconds of data should be processed at a time, and whether the table is periodically cleaned up. The data file can be modified to add optional where clause information, for example, custodyType = shared. This information allows the DPResync utility to optimize comparison and synchronization activities while reducing interference with normal operations, for example, minimizing database locks. The syntax is:
DPCreateResyncDatafile [-f <filename>] [-D <destinSystem>] [-o <order>] [-v] [-h]
Where the optional parameters are:
|
Parameter |
Description |
|---|---|
|
-f <filename> |
Creates the data file describing tables replicated from this source system. The files are created in the directory: <DataDirectory>\scripts\DatapumpDefaults to filename: DPResyncData_<SystemName>.txt |
|
-D <destinSystem> |
Creates a data file that only contains tables that are configured for replication from this source system to the destination system. This option also adds the destination system name to the default data filename. For example, if no filename parameter is specified but a destinSystem is specified, then the file created is: DPResyncData_<SystemName>_to_<destinSystem>.txt |
|
-o <order> |
If order = asc, order the file using priority ascending. If order = desc, order priority descending.(desc is used by deletion scripts.) Default: asc |
|
-v |
Prints progress messages. |
|
-h |
Display usage message |