Difference between revisions of "Recitalreplication"

From Recital Documentation Wiki
Jump to: navigation, search
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The replication services are administrated with the recitalreplication command. It takes the following arguments.
+
The replication services are administrated with the '''recitalreplication''' command. It takes the following arguments.
 
+
'''Note:  recitalreplication must be run as root.  For systems with a hidden root account, please precede commands with ’sudo’.'''
+
  
 +
Note:  recitalreplication must be run as root.  For systems with a hidden root account, please precede commands with '''sudo'''.
  
 
==== help  ====
 
==== help  ====
 
Using the ''help'' or ''-h'' argument  will display a list of arguments for all the services.
 
Using the ''help'' or ''-h'' argument  will display a list of arguments for all the services.
  
<code lang="bash">
+
<pre>
 
  recitalreplication help
 
  recitalreplication help
</code>
+
</pre>
  
 
==== start ====
 
==== start ====
 
This argument is used to start the configured replication services on the system.  
 
This argument is used to start the configured replication services on the system.  
 
  
 
==== stop ====
 
==== stop ====
 
This argument is used to stop the configured replication services on the system.  
 
This argument is used to stop the configured replication services on the system.  
 
  
 
==== restart ====
 
==== restart ====
 
This argument is used to restart (stop, then start) the configured replication services on the system.  
 
This argument is used to restart (stop, then start) the configured replication services on the system.  
 
  
 
==== status ====
 
==== status ====
 
This argument is used to show the current status of the configured replication services on the system.  
 
This argument is used to show the current status of the configured replication services on the system.  
  
 +
==== fullstatus ====
 +
This argument is used to show the full status of the configured replication services on the system.
  
==== -d seconds ====
+
==== skip subscriber ====
Specify the delay in seconds between checking for new transactions. Specifying this argument on the command will overwrite the setting specified for [[DB_REPDELAY]] in the [[Configuration Files|recital.conf]] file.
+
Skip over the current transaction in the published subscriber queue.
 +
 
 +
==== clear subscriber ====
 +
Clear the current transactions in the published subscriber queue.
 +
 
 +
==== show ====
 +
Show the transaction details for the specified row number from the published queue, default is last transaction.
  
==== -i ====
+
==== add ====
Rebuild the subscriber index used for Peer to Peer replication.
+
Add a subscriber.
  
 +
==== del ====
 +
Delete a subscriber.
 +
 +
==== reset ====
 +
Reset the current transactions in the published subscriber queue.
 +
 +
==== -d seconds ====
 +
Specify the delay in seconds between checking for new transactions. Specifying this argument on the command line will overwrite the setting specified for [[DB_REPDELAY]] in the [[Configuration Files|recital.conf]] file.
  
 
==== -h ====
 
==== -h ====
 
List available command line options (this page).
 
List available command line options (this page).
 
  
 
==== -l ====
 
==== -l ====
Turn logging on. Specifying this argument on the command will overwrite the setting specified for [[DB_REPLOG]] in the dbservice.conf file.
+
Turn logging on. Specifying this argument on the command line will overwrite the setting specified for [[DB_REPLOG]] in the dbservice.conf file.
 
+
  
 
==== -p password ====
 
==== -p password ====
 
Specify a password for the server the publisher is running on. The password can also be specified in the data source.
 
Specify a password for the server the publisher is running on. The password can also be specified in the data source.
 
  
 
==== -r ====
 
==== -r ====
 
Reset the time stamp so all transactions in the queue are processed.
 
Reset the time stamp so all transactions in the queue are processed.
 
  
 
==== -u username ====
 
==== -u username ====

Latest revision as of 18:30, 24 June 2010

The replication services are administrated with the recitalreplication command. It takes the following arguments.

Note: recitalreplication must be run as root. For systems with a hidden root account, please precede commands with sudo.

help

Using the help or -h argument will display a list of arguments for all the services.

 recitalreplication help

start

This argument is used to start the configured replication services on the system.

stop

This argument is used to stop the configured replication services on the system.

restart

This argument is used to restart (stop, then start) the configured replication services on the system.

status

This argument is used to show the current status of the configured replication services on the system.

fullstatus

This argument is used to show the full status of the configured replication services on the system.

skip subscriber

Skip over the current transaction in the published subscriber queue.

clear subscriber

Clear the current transactions in the published subscriber queue.

show

Show the transaction details for the specified row number from the published queue, default is last transaction.

add

Add a subscriber.

del

Delete a subscriber.

reset

Reset the current transactions in the published subscriber queue.

-d seconds

Specify the delay in seconds between checking for new transactions. Specifying this argument on the command line will overwrite the setting specified for DB_REPDELAY in the recital.conf file.

-h

List available command line options (this page).

-l

Turn logging on. Specifying this argument on the command line will overwrite the setting specified for DB_REPLOG in the dbservice.conf file.

-p password

Specify a password for the server the publisher is running on. The password can also be specified in the data source.

-r

Reset the time stamp so all transactions in the queue are processed.

-u username

Specify a user name for the server the publisher is running on. The user name can also be specified in the data source.