Step 3 In the Arguments field, enter desired arguments, as described in the Using section below.
Note: When entering arguments, the dbdiff command is already implied. Do not enter it in the
Arguments field.
Step 4 Specify the command duration time or accept the default (60 seconds). This is the amount of
time the command will attempt to run before terminating.
Step 5 If desired, check Elevate Command Priority. This ensures the command will run regardless of
the level of server activity.
Step 6 Click the Run button.

To Access DBDiff from a Command Line on a Node

From a command-line on an ICM node on which SQL Server is installed, you can access DBDiff
from any location on the drive on which ICM is installed. For example:
c:\>dbdiff
c:\temp>dbdiff

Using DBDiff

Syntax: dbdiff <database1.table@host1> <database2.table@host2>
You can also use the batch script diffconfig.bat to invoke DBDiff for various tables to
automatically compare two ICM databases.
Syntax: diffconfig <database1> <host1> <database2> <host2>
<database2.table@host2>
For example: diffconfig cust1_sideA geoxyzlgra cust1_sideB geoxyzlgrb
Command Line Options
Syntax: DBDiff {database a}.{table a}[@server a] {database b}.{table
b}[@server b] [/out:{file}] [/key:{pkey1,pkey2,...}] [/where:"{where
clause}"]
How to Use the DumpCfg Utility
Use the DumpCfg utility to analyze records in the ICM Config_Message_Log table to determine
what actions have been performed on an ICM system, when, by whom, and using what
applications.
For use with ICM Loggers only, but can be run from any ICM component.
Cisco Support Tools User Guide for Cisco Unified Software Release 2.1(1)
164
Chapter 13: - Using Cisco Common Tools
How to Use the DumpCfg Utility