000014239 - How to delete closed provisioning requests?

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014239
Applies ToSecurID Appliance 3.0.4
RSA Authentication Manager 7.1.SP4
IssueHow to delete closed provisioning requests?
ResolutionThe closed requests can be exported into a file and imported back into the database using a command line utility. The export function deletes the records. You can export closed requests if you want to free up disk space and to increase the  speed of search operations in the system. You can import archived requests to resend an approval e-mail to a user who has lost the approval e-mail that contained a token file.

Export Options

-D --delete (Optional) Deletes records after exporting.

-E --to Date Requests created on or before this date are exported [mm/dd/yyyy].

-S --from Date Requests created on or after this date are exported. [mm/dd/yyyy].

This utility exports the associated attributes and process instance data into a .zip file, Request_YYYY_MM_DD_HH_MIN_SEC.ZIP which contains the following files:
? Request Data - Request_YYYY_MM_DD_HH_MIN_SEC.CSV
? Request Attribute Data - Request_Att_YYYY_MM_DD_HH_MIN_SEC.CSV
? Process instance data - Request_WF_YYYY_MM_DD_HH_MIN_SEC.ZIP


? To export requests from 03/03/2007 to 03/07/2007 and delete the requests after exporting them, type:

   $cd utils

./rsautil archive-ucm-request -u jsmith -p steverest -m portersq -d C:\archivedRequest -a EXPORT -S 03/03/2007 -E 03/07/2007 -D

  The archived requests are saved in a .zip file.

? To import archived requests and the associated process instance data, type:

   $cd utils

   ./rsautil archive-ucm-request -u jsmith -p st5everest -m porter95sq -d C:\archivedRequest -a IMPORT -j Request_2007_03_06_15_48_26.zip

Legacy Article IDa58213