4>>-cdr check replicate--+-------------------------+------------->
4                        |                    (1)  |
4                        '-| Connect Option |------'
4 
4>-- --master=data_server-- --repl=repl_name--------------------->
4 
4     .---------------.
4     V               |
4>--+---target_server-+-+--+------------+------------------------>
4   '- --all------------'  '- --verbose-'
4 
4>--+------------------------------------------------+----------><
4   '- --repair--+---------------------------------+-'
4                '- --extratargetrows=--+-delete-+-'
4                                       +-keep---+
4                                       '-merge--'
4 

4
1. See page Connect Option.
4

The following table describes the cdr check replicate options.

Use the cdr check replicate command to check the 4consistency of data between multiple database servers for a specific replicate. 4The cdr check replicate command compares all rows on 4all specified database servers against the data in the reference server and 4produces a consistency report. If you include the --verbose option, the report lists every inconsistent row; otherwise, the report 4summarizes inconsistent rows. If you include the --repair option, the cdr check replicate command repairs 4inconsistent rows so that they match the rows on the reference server. During 4a repair of inconsistent rows, the cdr check replicate command 4uses direct synchronization as a foreground process.

The cdr check replicate command requires that its 4associated user-defined routines are installed and registered in each 4database that is involved in the checking process. For instructions about 4installing and registering these routines, see Preparing the checksum 4Support Functions.

The following command generates a consistency report for a replicate named repl1, comparing the data on the server serv2 with the data on the server serv1:

cdr check replicate --master g_serv1 --repl=repl_1 g_serv2

The summary consistency report for the previous command might be:

------   Statistics for repl1 ------
4Node                  Rows     Extra   Missing  Mismatch Processed
4---------------- --------- --------- --------- --------- ---------
4g_serv1                 52         0         0         0         0
4g_serv2                 52         0         0         0         0

This report indicates that the replicate is consistent on these servers.

If the replicate has inconsistencies, the consistency report for the previous 4command might be:

------   Statistics for repl1 ------
4Node                  Rows     Extra   Missing  Mismatch Processed
4---------------- --------- --------- --------- --------- ---------
4g_serv1                 67         0         0         0         0
4g_serv2                 65         0         2         1         0
4
4WARNING: replicate is not in sync

This report indicates that the server g_serv2 is 4missing two rows and has one inconsistent row.

The following command generates a consistency report and repairs inconsistent 4rows on all servers for a replicate named repl1:

cdr check replicate --master g_serv1 --repl=repl_1 --all --repair

The consistency report for the previous command might be:

------   Statistics for repl1 ------
4Node                  Rows     Extra   Missing  Mismatch Processed
4---------------- --------- --------- --------- --------- ---------
4g_serv1                 67         0         0         0         3
4g_serv2                 65         0         2         1         0
4g_serv3                 67         0         0         0         0
4
4WARNING: replicate is not in sync

This report indicates that three rows were replicated from g_serv1 to g_serv2: two missing rows plus one inconsistent 4row.

If a target server has extra rows, the consistency report for the previous 4command might be:

------   Statistics for repl1 ------
4Node                  Rows     Extra   Missing  Mismatch Processed
4---------------- --------- --------- --------- --------- ---------
4g_serv1                 67         0         0         0         2
4g_serv2                 67         2         2         0         2
4g_serv3                 67         0         0         0         0
4
4WARNING: replicate is not in sync

This report indicates that g_serv2 has two extra 4rows and is missing two rows. Two rows were processed on g_serv1 to replicate the missing rows to g_serv2. 4Also, two rows were processed on g_serv2 to delete the 4extra rows. Because the --extratargetrows option is 4not specified, the default behavior of deleting rows on the target servers 4that are not on the reference server occurs.

The following table describes the columns of the consistency report.

The following command generates a verbose consistency report for a replicate 4named repl1:

cdr check replicate --master g_serv1 --repl=repl_1 g_serv2 --all --verbose

The verbose consistency report for the previous command might be:

------   Statistics for repl1 ------
4data mismatch between g_serv1 and g_serv2
4item_num:1
4order_num:1011
4--------------------------------------------------
4row missing on g_serv2
4item_num:1
4order_num:1014
4--------------------------------------------------
4row missing on g_serv2
4item_num:2
4order_num:1014
4--------------------------------------------------
4Node                  Rows     Extra   Missing  Mismatch Processed
4---------------- --------- --------- --------- --------- ---------
4g_serv1                 67         0         0         0         0
4g_serv2                 65         0         2         1         0
4
4WARNING: replicate is not in sync

This report indicates that there is one inconsistent row on g_serv2. The primary key for that row is the combination of the item_num column and the order_num column. The row 4that is inconsistent is the one that has the item number 1 and 4the order number 1011. There are two rows that are missing on g_serv2, each identified by its primary key values.

4
• cdr sync replicate