Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  21. Using Multiple Engines in an ILM Environment
  22. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  23. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Airline Ticket Example

Airline Ticket Example

You have multiple tables that contain information about airline tickets and you want to archive data for tickets that are older than one year.
You have the following tables that contain airline ticket information:
Table
Columns
TICKET_NUMBER
  • TICKET_NUMBER
  • ISSUE_DATE
  • CUST_ID
TICKET_COUPON
  • TICKET_NUBMER
  • COUPON
  • FROM_CITY
  • TO_CITY
TICKET_COUPON_SAVE
  • TICKET_NUMBER
  • COUPON
  • IS_USED
TICKET_PARTITION
  • TICKET_NUMBER
  • ISSUE_DATE
  • PASSENGER_NAME
TICKET_PARTITION_TARGET
  • TICKET_NUMBER
  • PASSENGER_NAME
  • ID_NUM
TICKET_SAVE
  • TICKET_NUMBER
  • ISSUE_DATE
  • CREDITCARD
Each table has a TICKET_NUMBER column. You use the TICKET_NUMBER columns as foreign keys to relate the tables to the driving table and create an entity. You use the TICKET_NUMBER table as the driving table because it has the ISSUE_DATE column. After you create the entity, you use the ISSUE_DATE column to determine which ticket numbers are older than one year, and you archive the rows in each table that have the old ticket numbers.
To create an entity that contains all the tables with airline ticket information, you use Enterprise Data Manager to find table relationships that you can use as foreign keys. The foreign key relationships that you select determine how Enterprise Data Manager forms the entity.