Primary log storage space for the system

It is critical that you allocate enough disk space for the primary logs. Content Manager OnDemand cannot load reports if the database manager runs out of space for the primary logs.

The amount of primary log space required on the system is a factor of the largest report that you plan to load into the system (in terms of the number of indexed items, the number of indexes, and the size of the indexes), the maximum number of reports that you plan to load into the system at any one time, and some buffer space. In addition, for Db2®, if you use Tivoli® Storage Manager to maintain the Db2 archived log files, it is recommended that you triple the amount of space that you estimate for the primary logs. To estimate the total amount of primary log space required for your system:

Determine the primary log space required for the largest report.
Estimate the maximum number of reports that Content Manager OnDemand must process at any one time. Determine the storage space required for each report. Total the values.
Double the sum of the previous two values. The result is the storage space required for the primary logs.
Using the previous value, verify that the database manager will allocate enough primary log space. Use the following calculation and database configuration parameters:
Figure 1. Calculating primary log storage space
```
     PrimaryLogSpace = ( ( ( logprimary + logsecond )
                          * ( logfilsiz + 2 ) * 4096 ) + 8192 )
```
- The logprimary is 40
- The logsecond is 2
- The logfilsiz is 1000

By default, Content Manager OnDemand allocates approximately 172 MB of primary log space.