The Disposition Sweep for an Auto Destroy action immediately
deletes those records marked for Auto Destroy.
About this task
Attention: When running a disposition sweep for
an Auto Destroy action on a multi-filed record, the record is unfiled
from the container targeted by the sweep. However, the record remains
in other containers not associated with the sweep.
In order
for this type of sweep to complete successfully, you must first tag
records with an Auto Destroy action. For more information, see the
adding an action topic. You must also update the old disposition schedule
to use Auto Destroy by changing the Phase properties. For more information,
see the modifying a disposition schedule topic. There is also a special
command for running disposition sweep for and Auto Destroy action
if you have multiple profiles. Profiles allow you to save different
configurations and run sweep using these configurations without the
need to reconfigure them.
What to do next
Checking the log file
After Disposition Sweep runs, check
the activity log you configured. The log file shows when various types
of processes start and end and lists entities processed and updated.
If there are errors, a trace is included. What is not included though
is a list of records that failed, since Content Platform Engine is unable to supply
the information.
By default, disposition Sweep
for Auto Destroy generates a transcript file with the profile name,
the name "AutoDestroy," and date and time to run Auto Destroy. If
no profile is provided when running an Auto Destroy, the transcript
file uses “DefaultProfile” as the prefix. For example, if you run
RecordsManagerSweep.bat
-DispositionSweep -autodelete on 12/03/2011 at 14:13:30,
then
DefaultProfile_AutoDestroy_2011_12_3_14_13_30.log will
be found in the
RecordsManagerSweep folder.
If you run
RecordsManagerSweep.bat -DispositionSweep –autodelete
–profile Profile1 on 12/03/2011 at 14:13:30, then
Profile1_AutoDestroy_2011_12_3_14_13_30.log will
be generated. This log file shows the following information:
- The time, the entity type (record or container) and ID.
- If the entity deletion succeeded or failed along with the reason
for the failure if the deletion failed.
Running Disposition Sweep with
-autodelete and
generating the log file can cause some performance degradation. If
you do not want the Auto Destroy log, you can run the following command
which runs Disposition Sweep without generating a log file. There
is also a special command which runs disposition sweep without generation
a log file if you have multiple profiles.
Operating system |
Command |
AIX, HP-UX, Linux, and Solaris |
./RecordsManagerSweep.sh -DispositionSweep -autodelete -notranscript [-profile
"profile name"] |
Windows |
./RecordsManagerSweep.bat -DispositionSweep -autodelete -notranscript [-profile
"profile name"] |