Chapter 18. Troubleshooting and tracing 379
18.1.2  Indexing and loading issues
The following common problems are encountered while users index or load documents:
/SM590000Problem: When you attempt to index a report with a large record length, you see the error 
message that is shown in Figure 18-1.
Figure 18-1   Error message with return code 310
Reason or resolution: The maximum record length, which is 32 KB, for AFP Conversion 
and Indexing Facility (ACIF) might be exceeded.
Return code 310 explanation: An attempt to read a dataset failed. This message is 
informational and further action takes place in higher-level modules, if required. The file 
format is not valid.
/SM590000Problem: The arsload program performs progressively slower over time.
Reason or resolution: Performance problems can be caused by various reasons, and 
they require careful examination. Content Manager OnDemand issues an SQL DELETE 
against the ARSLOAD table before Content Manager OnDemand adds that same 
information to the ARSLOAD table to guarantee uniqueness. Duplicate information cannot 
be in the ARSLOAD table. This SQL DELETE is a single action against the ARSLOAD table 
and it uses an index that is formed from the application group identifier (AGID) and NAME. 
The ARSLOAD table has two indexes: 
– ARSLOAD_NAME_IDX, which contains the AGID and NAME
– ARSLOAD_IDX, which contains the AGID and EXP_DATE columns
Without the ARSLOAD_NAME_IDX, each load performs a complete table scan of the 
ARSLOAD table. 
Check to see whether you already have these indexes. In addition to index creation, gather 
statistics by running the following command:
arsdb -I <INSTANCE_NAME> -mv
/SM590000Problem: The arsload program terminates when an unrecoverable error occurs during 
index, database, or storage manager processing.
Reason or resolution: Open the Content Manager OnDemand system log folder and 
view the messages that the arsload program generated during the load process. Search 
for message number 88 in the system log.
If the arsload program failed during indexing, correct the problem and then restart the load 
process from the beginning. Common causes of problems during indexing include invalid 
input files, invalid indexing parameters, invalid indexing parameter files, and insufficient 
temporary space.
If the failure occurred during database processing or storage manager processing, check 
the database or storage manager for errors.
Check the message log for a load ID that the arsload program saved in the system log. 
Before you attempt to reload the input data, you must remove the data that was created 
during the failed load process by using the UNLOAD function of the arsadmin program. 
Restart the load process from the beginning.
0425-422 AN ERROR OCCURRED WHILE ATTEMPTING TO READ /filename RETURN CODE 
310.