Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Archive 6.5.1
  • All Products

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. Data Privacy
  18. Oracle E-Business Suite Retirement Reports
  19. JD Edwards Enterprise Retirement Reports
  20. Oracle PeopleSoft Applications Retirement Reports
  21. Language Settings
  22. Appendix A: Data Vault Datatype Conversion
  23. Appendix B: Special Characters in Data Vault
  24. Appendix C: SAP Application Retirement Supported HR Clusters
  25. Appendix D: Glossary

User Guide

User Guide

Back Next

Source

Source

Field
Description
Connection name
Source connection that you want to archive from. This field is mandatory.
Analyze Interim
Oracle sources only. Determines when the interim table is analyzed for table structure and data insertion.
  • After Insert. Analyzer runs after the interim table is populated.
  • After Insert and Update. Analyzer runs after the interim table is populated and updated.
  • After Update. Analyzer runs after the interim table is updated.
  • None. Analyzer does not run at all.
Default is After Insert and Update. To optimize performance for best results, use the default value.
Delete Commit Interval
Number of rows per thread that the archive job deletes before the job issues a commit to the database.
Default is 30,000. Performance is typically optimized within the range of 10,000 to 30,000. Performance may be impacted if you change the default value. The value you configure depends on several variables such as the number of rows to delete and the table sizes.
Use the following rules and guidelines when you configure the commit interval:
  • If you configure an Oracle source connection to use Oracle parallel DML for deletion, the archive job creates a staging table that contains the row IDs for each commit interval. The archive job truncates the table and reinserts rows for each commit interval. Populating the staging table multiple times can decrease performance. To increase performance, configure the commit interval to either zero or a very high amount, such as 1,000,000, to generate a single commit.
  • If you pause the archive job when the job deletes from Oracle sources, the commit interval affects the amount of time that the job takes to pause. The job pauses after all threads commit the active transaction.
  • As the commit interval decreases, the performance may decrease. The amount of messages that the job writes to the log increases. The amount of time that the archive job takes to pause decreases.
  • As the commit interval increases, performance may increase. The amount of messages that the job writes to the log decreases. The amount of time that the archive job takes to pause increases.
Insert Commit Interval
Number of database insert transactions after which a commit point should be created. Commit interval is applicable when the archive job uses JDBC for data movement.
If your source data contains the Decfloat data type, set the value to 1.
Delete Degree of Parallelism
Number of concurrent threads that are available for parallel deletion. The number of rows to delete for each table is equally distributed across the threads.
Default is 1.
Insert Degree of Parallelism
The number of concurrent threads for parallel insertions.
When the Oracle Degree of Parallelism for Insert is set to more than ‘1’, the java parallel insert of tables is not used.
Update Degree of Parallelism
The number of concurrent threads for parallel updates.
Reference Data Store Connection
Required when you use the history database as the source and you only want to purge from the history database.
Connection that contains the original source reference data for the records that you archived to the history database. The source includes reference data that may not exist in the history database. The archive job may need to access the reference data when the job purges from the history database.
0 COMMENTS
We’d like to hear from you!