as a DB2 DBA we have defined a second storage path
DB_STORAGE_PATH /db2/oda/db2data2/
From the ARS Interface the tablespaces are defined as SMS Tablespace with autostorage = no
The question is: what happenens if the first storage path is full ?
J?rgen
P.S. with DMS Tablespace (not supported with CMOD) - i can do DB2: alter tablespace rebalance - and the TS is on both storage path's
In CMOD, the plan would be that you define SMS filesystems inside the ars.dbfs configuration file, then create the database.
Can you not just define new tablespace containers on the new filesystems?
-JD.
thank you for the answer - the tablespace containers are defined by the CMOD Software (Application Group) - the two storage paths are defined in ars.dbfs File. May be all is defined right - and the second storage path is used, if the the first is full ?? ;D
J?rgen
Hello Juergen,
If you read the documentation it says:
QuoteThe 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.
Have you checked that part about the "equal amount of disk space" ??
Sincerely yours,
Alessandro