DSRUTIL utility
Once you have initially set up, enabled, and started Fathom Replication, you can use the DSRUTIL Utility to perform specific Fathom Replication server, Fathom Replication agent, source, and target database requests. The syntax for this utility is as follows:
database
Database is the name of the database to perform the action on. The name of the database must be the first argument or it must be preceded with -db. The database must be a valid name.
-db
database
The name of the database to perform the action on. When the database name is specified after the -db
argument, the -db
database
argument group can appear anywhere on the command line.
-C
ACTION
The -C argument is used to specify the action to be performed on the database. Details of specific actions and their modifiers are described in Table 3–4.
Server
| Agent
The action will be performed on the Fathom Replication server or the Fathom Replication agent.
name
The name of the Fathom Replication agent to perform the action on. Each Fathom Replication server maintains a list of named Fathom Replication agents that it is communicating with. The agent name must be valid.
ALL
The action will be performed on all Fathom Replication agents.
Table 3–4 shows the possible DSRUTIL utility command actions and their modifiers.
Table 3–4: DSRUTIL command actions and modifiers
Command
action
|
Modifier
|
Description
|
|
|
Allows you to apply AI extents generated by the source directly to the target database. This is useful when there is a source failure and there are AI blocks in transit between the server and agents.
Requirements for using this feature:
- Agent must be in pre-transition state.
- The
transition property must be set to manual .
- Source must save AI extents to remote storage that is accessible to the target’s agent.
You can determine which extent to apply by using DSRUTIL target -C RECOVERY Agent .
|
|
|
The Fathom Replication server stops attempting to reconnect. This action is only applicable if the defer-agent-startup property was set to a valid non-zero time that has not yet expired.
The advantage of this command is that if you have connected to one of your required agents and you do not want to wait for the second, non-critical agent to connect, normal replication processing will begin and connection retries will stop.
The Fathom Replication agent that is connected and the Fathom Replication server will go through startup synchronization. Once complete, normal replication activity will continue.
|
|
|
Allows you to disable Fathom Replication while the source database is online. Before Fathom Replication is disabled, the server is terminated.
When the database is up and running but the Replication server and agent are not, for example after a crash or termination, this command makes the specified database a normal Progress database. This command only works when the database is up. If it is a target database, this command does not disable ERO mode. To change this, you must shut down and restart the database.
If the agent is still running, this command will terminate the agent before disabling Fathom Replication.
|
|
|
Displays a PROMON-type series of screens that display the current state of replication. This is a useful command to see what activities are taking place while Fathom Replication is running.
|
|
|
Displays the replication recovery information.
|
|
|
This is useful if the server ended, and the Progress database is waiting for Fathom Replication server action. For example, the Replication server is waiting for synchronous transaction acknowledgements, RELWAITS frees up any pending waits that might be outstanding so that database activity can continue.
|
|
|
The Fathom Replication server is restarted. The action will not be performed if the Fathom Replication server is currently running. The advantage to using this command is that you do not have to restart your database.
|
|
|
The Fathom Replication server starts one or both of its configured agents. The advantage of this command is that you do not have to restart your server.
The database must be a valid source database that is online.
The Fathom Replication server must be running.
If the name of the agent, or ALL of the agents specified are currently active, an error will be returned.
If the restart fails, an error will be returned.
Success will be returned on successful completion.
|
|
|
Terminates the currently running Fathom Replication server or agent.
The advantage to using this command is that the database stays up and running, where PROSHUT would shut the database down.
|
|
|
Instructs a Fathom Replication agent to transition this target database to normal Progress database. This command can be used to force a transition when the server is in contact with the agent or if the server and agent have lost connection and you want to perform a manual transition.
|
|
|
Forces the target database to go into a pre-transition state.
|