Identify and resolve data inconsistencies

-S <source service>

The source system.

Use the following format for the system name: [system:[RDBMS:]][userid/passwd@]service

Typically only the service name is specified, such as, the RTDB server name. For a full description of the options, execute the DPutil -h command.

-D <destination service>

The destination system.

The destination is specified in the same format as the source where the destination database is located in the same domain; for example, <system>\oasyshdb.

If the destination is located in a different domain, the Data Access Layer (DAL) driver, alias, and Remote Client Service (RCS) being used must also be specified.

For example: main:MSDAL:Dir=sub\\remote_RCS_XFER;Alias=Historical_XFER

Where main is the DPSystem and sub is the destination system in the untrusted domain.

-b <begin date>

The starting time and date of the data collection period you want to investigate or resolve.

The date must be entered in Greenwich Mean Time (GMT) format or as a time string in the "mm/dd/yyyy hh:mm:ss" format.

-B

Run the command in the background.

By default, the command runs in the foreground.

-e <end date>

The end time and date of the data collection period you want to investigate or resolve.

The date must be entered in Greenwich Mean Time (GMT) format or as a time string in the "mm/dd/yyyy hh:mm:ss" format.

If you do not specify the -e parameter, the command will use data up to the most recent entry.

-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.

-r <run time>

The time to start running the resynchronization. Valid values are between 0-59. For example, if your run time is 15 and your stop time is 20, the resynchronization will occur at 15-20 minutes after the top of hour (1:15-1:20, 2:15-2:20, etc.).

-s <stop time>

The time to stop running the resynchronization. Valid values are between 0-59. For example, if your run time is 15 and your stop time is 20, the resynchronization will occur at 15-20 minutes after the top of hour (1:15-1:20, 2:15-2:20, etc.).

-T

Run in test mode; do not actually execute against the source or destination.

-h

Display usage message that defines all the parameters for the DPResync commands.

-f <filename>

(Optional) The name of the resynchronization file to create. When not specified, the file is created in the directory: %DNADataRoot%\Historical\scripts\Datapump\DPResyncData_<SystemName>.txt.

-D <destination>

The destination Microsoft SQL Server connection; for example, backup\OASYSHDB.

-S <source>

The source Microsoft SQL Server connection; for example, main\OASYSHDB.

-s <DPSystem>

The name of the destination system configured in the Datapump table on the source system.

-o <order>

(Optional) If order = asc, order the file using priority ascending.
If order = desc, order priority descending. (desc is used by deletion scripts.)
The default is asc.

-A <archSvrName>

(Optional) The name of the server in the Archive Schedule table on the destination Microsoft SQL Server connection. The default value is Historical.

-h

(Optional) Display the usage message.