startdbpurge
Use the startdbpurge command
to create a database purge task to be run as a non-interactive task at a later
time, using the IBM Director scheduler.
Syntax

>>-perfcli-- --startdbpurge-- ---devtype--+-ess-+-- ---quiet---->
+-svc-+
'-all-'
>--+---------------+-- --+----------------------+-- ------------>
+--days--days---+ '--rmexceptinfo--+-y-+-'
'--years--years-' '-n-'
>--task_name---------------------------------------------------><
Parameters
- -devtype ess | svc | all
- An optional parameter that clears data for only the device type specified.
- -quiet
- An optional parameter that turns off the confirmation prompt for this
command.
- -days days | -years years
- Specifies the number of days or years for which the performance data
will be purged. Valid values for days are from 1 to
365 days. Valid values for years are from 1 to 10
years. If this flag is not specified, performance data for 365 days will be
purged. You should specify either the -days or the -years flag.
- -rmexceptinfo y | n
- An optional parameter that specifies whether exception data is to be
purged. Specify y to purge the data; specify n if you do not want the data purged.
- task_name
- Assigns a user-defined task name for the database purge task. The task
name must be unique and cannot be the same as another existing Director task
name.
Description
You can use the startdbpurge command to create a
database purge task to be run as a non-interactive task at a later time, using
the IBM Director scheduler.
Return values
- Database purge task task_name successfully started.
Possible failures
- Task task_name already exists.
Examples
An invocation example:
perfcli startdbpurge -devtype ess -perfinfo 5 -unit days mypurgetask
The resulting output:
Are you sure you want to purge the database since this is an irrecoverable operation
that could be a long-running task and impact concurrent operations? y/n
y
Database purge task mypurgetask successfully started.