>>-cdr remaster--+-------------------------+-------------------->
                 |                    (1)  |
                 '-| Connect Option |------'
 
>-- --master=server--replicate--+----------+-------------------><
                                '-modifier-'
 

1. See page Connect Option.

The following table describes the option to cdr remaster.

Use the cdr remaster command to perform one of the following tasks:

• Convert a classic replicate to a master replicate. Master replicates ensure schema consistency among the participants in the replicates.
• Update the definition of a master replicate whose participant was changed in an alter operation. You can change the SELECT clause or the server from which to base the master replicate definition.
• The basereplicatename is the name of the replicate being remastered (up to 64 characters of this name are used).
• The localCDRID is the CDR group ID of the server you specified with the --connect option. You can obtain this ID using the onstat -g cat servers command or by looking in the SQLHOSTS file. Alternatively, you can query the syscdrserver view in the sysmaster database.
• The pid is the process ID of the client computer.

  An example of a shadow replicate name is:

  Shadow_4_Repl1_GMT1090373046_GID10_PID28836

To use the cdr remaster command, the master replicate definition must have been created with name verification turned on (--name option of the cdr define replicate command set to y).

As part of its processing, the cdr remaster command creates a shadow replicate. The shadow replicate is named as follows:

Shadow_4_basereplicatename_GMTtime_GIDlocalCDRID_PIDpid

The following example shows the original definition of the master replicate before the alter operation:

cdr define repl --master=delhi -C timestamp\
newrepl "test@delhi.tab" "select col1, col2 from tab"\

This example shows the cdr remaster command adding a new column, col3, in the newrepl participant:

cdr remaster --master=delhi newrepl\
"select col1, col2, col3 from tab"