Administer > Deploy > Publish a store archive > Publishing a store archive using the Publish wizard

Configure publish

Set database attributes

db2 connect to dbname
db2 alter table catentdesc volatile
db2 alter table attribute volatile
db2 alter table attrvalue volatile

Disable the summary tables

Leaving the summary tables enabled may result in the summary tables being updated during publish, which could result in a database transaction log overflow and affect the publishing performance.

From Configuration Manager select...

WebSphere Commerce | Node | Instance List | instance | Search Configuration | Schema Optimization tab

...and ensure that all check boxes are cleared. Then click Apply.

Increase of space in the transaction log

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 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 the site). Increasing the LOGPRIMARY increases your space requirement.

Before publishing a store archive

Before publishing a store archive, ensure that the appropriate services and servers are running.

+

Search Tips   |   Advanced Search