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

Data Vault Restore to an Existing Production Database

Data Vault Restore to an Existing Production Database

When you restore data to an existing production database, you must determine whether the schema on the original production database has been updated since the data was archived.
If the production database schema has been updated, you must synchronize schemas between the existing database and the Data Vault. You can then run either a cycle or transaction restore.
When you restore archived data and the records exist in the target database, the restore job will fail if key target constraints are enabled. If target constraints are disabled, the operation might result in duplicate records.

0 COMMENTS

We’d like to hear from you!