
This report checks entries in the file system of CM repositories running in DBFS or FSDB persistence mode. The results list entries that you can delete without risk.
You can set the scope when you start the report.
Scope tab
| Parameter | Description |
|---|---|
|
CM repository prefixes with persistence mode DBFS or FSDB |
Automatic listing of all prefixes of CM repositories running in DBFS or FSDB persistence mode. Select at least one entry. |
You can specify the following parameters for the report.
Parameters tab
| Parameter | Description |
|---|---|
|
Minimum Size: |
Minimum file size in bytes. To search for files of any size, choose -1. |
|
Minimum Age (Days): |
Age in days that orphaned files need to have in order to be found by the report. |
|
Collect Empty Folders: |
If this checkbox is activated, the report finds empty folders in DBFS mode. You can delete empty folders without risk. |
|
Collect Temporary Files: |
If this checkbox is activated, the report finds temporary files that the CM repository created beneath the root directory. Temporary files should normally be eradicated automatically by other means. If this does not happen, you can find temporary files using this report and delete them. |
|
Collect Content Files: |
If this checkbox is activated, the report finds orphaned entries in the file system with no connection to the database. |
|
Collect Alien Files: |
If this checkbox is activated, the report finds all files or folders beneath the root directory that were not created by a CM repository manager and therefore do not match the naming convention. |
When you display the results, you can use the Commands tab. You can delete objects found.
Commands tab
| Command | Description |
|---|---|
|
Remove |
Removes the selected objects from the file system permanently. |
The objects found are given an RID in the report. However, they do not represent resources. If you follow the link you receive an error message.
We recommend that you execute this report once a month. Execute the report several times in succession to make sure that all entries with errors have been found and eradicated.
More Information