Troubleshooting WebSphere Commerce Analyzer

The troubleshooting information for WebSphere Commerce Analyzer is divided into the following categories:

• Troubleshooting WebSphere Commerce Analyzer help
• Troubleshooting DB2 problems on WebSphere Commerce Analyzer
  • No schema displays on an iSeries database
  • Upgrading your DB2 fix pack level on the WebSphere Commerce Analyzer machine
• Troubleshooting replication and ETL
  • WebSphere Commerce already running error
  • Primary key error
  • Unable to allocate new pages in tablespace
  • Recover from a load operation that failed because of a data problem
  • SET INTEGRITY or SET CONSTRAINTS command fails
  • WebSphere Commerce Analyzer data mart runs out of disk space
  • WebSphere Commerce Analyzer DB2 transaction log fills up
  • A network outage occurs
  • A windows failure occurs on the WebSphere Commerce Analyzer server and causes a system restart or DB2 restart
  • The ASNCAP program stops
  • Replication setup fails
  • A step fails during initial replication and ETL
  • A step fails after initial replication and ETL
  • The first step in the replication cycle runs for a long time
  • CHECK_REFERENCE fails due to a missing value
  • Previous ETL run started but not finished
  • Poor performance
  • Time stamp out of range
• Troubleshooting reports
  • No data in the Business intelligence reports

  For troubleshooting information about WebSphere Commerce Analyzer installation and configuration, see the WebSphere Commerce Analyzer section of the WebSphere Commerce Additional Software Guide.

Related concepts

• Business intelligence and analytics
• WebSphere Commerce Analyzer
• Reference tables
• Replication and extract, transform, and load (ETL) processes

Related tasks

• Run replication and ETL
• Viewing WebSphere Commerce Analyzer reports

(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.