Migrating indexes

About this task

Note: This section provides an overview of the process of migrating index data from the database to archive storage. See "Migrating and importing index data" for information about configuring the system for migration processing.

Content Manager OnDemand provides automatic migration to move indexes from the database to archive storage to maintain seldom used indexes for long periods of time.

Important: If you use migration to move indexes to archive storage, make sure that you migrate them after there is no longer a need to retrieve the documents to which they point.

The ARSMAINT program uses an application group's migration policy to control when migration of indexes for an application group occurs:

Migration of Indexes. If you specify No Migration, then migration of indexes is disabled for the application group. (That is, index data will not be migrated.) If you specify Migrate After n Days, then index data is eligible to be migrated after reaching the specified number of days. Indexes will be migrated the next time that the ARSMAINT program runs.
Life of Data and Indexes. The length of time in days to maintain index data on the system. For migration, this value must be greater than the Migrate After n Days value.

Content Manager OnDemand does not migrate index data from the database to archive media until migration processing runs. The ARSMAINT program is the migration utility. You can control automatic migration processing by scheduling the ARSMAINT program to run with the appropriate options. You can also manually start migration processing by running the ARSMAINT program from the prompt. See ARSMAINT for more information about the ARSMAINT program.

The IBM® Content Manager OnDemand for Multiplatforms: Installation and Configuration Guide provides help with scheduling tasks.

The ARSMAINT program migrates indexes from each file system listed in the table space file system file.

After a migrated table is successfully loaded into the System Migration application group, the table is dropped from the database. However, Content Manager OnDemand keeps track of all migrated tables. That way, if index data in a migrated table is needed, then Content Manager OnDemand can alert an administrator to take action (such as manually import the table back into the database).

You can control automatic migration processing by scheduling the ARSMAINT program to run with the appropriate options. See ARSMAINT for more information about the ARSMAINT program.

The IBM Content Manager OnDemand for Multiplatforms: Installation and Configuration Guide provides help with scheduling tasks.

You can also manually start migration processing by running the ARSMAINT program from the prompt. For example, to run migration processing, enter the following command at the prompt:

     arsmaint -e

When the ARSMAINT program migrates indexes, it saves the following messages in the system log. A set of three messages should be saved in the system log for each table that is migrated from the database to archive storage:

     166 ApplGroup Segment Export (ApplGrp) (Segment)
     14 DB Info Exported (SQL Code)
     87 ApplGrp Load (System Migration)

The first message identifies a segment of application group index data that is to be migrated from the database to archive storage. The second message reports the status of exporting the table from the database to temporary storage. The third message reports the status of loading the migrated table into the System Migration application group. The System Migration application group must be assigned to a storage set that identifies a client node that is maintained by the archive storage manager.