>>-cdr error--+-------------------------+----------------------->
| (1) |
'-| Connect Option |------'
>--+------------------------------------+----------------------><
+- --seq=err_server:seqno------------+
+- --prune--"--+----------+--last--"-+
| '-first--,-' |
+- --zap-----------------------------+
| .-------------------. |
| V | |
'-----+- --follow-+---+--------------'
+- --all----+
'- --nomark-'
Notes:
- See page Connect Option.
| Element |
Purpose |
Restrictions |
Syntax |
| err_server |
Name of database server group that holds the error table |
The server must be registered for Enterprise Replication. |
Long Identifiers |
| first |
Start date for a range |
You must provide a valid date and time. |
Time of Day |
| last |
Ending date for range |
You must provide a later date and time than first. |
Time of Day |
| seqno |
Sequence number of a specific error |
You must provide the number of an error in the error table. |
Integer |
The
following table describes the options to cdr error:
| Long Form |
Short Form |
Meaning |
| (no options specified) |
|
Print the current list of errors and then mark them as reviewed. Enterprise Replication does not display errors marked as reviewed. |
| --all |
-a |
Print all errors, including those already reviewed. |
| --follow |
-f |
Continuously monitor the error table. |
| --nomark |
-n |
Do not mark errors as reviewed. |
| --prune |
-p |
Prune the error table to those times in the range from first to last. If first is omitted, then all errors earlier than last are removed. |
| --seq |
-s |
Remove the (single) error specified by server:seqno from the error table. |
| --zap |
-z |
Remove all errors from the error table. |
The cdr error command allows you to examine replication
errors on any replication server. Sometimes a command succeeds on the server
on which it is executed but fails on one of the remote servers. For example,
if you execute cdr define replicate on server1, but the table name is misspelled on server2, the command succeeds on server1 and appears to
have completed successfully. You can use cdr error -c server2 to see why replication is failing.
The cdr error command also allows you to administer
the cdr error table remotely. The reviewed flag lets
you watch for new errors while keeping the old errors in the table. For example,
you could run cdr error periodically and append the
output to a file.
The
following command displays the current list of errors on database server hill:
cdr error --connect=hill
After the errors are displayed, Enterprise Replication marks the errors
as reviewed.
The following command connects to the database server lake and removes from the error table all errors that occurred before
the time when the command was issued:
cdr error -c lake --zap
The following command deletes all errors from the error table that occurred
at or before 2:56 in the afternoon on May 1, 2000:
cdr error -p "2000-05-01 14:56:00"
The following command deletes all errors from the error table that occurred
at or after noon on May 1, 2000 and before or at 2:56 in the afternoon on
May 1, 2000:
cdr error -p "2000-05-01 14:56:00,2000-05-01 12:00:00"