Specifying the ARS.DBFS file for the instance

The ARS.DBFS file lists the file systems on the library server that can be used by the database manager to maintain index data in table spaces.

The rules for using table space file systems are:
  • You should store only Content Manager OnDemand application group data in the table space file systems.
  • You should define a minimum of two table space file systems. (In general, the more table space file systems that you define, the better for performance and recovery.)
  • You should allocate equal amounts of disk space to each table space file system. If you increase the amount of space in one table space file system, you should increase the amount of space in the other table space file systems by an equal amount.
  • For Db2®, if you are planning on using Automatic Storage for tablespaces, you do not need to define any file systems for the database tablespace containers in the ARS.DBFS file.

Each line in the ARS.DBFS file identifies the name of a file system that Content Manager OnDemand can use to store table spaces and specifies the type of table spaces created in the file system.

When naming table space file systems, you should use the following convention: 
     /filesystem SMS
Where filesystem is the name of the file system and SMS indicates the type of table spaces created in the file system. The name of the file system should identify the type of table spaces that can be created in the file system. For example, the following line identifies an SMS table space file system: 
     /arsdb/db1/SMS SMS
The following example shows an ARS.DBFS file that defines three SMS table space file systems: 
     /arsdb/db1/SMS SMS
     /arsdb/db2/SMS SMS
     /arsdb/db3/SMS SMS