Home | Previous Page | Next Page   Setting Up and Managing Enterprise Replication > Managing Replication Servers and Replicates > Resynchronizing Data Among Replication Servers > 4 4 4

Performing a Repair Job

4

Repair jobs are named background processes that synchronize two database 4servers for a specific replicate or replicate set.

4

Repair jobs can be 4run online while replication is active. First, you create the repair job using 4the cdr define repair command. Then, run the job using 4the cdr start repair command.

4

You can define a repair job for a single replicate or for a replicate set. 4When you repair a replicate set, Enterprise Replication synchronizes tables 4in an order that preserves referential integrity constraints (for example, 4child tables are synchronized after parent tables).

4

3During the execution of the repair process, lock contention 3is possible. The repair process performs dummy updates on a block of rows 3at a time, however, the whole table is not locked.4

4

3Transaction log consumption increases during a repair process 3due to operations on repair control tables as well as dummy updates on the 3user table.4

4 4
Important:
4
Running a repair job can consume a 4large amount of space in your log files. Ensure you have sufficient space 4before starting the repair job.
4

The following restrictions apply to running repair jobs:

4 4

If a repair job cannot repair a row, the inconsistent row is recorded in 4an ATS or RIS file. For more information, see Repairing Failed Transactions with ATS and RIS Files.

4 4

Filtering a Repair Job

4

If you have a situation where 4just part of the table needs to be repaired, for example when one fragment 4in a partitioned table has incorrect data, you can use the --filter (-f) option of the cdr 4define repair command. With the --filter option 4you specify a WHERE clause for the source participant and a WHERE clause for 4the target participant that restrict the columns for which the repair job 4runs.

4 4
Important:
4
In the WHERE clauses, only specify 4columns that are exactly the same on the source and target nodes and only 4specify columns that are not updated.
4 4

Stopping Repair Jobs

4

You can stop a repair job using the cdr stop repair command. You can restart from where it left off by running the cdr start repair command again. If you have defined a new repair job 4of the same name, the new job is started from the beginning. The old, partially 4run job is not started again.

4 4

Viewing Information About Repair Jobs

4

You can view information about 4repair jobs by using the cdr list repair command.

4 4

Deleting Repair Jobs

4

Repair job definitions are 4not automatically removed from the global catalog; delete them using the cdr delete repair command.

4 4
Warning:
4
If the repair job is active when you 4issue the cdr delete repair command, the repair data 4in the send queue of the source server is purged.
Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]