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

Create a New Default Segment

Create a New Default Segment

You can create a new default segment for a segmentation policy after the end of a specified time period. Create a new default segment when the data classification for the segmentation group contains only one dimension.
If the transactions in the default segment are primarily from the last time period, such as a year or quarter, and the default does not have a large number of active transactions, you can create a new default segment. When you create a new default segment, the ILM Engine creates the new default segment and renames the old default segment based on the time period of the transactions that it contains, for example 2013_Q2.
The ILM Engine moves active transactions and transactions that do not meet the business criteria of the renamed 2013_Q2 segment from the renamed segment to the new default segment. This method requires repeated row-level data movement of active transactions. Do not use this method if the default segment has many open transactions.
You can generate one new default segment at a time. Before you can generate another default segment, you must either delete or implement any existing generated default segments.
Before you run the job to create the new segment, you can configure the job steps. The following table lists each of the job steps to create a new default segment:
Step
Description
New segment internal task
Required. Internal task that prepares the job to run.
Preprocess business rules
Uses interim tables to preprocess the business rules you applied to the segmentation group. This step is visible only if you selected to use interim table processing in the Enterprise Data Manager.
Create new segments
Required. Creates the table spaces, grants required schema access, and creates the segments.
Incremental move policy segments to default
Estimates the size of tables in the segmentation group based on row count and determines how many datafiles to allocate to a particular tablespace.
Default is skip.
Collect segmentation group statistics
Collects database statistics, such as row count and size, for the segmentation group.
Drop interim tables
If you have enabled interim table processing to pre-process business rules, this step drops the interim tables.
Clean up after segmentation
Cleans up temporary objects, such as tables and indexes, that are no longer valid after segment creation.

0 COMMENTS

We’d like to hear from you!