Configuring publish

To avoid store publishing problems, set database attributes, disable summary tables and increase transaction log size before you publish a store archive.

Procedure

Set the following attribute values to volatile by using the Alter Table notebook or the alter table statement to alter the row format of table data.
To alter a table, you must have one of the following authorities or privileges:
- ALTER privilege
- CONTROL privilege
- SYSADM authority
- DBADM authority
- ALTERIN privilege on the table schema
1. Open a DB2 command window.
2. Type: db2 connect to databasename.
3. Then type: db2 alter table catentdesc volatile
4. Then type: db2 alter table attribute volatile
5. Then type: db2 alter table attrvalue volatile
Disable the summary tables. Leaving the summary tables enabled may result in the following:
- Summary tables will be updated during publish, which could result in a database transaction log overflow and affect the publishing performance. To disable the summary tables:
  1. Open Configuration Manager.
  2. In Configuration Manager, select WebSphere Commerce > Node > Instance List > instance_name > Catalog Search Configuration.
  3. Select the Schema Optimization tab.
  4. Ensure that all check boxes are cleared. Then click Apply.
Increase the amount of space available for DB2 transaction logs by updating the LOGFILSIZ, LOGPRIMARY, and LOGSECOND database configuration parameters.
1. In a DB2 command window (db2 on Unix platforms and db2cmd or db2cmdadmin on Windows platforms), view the database configuration:
```
db2 get db cfg for databasename
```
  - In a DB2 command window, type:
```
RESTART DATABASE databasename
```
  - In a DB2 command window, type:
```
db2 update db cfg for 
databasename using LOGPRIMARY 20
```
    where 20 is the number of primary logs (this number may be different for your site). Increasing the LOGPRIMARY increases your space requirement.
2. Find the LOGFILSIZ parameter.
3. Increase the LOGFILSIZ parameter with a value that is larger than the current LOGFILSIZ value:
```
db2 update db cfg for databasename using LOGFILSIZ newlogfilesize 
```
4. Similarly, increase the LOGPRIMARY parameter with a value that is larger than the current LOGPRIMARY value.
```
db2 update db cfg for databasename using LOGPRIMARY newlogprimarysize
```
  For example, if you set the newlogprimarysize to 20, then 20 is the number of primary log files. Increasing this parameter increases your space requirement.
5. Similarly, increase the LOGSECOND parameter with a value that is larger than the current LOGSECOND value.
```
db2 update db cfg for databasename using LOGSECOND newlogsecondsize
```
  For example, if you set the newlogsecondsize to 20, then 20 is the number of secondary log files. Secondary log files are allocated only after all primary log files are fully allocated.