Configuring publish

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


  1. 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
  2. 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 > Search Configuration.
      3. Select the Schema Optimization tab.
      4. Ensure that all check boxes are cleared. Then click Apply.
  3. Increase the amount of space available in the transaction log by doing one or more of the following:
    1. Create secondary transaction logs using the DB2 Control Center.
    2. Increase the transaction log file size by doing one of the following:
      • In a DB2 command window, type:
        db2 get db cfg for 

        Then, look for the log file size ( LOGFILSIZ). After finding the log file size, type:

        db2 update db cfg for 
        databasename using LOGFILSIZ 

        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.