Replication Agent System Database (RASD) Management

Replication Agent for Oracle and Replication Agent for Microsoft SQL Server use an embedded database, managed by SQL Anywhere, for the RASD.

• RASD
  Each instance of Replication Agent for Oracle or Replication Agent for Microsoft SQL Server depends on the information in its RASD to recognize database structure or schema objects in the transaction log.
• Updating the RASD
  The RASD is usually updated automatically during normal replication activity.
• Updating the Log Device Repository
  Replication Agent stores information about primary log devices in its RASD when you initialize the Replication Agent instance. Log device information in the RASD is referred to as the log device repository.
• Backing Up the RASD
  As with any database, you should periodically back up the RASD to prevent data loss in the event of a device failure. Each backup is saved in a separate directory, the name of which consists of the date and time the backup occurred. The most recent backup is also stored in the backup directory in addition to its own dated directory.
• Restoring the RASD
  If the RASD becomes corrupt (for example, because of a device failure), you can restore the database from the most recent backup files.
• RASD Truncation
  To keep the RASD from growing indefinitely, you can periodically truncate older versions of its primary database object metadata.
• Default Host and Port Number Configuration
  The RASD, an embedded SQL Anywhere database, starts when the Replication Agent starts. By default, the SQL Anywhere host value is localhost, and the SQL Anywhere port number is the Replication Agent port number +1.