MustGather: Massload Utilities Issues in WebSphere Commerce

Technote (troubleshooting)


Problem(Abstract)

MustGather: Massload Utilities Issues in WebSphere Commerce

Resolving the problem

Gathering this MustGather information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.

Considerations before collecting data
Take note of the following before collecting the information described below:

  • Performance
    • Runtime tracing may be verbose, and it could impact performance during peak time. If possible, reproduce the problem on a non-production environment to capture tracing.
  • Security
    • Some trace strings could capture sensitive or personal infomation. Please be sure to sanitize the logs before uploading to IBM. Commerce uses data masking to help mask sensitive data. See Knowledge Center Masking Sensitive data in traces

Collecting Data


I. Configure environment

Follow the instructions below to configure your environment to capture the required diagnostic information:

  1. Additional configuration steps
    1. In addition to the individual logs for some of the loading utilities, you can configure an additional message log file, messages.txt, and a trace file, traces.txt, for the loading utilities. This can be helpful in getting more information to help determine any problems you may encounter. You can configure the contents and location of these files by editing the WCALoggerConfig.xml file. Follow the link below to enable tracing for the loader utilities before reproducing the problem.
      http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/index.jsp?topic=/com.ibm.commerce.data.doc/tasks/tml_config_tracing_logging.htm


II. Reproduce problem

  1. Provide the exact usage of the utility that was used , including all parameters provided.
  2. Provide any input and output files that were used and created from the loader utilities.


Ill. Validate the issue was captured
Before sending logs to IBM, ensure that the issue being reported was captured. Recommend to review the following documents to help facilitate proper log collection: Avoiding pitfalls when collecting traces.


IV. Collect data

Collecting general product information
Include the general information requested in MustGather: General Issues in WebSphere Commerce V7.0 alongside the component-specific information requested below.

  1. Collect the following files from the system:
    1. WC_installdir/logs/messages.txt1
    2. WC_installdir/logs/trace.txt2
  2. Collect the contents of the following directories from the system:
    1. WC_installdir/logs3
  3. *Naming conventions can be found here.


    • -What are these files?
      1 Loader utility log
      2 Loader utility trace
      3 May contain other log outputs used by loader utilities

  4. Run the following database queries to collect the necessary information from your database (output results in CSV format):
    Query Output file name
    SELECT * FROM KEYS KEYS.csv
    DB2 SELECT * FROM SYSCAT.TABLES SYSCAT_TABLES.csv
    DB2 SELECT * FROM SYSCAT.INDEXES SYSCAT_INDEXES.csv
    DB2 SELECT * FROM SYSCAT.REFERENCES SYSCAT_REFERENCES.csv
    Oracle SELECT * FROM ALL_CONS_COLUMNS A JOIN ALL_CONSTRAINTS C ON A.CONSTRAINT_NAME = C.CONSTRAINT_NAME WHERE C.CONSTRAINT_TYPE = 'R' SYS_ALL_CONSTRAINTS .csv



Submitting data to IBM Support

To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:


Document information


More support for:

WebSphere Commerce Enterprise
Utilities/Tools

Software version:

7.0, 8.0

Operating system(s):

AIX, IBM i, Linux, Solaris, Windows

Software edition:

All Editions

Reference #:

1454426

Modified date:

2015-04-10

Translate my page

Content navigation