ra_locator

Description

Returns the current value of the LTM Locator maintained by the Replication Agent, requests an LTM Locator value from the primary Replication Server, or sets the value of the LTM Locator maintained by the Replication Agent to zero.

Syntax

ra_locator [update|zero]

Parameters

Examples

Example 1

ra_locator

This command returns the current value of the LTM Locator maintained by the Replication Agent, as shown:

Locator
 ---------------------------------------------------
 000000005200000000000000527FFFFFFFFFFFFFFF0022FB3B
 (1 row affected)

Example 2

ra_locator update

This command requests a new LTM Locator value from the primary Replication Server.

Example 3

ra_locator zero

This command sets the value of the LTM Locator maintained by the Replication Agent to all zeros.

Usage

• When ra_locator is invoked with no option, it returns the current value of the LTM Locator maintained by the Replication Agent instance. For UDB, the Replication Agent stores the value of the LTM Locator in a table in the primary database; for Oracle and Microsoft SQL Server this value is stored in the RASD.

  The value of the LTM Locator that is maintained by the Replication Agent is also known as the origin queue ID.

• When ra_locator is invoked with the update keyword, it requests a new LTM Locator value from the primary Replication Server, and the Replication Agent saves the value.

  When the ra_locator command is invoked with the update keyword, the change takes effect only if the Replication Agent instance is in Replicating state.

• When ra_locator is invoked with the zero keyword, it sets the value of the LTM Locator maintained by the Replication Agent to zero.

• The LTM Locator contains information that the Replication Agent uses to determine where to start reading the transaction log.

  Upon start-up or recovery from a connection failure, the Replication Agent automatically requests an LTM Locator value from the primary Replication Server.

  • If the value of the LTM Locator returned from the primary Replication Server is zero, then Replication Agent uses the LTM Locator value stored in the transaction log system table.

  • If the value of the LTM Locator in the transaction log system table is zero, then Replication Agent starts reading the transaction log from either the current beginning of the log, or from the end of the log for UDB.

• For more information about the format of the origin queue ID, see the chapter for your specific primary data server in the Replication Agent Primary Database Guide.

• If the Replication Agent transaction log does not exist, the ra_locator command returns an error message.

• The ra_locator command with the zero keyword is valid only when the Replication Agent instance is in Admin state.

• Without the zero keyword, the ra_locator command is valid when the Replication Agent instance is in either Admin or Replicating state.

See also