226 IBM Content Manager OnDemand Guide
If a user queries the index data that was migrated, an administrator must act to import a copy 
of the migrated table or tables by running ARSADMIN (Multiplatforms or z/OS) or Start Import 
into Content Manager OnDemand (STRIMPOND) on IBM i. After Content Manager OnDemand 
maintains the imported index data in the database for the number of days that is specified in 
the Keep Imported Migrated Indexes field, Content Manager OnDemand deletes the data 
from the database.
Migration of indexes 
This configuration is set up by clicking Advanced on the Storage Manager tab of the 
Application Group window.
This field determines when Content Manager OnDemand migrates index data to archive 
storage. Choose from No Migration or Migrate After __ Days. As a preferred practice, do not 
migrate indexes to archive storage. Indexes that are migrated cannot be searched until after 
they are imported by an administrator. Use this capability only under limited circumstances.
The index data must be migrated only after users no longer need to access the data. If a user 
must access data in the migrated tables, the process of importing the data into the database 
requires administrator intervention, and usually results in a significant delay in completing the 
query. Additional space is required in the database and temporary storage areas to import the 
data.
To enable the migration of index data, you must define a storage set that identifies a storage 
node that is maintained by ASM and update the System Migration application group to use 
the storage set.
10.3.2  Expiring data and indexes
In all four of the storage and expiration scenarios, the index data is stored in the Content 
Manager OnDemand database in application group data tables. Typically, these indexes are 
expired when the document data is expired from the system.
Life of Data and Indexes field
This field determines when Content Manager OnDemand deletes documents, resources, and 
index data from the application group. 
Closing index tables: Before you can migrate index data, the index tables must be closed. 
The following Database Organization field options are valid:
/SM590000If the Database Organization field for the application group is set to Single Load per 
table, this option is no longer supported. 
/SM590000If the Database Organization field for the application group is set to Multiple Loads per 
table, the index table is closed when the Maximum Rows value is reached. 
/SM590000The Single table for all loads option is available for Content Manager OnDemand for 
z/OS and Content Manager OnDemand for IBM i. Select the Single table for all loads 
check box if you want to create one database table for each application group. This 
option is most frequently used when you load a small amount of data. If you select this 
option, the Maximum Rows field in this window is removed.
To close a table to loading before the Maximum Rows value is reached, run the ARSTBLSP 
program with the -a1 parameter.