Troubleshooting publishing

If you experience problems while publishing a store archive, do the following:

  1. Review the following log files:
    • activity.log
    • trace.log
    • message.txt
    • trace.txt
    • iSeries RESWCSID.txt
    • SystemOut.log and SystemErr.log
    For more information and locations for each log file, see Publish log files.
  2. To configure logging for the Loader package, including increasing the logging level, see Customizing logging for the Loader package.
  3. Enable the WC_DEVTOOLS trace log. For more information, see the WebSphere Commerce Administration Guide.
    1. 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.
  4. 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:

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.

AIXSun Solaris Operating EnvironmentLinuxWindowsTransaction 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:

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.