Table of Contents

Search

  1. Preface
  2. Introduction
  3. Accessing Data Archive
  4. Working with Data Archive
  5. Scheduling Jobs
  6. Viewing the Dashboard
  7. Creating Data Archive Projects
  8. Salesforce Archiving
  9. SAP Application Retirement
  10. Creating Retirement Archive Projects
  11. Integrated Validation for Archive and Retirement Projects
  12. Retention Management
  13. External Attachments
  14. Data Archive Restore
  15. Data Discovery Portal
  16. Data Visualization
  17. Oracle E-Business Suite Retirement Reports
  18. JD Edwards Enterprise Retirement Reports
  19. Oracle PeopleSoft Applications Retirement Reports
  20. Smart Partitioning
  21. Smart Partitioning Data Classifications
  22. Smart Partitioning Segmentation Policies
  23. Smart Partitioning Access Policies
  24. Language Settings
  25. Appendix A: Data Vault Datatype Conversion
  26. Appendix B: Special Characters in Data Vault
  27. Appendix C: SAP Application Retirement Supported HR Clusters
  28. Appendix D: Glossary

Legal Hold

Legal Hold

You can put records from related entities on legal hold to ensure that records cannot be deleted or purged from the Data Vault. You can also put a database schema or an entire application on legal hold. A record, schema, or application can include more than one legal hold.
Records from related entities, when put on legal hold, are still available in Data Vault search results. Legal hold at the application or schema does not depend on the relationship between tables.
You can apply a legal hold at the schema level to one or more schemas within an archive folder. A schema might include an entity that contains tables that are also a part of a different schema. If you try to apply a legal hold on a schema that contains tables that have a relationship to another schema, you receive a warning message. The warning includes the name of the schema that contains the related tables.
You can continue to apply the legal hold on the selected schemas, or you can cancel to return to the selection page and add the schema that contains the related tables. If you do not include the schema that contains the related tables, orphan data is created in the related tables when you purge the tables that you placed on legal hold.
A legal hold overrides any retention policy. You cannot purge records on legal hold. However, you can still update the retention policy for records on legal hold. When you remove the legal hold, you can purge the records that expired while they were flagged on legal hold. After you remove the legal hold, run the Purge Expired Records job to delete the expired records from the Data Vault.
To apply a legal hold, you must have one of the following system-defined roles:
  • Administrator
  • Legal Hold User

0 COMMENTS

We’d like to hear from you!