Configuring the transaction logs size

If your environment consists of many endpoints, increase the transaction logs size to improve performance.

About this task

The transaction logs size can be configured through the LOGFILSIZ DB2 parameter that defines the size of a single log file. To calculate the value that can be used for this parameter, you must first calculate the total disk space that is required for transaction logs in your specific environment and then multiply it, thus obtaining the size of one transaction log. The required amount of disk space depends on the number of endpoints in your environment and the number of endpoints in the biggest scan group for which data is processed during the import.

During the performance test execution, details such as, disc utilization, disk speed, memory utilization is calculated. The details are shown in the form of chart.

Important: Use the provided formula to calculate the size of transaction logs that are generated during the import of data. More space might be required for transaction logs that are generated when you remove the data source.

Procedure

Use the following formula to calculate the disk space that is needed for transaction logs:

<The number of computers> × 0.0012 GB + <the number of computers in the biggest scan group> × 0.0012 GB + 17 GB

To obtain the size of a single transaction log file that can be specified in the LOGFILSIZ DB2 parameter, multiply the result by 1852.

Note: The number 1852 expresses the relation between the primary and secondary log files and is necessary to calculate the size of a single transaction log file (LOGFILSIZ). The factor was calculated assuming the default number of log files (LOGPRIMARY = 25 and LOGSECOND = 110).
Run the following command to update the transaction log size in your database. Substitute value with the size of a single transaction log.
Note: TEMADB is the default database name. If you are unsure whether it applies to your database, see: Checking the database name.
```
db2 update database configuration for TEMADB using logfilsiz value
```
For the changes to take effect, restart the database. Run the following commands:
```
db2 deactivate db TEMADB
db2stop
db2start
db2 activate db TEMADB
```
Restart the BigFix Inventory server.
1. To stop the server, run the following command:
```
/etc/init.d/BFIserver stop
```
2. To start the server, run the following command:
```
/etc/init.d/BFIserver start
```

Example

Calculating the single transaction log size for 100 000 endpoints and 15 000 scan results:

100 000 × 0.0012 GB + 15 000 × 0.0012 GB + 17 GB = 155 GB
155 × 1852 = 287060

287060 is the value to be specified in the LOGFILSIZ parameter.