Accommodating the RASD

Each Mirror Replication Agent instance uses an embedded SQL Anywhere® database to manage its Mirror Replication Agent System Database (RASD).

Because the RASD stores information about primary database structure or schema objects, its size depends partly on the number of tables and procedures replicated, and the number of database users in the primary database.

When it replicates a data definition language (DDL) transaction, the Mirror Replication Agent creates a new version of the affected object’s metadata in its RASD. Over time, the size of the RASD can grow significantly, depending on the number and frequency of DDL transactions replicated.

If the RASD runs out of disk space, the Mirror Replication Agent shuts down and suspends replication. To prevent this, provide adequate disk space on the Mirror Replication Agent host machine to accommodate the initial size of the RASD, as well as some potential growth.

See the Mirror Activator Administration Guide for more information about the RASD.