Hi guys,
To delete a document held by Enhanced Retention Management, you must first release all Holds on that document. Fine.
You can release any hold using for example arsdoc hold_release. This includes removing an Implied Hold, using "-l IMPLIED_HOLD".
However, what if you accidentally remove the implied hold for the wrong document? How do you reset it properly?
arsdoc hold_add does not seem to accept "-l IMPLIED_HOLD":
2017-12-01 10:20:26.804052: ARS6822I Attempting login for userid 'odadmin' on server 'ARCHIVE' ...
2017-12-01 10:20:26.834828: ARS6080I Login successful
2017-12-01 10:20:26.834960: ARS6131I Searching for hold 'IMPLIED_HOLD' ...
2017-12-01 10:20:26.913433: ARS6085E Search unsuccessful
2017-12-01 10:20:26.913715: ARS6133E Unable to get hold information. The hold does not exist or the user does not have permission to access the hold.
2017-12-01 10:20:26.914632: ARS6026I arsdoc completed.
So. We don't want to export the entire batch and reload it again.
Can we "cheat" in a "half nice" way and run:
arsdoc update ... -i "<suitable SQL to find the document to update" -n Lockdown=<current value of Lockdown +16384>
?
Or how else do we restore the Implied Hold to the document?
(As far as I know, Implied Holds are only stored in the "Lockdown" field, as the value 16384, not in any other ARSHOLD* table. Let me know if this is wrong - if so, the suggested action above will obviously not work.)
I think the idea behind preventing you from re-applying an "implied hold" is that it shows that the load was modified. I'd suspect that the best way to re-apply the hold is to create a new one explaining that a document was deleted, and why.
-JD.