ra_locator

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

Syntax

ra_locator [ { update | zero | move_truncpt } ]

Parameters

update – the optional keyword to request a new LTM Locator value from the primary Replication Server.
zero – The optional keyword to set the value of the LTM Locator stored in the Replication Agent transaction log to zero.
move_truncpt – The keyword that moves the truncation point.

Examples

Example 1 –

ra_locator

This command returns the current value of the LTM Locator maintained by 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 Replication Agent to all zeros.
Example 4 –
```
ra_locator move_truncpt
```
This command moves the transaction log truncation point to the end of the current transaction log.

Usage

When you invoke ra_locator with no option, it returns the current value of the LTM Locator maintained by the Replication Agent instance. For UDB, 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.

Note: The value of the LTM Locator that is maintained by Replication Agent is also known as the origin queue ID.
When you invoke ra_locator with the update keyword, it requests a new LTM Locator value from the primary Replication Server, and Replication Agent saves the value.

Note: When the you invoke ra_locator with the update keyword, the change takes effect only if the Replication Agent instance is in Replicating state.
When you invoke ra_locator with the zero keyword, it sets the value of the LTM Locator maintained by Replication Agent to zero.
The LTM Locator contains information that Replication Agent uses to determine where to start reading the transaction log.
Upon start-up or recovery from a connection failure, 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, 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, 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 section 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 the Admin or Replication Down state.
Without the zero keyword, the ra_locator command is valid when the Replication Agent instance is in the Admin, Replicating, or Replication Down state.
If you invoke ra_locator with the move_truncpt keyword, the truncation point is moved to the end of the log without change or modification to any Replication Agent components. (for Oracle, this is the end of the current online redo log.) The move_truncpt option has no effect if Replication Agent has not been initialized.

Note: To prevent Replication Server from requesting a log starting point that occurs earlier in the log than the location established by the move_truncpt option, Replication Server's LTM locator value for the primary connection must be zeroed. Execute the Replication Server System Database (RSSD) rs_zeroltm command against the primary database connection to zero the LTM locator.

If you move the secondary truncation point to the end of the primary database transaction log using ra_locator move_truncpt, you risk skipping over any DDL commands record in the log. The DDL commands might have been used by Replication Agent to update information stored within the Replication Agent System Database (RASD). If the RASD contents are incorrect due to skipping processing of some log records, you may force all of the schema information in the RASD to be refreshed using ra_admin refresh. If only the schema for a single object stored in the RASD is of concern, you can unmark and remark just that single object, which forces the schema of the object to be reread into the RASD.