Troubleshooting WebSphere Commerce Loader issues Technote
(troubleshooting)Problem(Abstract) This technote provides troubleshooting for the most common WebSphere Commerce Loader issues. Resolving the problem WebSphere Commerce provides utilities for preparing and loading data into a WebSphere Commerce database. These utilities provide various functions that can be strung together in the required sequence to solve particular WebSphere Commerce data management problems. The loading utilities are flexible enough to handle customizations that are made to the WebSphere Commerce schema. The loader utilities consist of the following utilities: txttransformer, xmltransformer, dtdgenerator, idresolver, massloader and massextract.
The objective of this document is to help customers determine and rectify the most common loader issues on their own.
IdResolver related issues:
Problems Possible Reason Possible Solution Unresolved ID (Primary key) The table entry does not exist in the KEYS or the SUBKEYS table. Make an entry for the corresponding table in the KEYS or SUBKEYS table. Unresolved ID (Foreign key) The unique key data provided in the input XML for that record might not be unique. Ensure that the unique keys data provided as an alias is in the correct sequence.
Ensure that the unique keys data provided as aliases exist in the XML file before the occurrence of this record, or check if this data already exists in the database.
Ensure that the foreign key constraints exist between the given table and its primary tables at the database level.
Make an entry in the IdResolveKeys.properties file for that particular table and provide this file path with the
–m propfile option to the IdResolver command.Unresolved ID (Foreign Key) This error can happen when using an alias to obtain the value for the Primary key, and the same alias is used elsewhere to refer to foreign keys in the foreign tables. Ensure that the primary key record appears before the foreign key records in the input XML file.
MassLoader related issues:
Problems Possible Reason Possible Solution Unable to massload a null string data This problem happens when the input XML data has empty data. For example: longdescription=(��) Configure MassLoadCustomizer:
The following two lines have to be added in the MassLoadCustomer.properties file and this file path has to be provided with the –customizer option when running the massload:
EnableNULLCheck = true
NULLStringLiteral =
If these suggestions do not resolve the problem, then proceed to the MustGather document.
Cross Reference information
Segment Product Component Platform Version Edition Commerce WebSphere Commerce Professional Edition Utilities/Tools AIX, Linux, Solaris, Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4 Professional Edition Commerce WebSphere Commerce - Express Utilities/Tools Linux, Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4 Express Commerce WebSphere Commerce Developer Enterprise Utilities/Tools Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4 Enterprise Commerce WebSphere Commerce Developer Professional Edition Utilities/Tools Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4 Developer Professional Edition Commerce WebSphere Commerce Developer Express Utilities/Tools Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4 Developer Express
Document Information Current web document: http://www.ibm.com/support/docview.wss?uid=swg21258227