WebSphere Commerce Portal V5.4 Solutions

374 WebSphere Commerce Portal V5.4 Solutions

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

򐂰 For accounts:

Remove the account.xml file from the store archive and the sarinfo.xml file.

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 ecmsg_hostname_timestamp.log or

ecmsg_instancename_timestamp.log (iSeries™) to ensure that the contract and

account assets published properly. If not, see “Republish a contract or account”

on page 373.

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:

a. In a DB2 command window, type:

db2 get db cfg for <wc_database>

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

db2 update db cfg for <wc_database> using <logfilsiz>

Where <logfilsiz> is a larger number then the previous number.

c. Restart DB2.

or

In a DB2 command window, type:

db2 update db cfg for <wc_database> using LOGPRIMARY 20