If you experience problems while publishing a store archive, do the following:
- Review the following log files: For more information and locations for each log file, see Publish log files.
- To configure logging for the Loader package, including increasing the logging level, see Customizing logging for the Loader package.
- Enable the WC_DEVTOOLS trace log. For more information, see the
WebSphere Commerce Administration Guide.
- If the problem occurred while executing a particular task, you should configure tracing for the corresponding component. For example, if it the contractimport or accountimport command fails, enable the corresponding component, WC_Contract. For more information, see the WebSphere Commerce Administration Guide.
- If an error occurs during the data loading phase of publishing, the error
displays on the Publish Details page in the Administration Console. To view the
Publish Details page for your store archive, see Viewing
publish status.
For more information on how publish works, see the WebSphere Commerce Store Development Guide, chapter "Publishing a complete store."
Republishing contract or account
If a message in the activity.log or the Publish Details page reports a duplicate contract exception, but publishing has completed successfully, do the following:
- Determine if the contract is the same.
- If the contract is the same, ignore the warning.
- If the contract is different, do the following:
- Ensure that you have changed the sequence number in the contracts.xml file
to the next number in the sequence. The sequence number is a combination of
the value for the majorVersionNumber and the
minorVersionNumber.
For example if the majorVersionNumber="1", and the minorVersionNumber="0" change the value for the minor version number to 1. The resulting sequence number will be 1.1. When you change the major version number and then republish the store archive, a new contract will be created in the database. This new contract replaces the previous contract. If you do not change the major version number, a "contract exists" error will be recorded in the logs when you republish the store archive, and the contract information will not be updated in the database - Import the contract. For more information, see Importing a contract (Business Edition).
- Ensure that you have changed the sequence number in the contracts.xml file
to the next number in the sequence. The sequence number is a combination of
the value for the majorVersionNumber and the
minorVersionNumber.
If a message in the activity.log or the Publish Details page reports a duplicate account exception, but publishing has completed successfully, ignore this warning.
Publishing is successful but store does not display or does not function properly
If publish is stated to be successful, but you can't launch the store, or the store isn't functioning properly, check the activity.log file for errors.



Transaction log for the database is full
If the message, "Transaction log for the database is full," displays in the message.txt log, you have the following options:
- 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 the following:
In a DB2 command window, type: db2 get db cfg fordatabasename
Then, look for the log file size ( logfilsiz). After finding the log file size, type:
db2 update db cfg fordatabasename using logfilsiz where logfilsiz is a larger number then the previous number. Restart DB2. OR In a DB2 command window, type:db2 update db cfg fordatabasenameusing 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.
- 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, do the following:
- Open Configuration Manager.
- In Configuration Manager, select the Instance, then select Search Configuration.
- Select the Schema Optimization tab.
- Ensure that all check boxes are cleared. Then click Apply.