In order to avoid publishing problems, the following actions are recommended before publishing your store archive:
- Set the following attribute values to volatile.
- Open a DB2 command window.
- Type: db2 connect todatabasename.
- Then type: db2 alter table catentdesc volatile
- Then type: db2 alter table attribute volatile
- 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:
- Open Configuration Manager.
- In Configuration Manager, select WebSphere Commerce > Node > Instance List > instance_name > Search Configuration.
- Select the Schema Optimization tab.
- Ensure that all check boxes are cleared. Then click Apply.
- 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:
Increase the amount of space available in the transaction log by doing one or more of the following:
- Create secondary transaction logs using the DB2 Control Center. For more information, see the DB2 Administration Guide.
- Increase the transaction log file size by doing one of the following:
- In a DB2 command window, type:
db2 get db cfg for databasename
Then, look for the log file size (LOGFILSIZ). After finding the log file size, type:
db2 update db cfg for databasename using LOGFILSIZ newlogfilesize
where newlogfilesize is a larger number than the current value.
Restart DB2.
- 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.
For more information, see the DB2 Administration Guide.
- In a DB2 command window, type: