Preface
Installation Overview
- Introduction
- Data Archive Installation
- Data Vault Installation
- Component Selection
- Application Accelerator Installation
- Dynamic Data Masking Installation
  - Enabling Dynamic Data Masking
Before You Install
- License Key
- X Window Server
- Data Archive Requirements for the ILM Repository
  - ILM Repository User
- Data Archive Requirements for the ILM Engine
- Data Vault Requirements
Data Archive Installation
- Data Archive Installation Overview
  - Installation Package
- Installing Data Archive Components
- Graphical Mode Installation
- Console Mode Installation
- Silent Mode Installation
  - Silent Mode Installation Properties
  - Installing in Silent Mode
- Informatica Data Archive Profiling Installation
Data Vault Installation
- Data Vault Installation Overview
- Graphical Mode Installation
- Console Mode Installation
- Silent Mode Installation
  - Step 1. Create the Properties File
  - Step 2. Run the Silent Installer
Application Accelerator Installation
- Application Accelerator Installation Overview
- Installing the Application Accelerators in Graphical Mode
- Installing the Application Accelerators in Console Mode
Application Retirement for Healthcare Accelerator Installation
- Application Retirement for Healthcare Accelerator Installation Overview
- Prerequisites
- Installing the Accelerator in Graphical Mode
- Installing the Accelerator in Console Mode
- After You Install
Salesforce Accelerator Installation
- Salesforce Accelerator Installation Overview
- Installing the Accelerator in Graphical Mode
- Installing the Accelerator in Console Mode
- After You Install
After You Install
- Client Machine Requirements
- Starting the ILM Application Server
  - Logging In to Data Archive
- Starting the Data Vault Components
- Configuring Memory Settings on a 64-bit Computer
- Configuring Embedded Tomcat for HTTPS
- Registering Services as Windows Services
  - Registering the Archive Service
  - Registering the Data Vault Service for External Attachments
- Configuring Data Archive
- Setting up SAP Retirement
Data Archive Upgrade
- Data Archive Upgrade Overview
- Before You Upgrade
- Upgrading Data Archive in Graphical Mode
- Upgrading Data Archive in Console Mode
- Upgrading Data Archive in Silent Mode
- After You Upgrade Data Archive
- Reverting to a Previous Version
Data Vault Upgrade
- Data Vault Upgrade Overview
- Before You Upgrade a Data Vault Component
- Upgrading in Graphical Mode
- Upgrading in Console Mode
- Upgrading in Silent Mode
  - Step 1. Create the Properties File
  - Step 2. Run the Silent Installer
- Troubleshooting Data Vault Upgrade
- After You Upgrade
- Reverting an Upgrade
Upgrading Oracle History Data
- Upgrading Oracle History Data Overview
- Upgrading Oracle History Data Prerequisites
- Steps to Upgrade the History Data
- Step 1. Run the History Upgrade Scripts
  - History Upgrade Scripts Parameters
  - Running the History Upgrade Scripts
- Step 2. Run the Create History Table Job with the Original Source
  - Running the Create History Table Job
- Step 3. Update the Application Version for Source and Target Connections
  - Updating the Application Version for Source and Target Connections
- Step 4. Run the Create History Table Job with the Updated Source
  - Running the Create History Table Job
- Step 5. Run the Seamless Data Access Job for the Updated Source
  - Running the Seamless Data Access Job
- Step 6. Run the Create Indexes Job
  - Running the Create Indexes Job
- Step 7. Gather Database Statistics
Upgrading PeopleSoft History Data
- Upgrading PeopleSoft History Data Overview
- Upgrading PeopleSoft History Data Prerequisites
- Steps to Upgrade the History Data
- Step 1. Run the History Upgrade Scripts
  - Running the History Upgrade Scripts
    - Original Application Changes Script Example
    - Updated Application Changes Script Example
- Step 2. Run the Create History Table Job with the Original Source
  - Running the Create History Table Job
- Step 3. Update the Application Version for Source and Target Connections
  - Updating the Application Version for Source and Target Connections
- Step 4. Run the Create History Table Job with the Updated Source
  - Running the Create History Table Job
- Step 5. Run the Seamless Data Access Job for the Updated Source
  - Running the Seamless Data Access Job
- Step 6. Run the Create Indexes Job
  - Running the Create Indexes Job
- Step 7. Gather Database Statistics
ILM Data Validation Option Setup
- ILM Data Validation Option Setup Overview
- Before You Set Up the ILM Data Validation Option
- Install the Data Vault Service ODBC Driver
  - Installing the Data Vault ODBC Driver in Graphical Mode
  - Installing the Data Vault ODBC Driver in Console Mode
- Create a Data Vault Service ODBC Data Source
  - Creating an ODBC Data Source on Windows
    - Using the Windows ODBC Data Source Administrator to Create a Data Source
    - Data Vault ODBC Data Source Parameters
  - Creating an ODBC Data Source on UNIX
- Create a PowerCenter Connection Object
- After You Set Up the ILM Data Validation Option
Data Archive Source and Target Database Requirements
- Source Database Requirements
- Target Database Requirements
Data Archive Connectivity
- Data Archive Connectivity Overview
- Native Connectivity
- DataDirect Connect JDBC Connectivity
- PowerExchange Connectivity
- Third-Party JDBC Connectivity
Data Archive Uninstallation
- Data Archive Uninstallation Overview
- Restore Archived Data
- Dropping Database Users and Links
- Dropping the ILM Repository
- Deleting the ILM Application Server Directory
- Uninstalling the Data Vault
- Uninstalling Source Adapters
- Deleting Remaining ILM Files
SAP Application Retirement
- SAP Application Retirement Overview
- SAP Application Retirement Architecture Options
- Setting Up SAP Application Retirement
- Step 1. Install the SAP Java Connector
- Step 2. Apply the SAP Transports
- Step 3. Assign Roles
- Step 4. Configure Conf.Properties
- Step 5: Set up the FTP or NFS Connection
  - Creating the FTP Connection
  - Creating the NFS Mount
Database Users and Privileges
- Database Users and Privileges Overview
- Administration User
- Production Application User
- Staging User
- History Read-Only User
- History Application User
- Combined User and Archive User for Seamless Access
- System User (Smart Partitioning)
- IBM DB2 Privileges
  - Bind Packages Privileges
  - Login User Privileges
- SAP Application Retirement Privileges
  - ZINFA_RETIREMENT_PREPARATION Role
Data Visualization Designer Installation
- Data Visualization Designer System Requirements
- Installing Data Visualization Designer
Data Archive Installation Requirements Checklist and Architecture Options
- Pre-Installation Requirements Overview
- Archive to a Database Checklists
- Archive or Retire to Data Vault Checklists
- Smart Partitioning Source Data Checklists
- Data Archive Options Installation Checklist
  - SAP Retirement Installation Checklist
- Data Archive Architecture Recommendations

Installation and Upgrade Guide

6.5
- 6.5.1
- 6.5 HotFix 1

Back Next

Live Archiving

Create a data staging tablespace in the source database for all live archive jobs. For example, AM_STAGING_D.

All live archive jobs require staging space. The archive job uses the staging space to store the following tables:

Interim tables: The archive job creates interim tables for business rule validation and candidate generation during the archive process.
The staging space requirements depend on the size of the interim tables. Configure the tablespace size to the number of archived rows from the largest table in a single archive job multiplied by the average row size. A general guideline is to use 1K for the average row size.

Staging tables: If you enable staging for the archive source connection, the archive job creates staging tables. The staging tables temporarily store a copy of the archived data before the archive job moves the data to the archive or history database.
The staging space requirements depend on the size of the data in the archive job. Configure the tablespace size to the largest amount of archived data in a single archive job.

Staging space is not required for retirement jobs. Retirement jobs do not validate business rules, generate candidates, or create staging tables because the jobs archive all source data.

Rename Saved Search

Table of Contents

Installation and Upgrade Guide

Installation and Upgrade Guide

Live Archiving

Live Archiving