...
| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
Resources & Remarks Modification History
|
| Excerpt |
|---|
Deletes all data belonging to a tenant from of the core system, including all objects in the repository, database, elasticsearchElasticsearch, audit entries and config files. |
...
This command may be useful if all data of a tenant should be deleted. Before using this command, you should ensure that the tenant is already disabled for user login, to prevent any unexpected data manipulations while the deletion process is running. Be careful, Please note that this operation cannot be undone and that there is no automatic data backup. Even objects under retention will be deleted. However, if binary content files are protected by an archive-internal retention, they cannot be deleted via this command.
While the command runs continuously runs, the deletion of DMS objects is stepwise performed step by step. Each day between the first object creation date and the current date is separately processed. Then again, each day is split in a variable number of time periods, such that the amount of objects to be deleted in each period is approximately equal to the number of fetch-size. For each period, the command follows this procedure:
- Processing of Process all current object versions:
- Deleting Delete each repository item, i.e., binary content files. (individual requests)
- Deleting Delete the objects in the Elasticsearch index. (batch request)
- Deleting Delete all database rows. (batch request)
- Processing of Process all old versions of DMS objects:
- Deleting Delete each repository item, i.e., binary content files. (individual requests)
- Deleting Delete all database rows. (batch request)
...
| Parameter | Argument Type | Description | Required | Default | Example |
|---|---|---|---|---|---|
--tenant <arg> | string | Tenant for which all data should be deleted. | yes | - | --tenant default |
| string | Target directory for result log. | no | - | --target-directory C:\Users\myusername\ymtenantdeletionlog |
--fetch-size <arg> | int | Fetch size, used to split days in time periods. Each period contains approximately as many elements as specified by The value must be at least 100 and not bigger than 1000010,000. | no | 1000 | --fetch-size 500 |
--what-if | boolean | Setting this flag will prevent the execution of the deletion. The process will be simulated in order to count all documents that would be deleted without this flag. | no | false | --what-if |
--skip-confirmation | boolean | Setting this flag will skip the initial warning , that all data is going to will be deleted. | no | false | --skip-confirmation |
...
In the following example, all objects of the tenant default will be deleted. Each day is split in time periods which contains contain approximately 500 objects.
...