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

Split the Default Segment

Split the Default Segment

If the default segment contains more than one time period of data, you can split the default segment.
If you have a large amount of data in the default segment that spans more than one time period, use the split default segment method. The split default segment method creates multiple new segments from the default segment and moves the transactions from the default segment into the appropriate segment for each time period.
For example, the default segment contains data from three quarters, including the current quarter. The split default method creates three new segments, one for each of the two quarters that have ended, plus a new default segment. The ILM Engine moves closed transactions to the new segment for the quarter in which they belong. Then the ILM Engine moves new and active transactions to the new default segment.
The split default method of segment creation works with both single and multidimensional data classifications. This method is ideal when the application environment has complex business rules with long transaction life cycles.
To split the default segment, the application database must be offline.
If the policy contains multiple segments in a Generated state and you want to delete one of the segments, you must delete the most recently generated segment first.
Before you run the job to split the default segment, you can configure the job steps. The following table lists each of the job steps to split the default segment:
Step
Description
New segment internal task
Required. Internal task that prepares the job to run.
Create audit snapshot - before
Creates a snapshot of the state of the objects, such as indexes and triggers, that belong to the segmentation group before the ILM Engine moves any data.
Create optimization indexes
Creates optimization indexes to improve smart partitioning performance. Indexes are used during the segment data step to generate the selection statements that create segments. This step is applicable only if you have defined optimization indexes in the Enterprise Data Manager.
Disable access policy
Disables the access policy on the default segment.
Create new segments
Required. Creates the table spaces, grants required schema access, and creates the segments.
Split single segment to multi segments
Required. Moves data to the new segment.
Drop optimization indexes
Drops any optimization indexes you created in the Enterprise Data Manager.
Create audit snapshot - after
Creates a snapshot of the state of the objects, such as indexes and triggers, that belong to the segmentation group after the ILM Engine moves the data into the segments.
Compare audit snapshots - summary
Compares and summarizes the before and after audit snapshots.
Compile invalid objects
Compiles any not valid objects, such as stored procedures and views, that remain after the ILM Engine creates segments.
Enable access policy
Enables the access policies you applied to the segmentation group.
Collect segmentation group statistics
Collects database statistics, such as row count and size, for the segmentation group.
Clean up after segmentation
Cleans up temporary objects, such as tables and indexes, that are no longer valid after segment creation.

Back to Top

0 COMMENTS

We’d like to hear from you!