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. Seamless Access Setup for Oracle R12 in Data Archive
  21. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  22. Using Multiple Engines in an ILM Environment
  23. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  24. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Normal Completion

Normal Completion

If the dropping or truncating of partitions is successful, the log shows the tables and partitions that were processed.
The following code shows an example of the log file:
30-Jun-2010 10:19:05CDT Calling staging api {call AA_PARTITION_PKG.drop_partition(?,?)} 30-Jun-2010 10:19:06CDT Dropping Partition ....: P20071101 for table ARC53_STAGING.SUBSRPTN_DIM_HIST 30-Jun-2010 10:19:06CDT Dropping Partition ....: P20071201 for table ARC53_STAGING.SUBSRPTN_DIM_HIST 30-Jun-2010 10:19:06CDT Dropping Partition ....: P20080101 for table ARC53_STAGING.SUBSRPTN_DIM_HIST 30-Jun-2010 10:19:06CDT Drop Partition Completed for Table ....: SUBSRPTN_DIM_HIST 30-Jun-2010 14:23:48CDT Calling staging api {call AA_PARTITION_PKG.truncate_partition(?,?)} 30-Jun-2010 14:24:35CDT Truncating Partition ....: P20071201 for table ARC53_STAGING.SUBSRPTN_DIM_HIST 30-Jun-2010 14:25:22CDT Truncating Partition ....: P20080101 for table ARC53_STAGING.SUBSRPTN_DIM_HIST 30-Jun-2010 14:25:22CDT Truncate Partition Completed for Table ....: SUBSRPTN_DIM_HIST
If there are no partitions to be dropped or truncated, the job completes successfully and there are no tables or partitions listed in the log.
The following code shows an example of the log file:
30-Jun-2010 11:31:18CDT Calling staging api {call AA_PARTITION_PKG.drop_partition(?,?)} 30-Jun-2010 11:31:18CDT Drop Partition Completed for Table ....: 30-Jun-2010 11:31:19CDT Calling staging api {call AA_PARTITION_PKG.truncate_partition(?,?)} 30-Jun-2010 11:31:19CDT Truncate Partition Completed for Table ....: