cdr modify replicate

The cdr modify replicate command modifies replicate attributes.

Syntax


1  cdr modify replicate?  %Connect Option  (1)?  --name=n
1+ 
1  %Conflict Options  (2)
1  %Scope Options  (3)
1  %Frequency Options  (4)
1  %Special Options  (5)
2  replicate
2? +  participant
Notes:
Element Purpose Restrictions Syntax
participant Name of a participant in the replication. The participant must be a member of the replicate. Participant and participant modifier
replicate Name of the replicate to modify. The replicate name must exist. Long Identifiers

The following table describes the option to cdr modify replicate.

Long Form Short Form Meaning
--name=n -n n Removes the name verification attribute from a master replicate.

Special Options

Special Options

1+ 
1   --ats
2.1 y
2.1 n
1   --ris
2.1 y
2.1 n
1   --firetrigger
2.1 y
2.1 n
1   --fullrow
2.1 y
2.1 n
1  --ignoredel=
2.1 y
2.1! n
1  
--serial
1  --UTF8=
2.1 y
2.1! n
1  --alwaysRepLOBs=
2.1 y
2.1! n
1  --cascaderepl=
2.1 y
2.1 n
Table 1. Special options for cdr modify replicate.
Long Form Short Form Meaning
--alwaysRepLOBS= Specifies whether columns that contain unchanged large objects are included in replicated rows:
  • --alwaysRepLOBS=n: Default. Columns that contain unchanged large objects are not replicated.
  • --alwaysRepLOBS=y: Columns that contain large objects are always included in replicated rows.
--ats y or --ats n -A y or -A n Activates (y) or deactivates (n) aborted-transaction spooling for replicate transactions that fail to be applied to the target database.
--cascaderepl None Enables replication of data arriving through ER. With traditional ER, data replicated by ER is not eligible for further replication. A cascade replicate, however, would also pick up data modifications arriving through ER, or otherwise caused by ER, e.g. as a result of a trigger action. Valid values are:
  • --cascaderepl=y=Enables cascaded replication.
  • --cascaderepl=n=No cascaded replication.

e.g.

Consider ER set up on three servers A and B + C, table X being present on all of them. Replicate R1 is defined to replicate data modifications from A to B, and another replicate R2 is defined to replicate modifications from B to C.

In a traditional ER setup, i.e. without --cascaderepl option,
  • application changes on A would be replicated to B through R1
  • app changes on B would be replicated to C through R2
  • those changes on A would NOT be replicated to C through R2 - because what arrives through ER is not eligible for ER

A cascade replicate created by adding --cascaderepl, would pick data arriving via ER also.

To avoid circular replication, among the participants of a cascade replicate only one can be in sending mode (Primary or Send-Only).
--firetrigger y or --firetrigger n -T y or -T n Causes the rows that are inserted by the replicate to fire (y) or not fire (n) triggers at the destination.
--fullrow y or --fullrow n -f y or -f n Specifies to (y) replicate the full row and enable upserts or (n) replicate only changed columns and disable upserts.
--ignoredel= -D Specifies whether to retain deleted rows on other nodes:
  • --ignoredel=y = Indicates that rows are retained if they are deleted on other nodes in the Enterprise Replication domain. You cannot use this option if you specify deletewins as the conflict resolution rule.
  • --ignoredel=n = Default. Indicates that deleted rows are deleted on all nodes in the Enterprise Replication domain.
--ris y or --ris n -R y or -R n Activates (y) or deactivates (n) row-information spooling for replicate row data that fails conflict resolution or encounters replication-order problems.
--serial -s Specifies that replicated transactions for the replicate are applied serially instead of in parallel.
--UTF8= Specifies whether to enable conversion to and from UTF-8 (Unicode) when you replicate data between servers that use different code sets.
  • --UTF8=y Default. Indicates that character columns are converted to UTF-8 when the row is copied into the transmission queue. When the replicated row is applied on the target server, the data is converted from UTF-8 to the code set used on the target server. No attempt is made to convert character data that is contained within opaque data types. You cannot use --UTF8=y for replicates that contain TimeSeries data types, user-defined data types, or module data types.
  • UTF8=n Indicates that code set conversion is ignored.

Usage

The cdr modify replicate command modifies the attributes of a replicate or of one or more participants in the replicate. You can also change the mode of a participant. If the command does not specify participants, the changes apply to all participants in the replicate.

To add or delete a participant, use the cdr change replicate command.

If you change the conflict resolution rule with cdr modify replicate, you must also specify the scope with the --scope option, even if you are not changing the scope.

The attributes for cdr modify replicate are the same as the attributes for cdr define replicate, with the following exceptions:
  • You cannot change the machine-independent decimal representation (--floatcanon) or IEEE floating point (--floatieee) formats.
  • You cannot change the conflict resolution from ignore to a non-ignore option (time stamp, SPL routine, or time stamp and SPL routine). You cannot change a non-ignore conflict resolution option to ignore.

    However, you can change from time stamp resolution to SPL routine resolution or from SPL routine resolution to time stamp.

  • The --ats, --ris, --firetrigger, and --fullrow options require a yes (y) or no (n) argument.

When you run the cdr modify replicate command, an event alarm with a class ID of 63 is generated, if that event alarm is enabled.

You can run this command from within an SQL statement by using the SQL administration API.

Examples

The following example modifies the frequency attributes of replicate smile to replicate every five hours: 
cdr modify repl --every=300 smile
The following example modifies the frequency attributes of replicate smile to replicate daily at 1:00 A.M.: 
cdr modify repl -a 01:00 smile
The following example modifies the frequency attributes of replicate smile to replicate on the last day of every month at 5:00 A.M., to generate ATS files, and not to fire triggers: 
cdr modify repl -a L.5:00 -A y -T n smile
The following example changes the mode of the first participant that is listed to receive-only and the mode of the second to primary: 
cdr mod repl smile R db1@server1:antonio.table1 \
                   P db2@server2:carlo.table2