To keep the RASD from growing indefinitely, you can periodically truncate older versions of its primary database object metadata.
Back up the RASD using rasd_backup before you
truncate it. See “Backing up the RASD”.
The RASD stores definitions for two types of database objects:
Articles – tables and stored procedures that are marked for replication
Users – database users who apply transactions in the primary database
Use the ra_truncatearticles, ra_truncateusers, and rasd_trunc_schedule commands to manage the size of the RASD. For information about these commands, see the Replication Agent Reference Manual.
You can truncate the RASD at any time, when the Mirror
Replication Agent instance is in any state.
Truncating older versions of articles in the RASD
Log in to the Mirror Replication Agent instance with the administrator login.
Use the following command to truncate articles in the RASD:
ra_truncatearticles NNN
Here, NNN is an LTM Locator value that identifies the oldest noncurrent version of any article to be kept.
All noncurrent versions of all articles that are less than the LTM Locator value you specify are truncated from the RASD. If the current (most recent) version of an article is older than the version identified by the LTM Locator value, it is not truncated.
Truncating older versions of users in the RASD
Log in to the Mirror Replication Agent instance with the administrator login.
Use the following command to truncate users in the RASD:
ra_truncateusers NNN
Here, NNN is an LTM Locator value that identifies the oldest noncurrent version of any user to be kept.
All noncurrent versions of all users that are less than the LTM Locator value you specify are truncated from the RASD. If the current (most recent) version of a user is older than the version identified by the LTM Locator value, it is not truncated.
