Oracle eMail Server Administrator's Guide Release 5.2 A86653-01 |
|
Replication involves periodically copying domain information from an SCN or DCN to other nodes in the system or domain so that the nodes have access to the same information. Configuration information, such as routing information, is replicated from the SCN to all other nodes in the system. Directory information is replicated from a DCN to member nodes and the nodes subscribed to it.
Replication occurs automatically. You can use the following tasks described in this chapter to monitor and manage replication:
Check the status of the replicator process to monitor the transfer of directory and node information from the DCN to the nodes subscribed to it.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
|
REPLOG_TOO_BIG
test.
REPL_UNACKED
test. Also, check to make sure there are no problems with the network or the computers.
See Also:
REPLOG_TOO_BIG
and the REPL_UNACKED
monitor tests
The following sections are displayed when you check the replicator process status:
All domains listed in the Outbound Packages status section are domains for which this eMail Server node is the DCN.
Outbound package status can be either sent
or ack
(nowledged). Sent
indicates that the package was sent. Ack
indicates that the destination node has acknowledged receiving the package.
The Outbound Packages status section displays:
Domains listed in the Inbound Packages status section are domains to which the node subscribes.
Inbound package status can be either received
or executed
. Received
indicates this node has received the package. Executed
indicates that the changes contained in the package have been implemented.
The Inbound Packages status section displays:
You can manually replicate information to a node if the replicator process is not running or not accessible. For example, the network connection to a particular node could be down.
You have two choices for manual replication. You can:
You can replicate information to a single node if you only want the information to go to one node.
This task can only be performed through the OOMGR command-line interface.
IOFCMGR>replicate to node=<node_name
> class={<class_name
> | all};
See Also:
"Parameters for Replicating by Manually Sending a Replicator Package to a Node" for more information about the parameters available with this command |
IOFCMGR>replicate to node=intmsg2 class=person;
You can replicate node information with a file by replicating the information to a file, transferring the file to another node, and then replicating from the file you just transferred.
This task can only be performed through the OOMGR command-line interface.
IOFCMGR>replicate to file=<file_name
> class={<class_name
> | all};
IOFCMGR>replicate from file=<file_name
>;
See Also:
"Parameters for Replicating by Manually Transferring a File" for more information about the parameters available with this command |
You can reset the replicator package numbering to force the replicator process to accept a package that has a number that does not match the next expected package. For example, if a package was not delivered due to network problems, you might need to reset the package numbering to skip the package that cannot be delivered.
This task can only be performed through the OOMGR command-line interface.
IOFCMGR>reset replicator;
This command causes the replicator process to accept the next package sent, regardless of number. The replicator process resets its sequencing starting with the number of the first package it receives.
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|