Use sysadmin erssd with the defrag parameter
to recover any unused space, shrink the ERSSD size, and rebuild
the ERSSD database file.
When Replication Server deletes rows from the ERSSD, for example
when Replication Server deletes exceptions from the exception log,
the ERSSD database does not release the space back to the ERSSD
filesystem. Therefore, you must defragment the ERSSD database to recover disk space.
The defrag parameter
uses the dbunload SQL Anywhere command to rebuild the
ERSSD.
Before defragmenting the ERSSD:
- Verify you have sufficient disk space in your ERSSD as defragmentation requires
as much space as the original ERSSD for working space.
- Set your site version to 15.0 or later to allow you to use
the defrag parameter.
- Verify the
replication system is not busy.
Executing sysadmin erssd, defrag:
Shuts down eRSSD.
Shuts down dbltm, the ERSSD Replication
Agent, if dbltm is running.
Calls dbunload to rebuild and
defragment the ERSSD database file. dbunload saves
the old transaction log as erssdName.olg in
the transaction log directory.
Restarts ERSSD.
The dREC recovery daemon restarts the dbltm for
the ERSSD.
Note: During the defragmentation process, more files may be
generated in the transaction log directory. Do not delete these
files. Replication Server and dbltm will remove
the files when the files are not needed.