382 IBM Content Manager OnDemand Guide
Figure 18-3   Output of db2 list tablespace 3 command
d. Check whether any of the containers that were listed previously belong to the file 
system that is full:
 If any of the containers that were listed previously belong to the full file system, 
close the opened application group data table by using the following command:
arstblsp -a 1 -g AppGrpName
The following message indicates that the table closed successfully:
Closed table successfully:  ApplGroup(AppGrpName) Agid(5016) Table(CAA1)
 If none of the containers that were listed previously belong to the full file system, 
continue to find the next application group.
When the application group data table is closed, Content Manager OnDemand creates a 
table on a file system as defined in ARS.DBFS when data is next loaded. Content Manager 
OnDemand also searches for a file system with more free space to create the new table.
/SM590000Problem: The arsmaint program fails to complete.
Reason or resolution: The problem that is most commonly encountered is that the cache 
file system is full or a link is broken. 
For a full cache file system, check to determine which file system is full, and expand the 
file system, if possible. 
For a broken link problem, the system log displays errors that relate to arsmaint. 
If neither situation is the case, check to see whether arsload is running at the same time. 
If arsload is running at the same time that you run the arsmaint -r command, arsmaint 
might fail. 
Tablespace Containers for Tablespace 3
 Container ID = 0
 Name = /arsdb/db1/SMS/ARCHIVE/root/CAA1.0.0
 Type = Path
 Container ID = 1
 Name = /arsdb/db1/SMS/ARCHIVE/root/CAA1.1.0
 Type = Path
 Container ID = 2
 Name = /arsdb/db1/SMS/ARCHIVE/root/CAA1.2.0
 Type = Path
 Container ID = 3
 Name = /arsdb/db1/SMS/ARCHIVE/root/CAA1.3.0
 Type = Path