Administer > Transforming, loading, and extracting data > Overview of the data load utility > Run the data load utility


Verify the results of the data load

Verify that the data load utility has run successfully by checking the exit value in the summary report or in the wc-dataload.log file. If errors occur, analyze the data in the error reports as a first step in finding the root cause.


Before you begin

Run the data load utility before verifying the results.

The wc-dataload.log logging/tracing file is generated each time the data load utility is run. Also, a separate error log file is generated for each LoadItem that consists of one or more errors. If no error occur, then no error logs are generated. The summary report is the information displayed on the console when you run the data load utility. See Data load order configuration file for more information on the data load order configuration file schema.


Procedure

  1. Check the summary report. The summary report contains the following information for each LoadItem:

    LoadItem Information Description
    Business Object Configuration The name of the business object configuration used.
    Data loader mode The mode specified for the data load run.
    Batch size The batch size value specified in the configuration file.
    Commit count The commit count value specified in the configuration file.
    Error Tolerance Level The error tolerance level as specified in your configuration file.
    Error Count The number of errors generated.
    Amount of data processed If you are using the default CSV reader, this number indicates the number of lines processed in the CSV source file.
    Amount of business objects processed The number of data objects returned from the data reader. One data object returned might be constructed into multiple business objects. But in most cases, one data object returned is constructed into one business object.
    Amount of business objects committed The number of constructed business objects that are saved in the database or in the files. This value depends on how the data writer is configured.
    Data loader initialization time The initialization time of the data loader.
    Data loader execution began The start time of the data load run in seconds.
    Data loader execution ended The end time of the data load run in seconds.
    Data loader completed in The total running time of the data load in seconds.
    Total flush time The total time it takes to call the JDBC batch execution. This information is only useful if the JDBC batch is enabled (that is, the batch size is greater than 1.) If the JDBC batch is enabled, then it is the total time spent to run all the SQL statements.
    Total commit time The total time it takes to call the database commit. The time is typically small and not useful.
    CSV file location The location of the source data.
    Table name, number of rows affected The names of the database tables updated, and the number of rows updated for each table.

    A sample summary report: 

    =============================================================================
==
WebSphere Commerce Data Load
=============================================================================
==

Load started at: Thu Sep 10 16:34:46 EDT 2009
Initialization completed in 12.031 seconds.

Processing MemberData...

-----------------------------------------------------------------------------
--
Load summary for load item: MemberData.
-----------------------------------------------------------------------------
--
Business Object Configuration: C:\Websphere\CommerceServer70\bin\fvt\config\F
T.DATALOADFRM-15-0301-bocfg-wc-loader.xml
Data loader mode: Replace.
Batch size: 1.
Commit count: 1.
Error Tolerance Level: 1.
Error Count: 0.
Amount of data processed: 2.
Amount of business objects processed: 1.
Amount of business objects committed: 1.
Data loader initialization time: 1 seconds.
Data loader execution began: Thu Sep 10 16:34:58 EDT 2009
Data loader execution ended: Thu Sep 10 16:35:00 EDT 2009
Data loader completed in 2.781 seconds.
Total flush time: 0 seconds.
Total commit time: 0 seconds.
CSV file location: C:\Websphere\CommerceServer70\bin\fvt\input\MEMBERDATA.csv
Affected tables (7): Table name: MEMBER, Affected number of rows: 1.
Table name: USERS, Affected number of rows: 1.
Table name: MBRREL, Affected number of rows: 1.
Table name: USERREG, Affected number of rows: 1.
Table name: ADDRBOOK, Affected number of rows: 1.
Table name: ADDRESS, Affected number of rows: 1.
Table name: MBRROLE, Affected number of rows: 1.
-----------------------------------------------------------------------------
--


Program exiting with exit code: 0.
Load completed sucessfully with no errors.

Load ended at: Thu Sep 10 16:35:00 EDT 2009
Load completed in 14.828 seconds.

  2. Open the wc-dataload.log file in the following directory:

    The system exit value displayed in the wc-dataload.log file or the summary report, indicates the following:

    1. If the data load utility finishes successfully without any errors, the system exit value is 0.

    2. If the data load utility finishes with some errors (fewer errors than the maxError), the system exit value is 1.

    3. If the data load utility terminates early because one of the DataLoader error number reaches the maxError, the system exit value is 2.

    4. If the data load utility terminates early due to some unrecoverable error such as DataLoadConfigException and DataLoadSystemException, the system exit is 3.

    Some exceptions that might be displayed in the report, are described...

    DataLoadSystemException

    This error occurs when there are some system errors. One example of a system error is the database deadlock exception, and Out of Memory exception.

    DataLoadSQLException

    This error occurs when the data load executes some SQL statement and the database throws an exception.

    DataLoadConfigException

    This error occurs when the configuration file contains incomplete elements or the content of element is incorrect.

    DataLoadApplicationException

    This error occurs when the input data source file has erroneous records.

  3. Optional: If an error has occurred, open the error log, located in the same directory. The filename of the error log contains the name of the LoadItem, as well as the date and time that the error occurred.

    For example, if an error occurred for the LoadItem CatalogGroup, the file name might be CatalogGroup_ERROR_2009.08.26_14.54.21.406.log. The error logs contain the following information:

    • File path location of the error log.

    • The application and exception messages that occurred.


Previous topic: Run the data load utility

Related reference

Troubleshoot: Data load error occurs when attempting to populate ITEMSPC table due to mandatory parameter missing

Troubleshoot: Data Load failed to start database error

Troubleshoot: Data Load ID not found error

Troubleshoot: Data Load ID not resolved for the table CATENTRY with the unique index data error


+

Search Tips   |   Advanced Search