Diagnostics and Troubleshooting Software Delivery › Purging RAL Records from MDB

Purging RAL Records from MDB

To purge obsolete RAL records in MDB, invoke the RAL Purge command. This command works component-wise and purges the components listed in the command. It can also purge distribution and repository server details under the following conditions:

• When a distribution is empty after purging of components is complete
• When a repository server has no distributions after purging of distributions is complete.

For example, the Lenny distribution has two components, testing and main, which are extracted by the RAL engine task. To remove the records in the testing component, remove or disable synchronization engine tasks using DSM Explorer and invoke the purge command manually at the %RALHOME% folder as follows:

java -jar ral.jar -purge ftp://testing-i25361/debian/ lenny testing MASTER DEBIAN "Enterprise Debian Repository" 

This command has the following format:

java -jar ral.jar -purge -uri uri -distribution distribution -component component -type type -format format -name repository name -desc description -log log path

URI

Specifies the URI of the Debian repository server.

Example:

RAL.jar -purge –uri ftp://testing-i25361/debian/ -distribution lenny –component testing –type MASTER –format DEBIAN –desc "Enterprise Debian Repository"

Distribution

Specifies the distribution that contains the component that you want to delete. You can use this parameter only if the format is DEBIAN.

Component

Specifies the component that you want to delete. Use commas to separate multiple components.

Type

Specifies the type of the repository as Master repository or Mirror.

Format

Specifies the repository format.
Valid value: DEBIAN

Name

Specifies the repository server name of the component that you want to delete. The name must match the repository name in the Repositories configuration table.

Desc

(Optional) Specifies the repository description as entered in the Repositories configuration table.

Log

(Optional) Specifies the log file path. If you do no specify the path, a log file is created in <DSM Install Path>\logs folder. The log file for purge operation would be RAL_purge_log.log.

Important! Verify that no synchronization engine tasks run during the purge operation. Also, verify that no users browse or create wrapper packages during the purge operation.