Reduced maintenance costs because application and database maintenance and license fees are no longer paid for the old application and its database, but data remains accessible to the user community.

Decommissioned data is needed every day by end-users and Optim caches it in memory so access is faster then the production database.

Reporting from the application against the archived data can be cheaper using tiered storage.

Optim can store decommissioned data in a compressed format so it will take less storage then it did in production.

Applications must continue to use data in a seamless manner.

An Insert process can always insert all the data successfully regardless of the presence of complex referential integrity (RI) cycles.

An Insert process allows for Update/Insert processing in one step; a Load process may not.

An Insert process will be faster than a Load process when inserting large volumes of data.

An Insert process allows you to use Column Maps to transform data; a Load process does not.

The Character or Numeric data must have a length of 256 bytes and be padded with blanks or binary zeros as needed.

The source column can only contain date or timestamp data.

The source column can contain date or timestamp data; character or numeric data may be used if a date format is applied to the AGE function.

The date format used in the Column Map must be entered in the format used by the database.