MustGather - WDI Client database errors

Technote (troubleshooting)


Problem(Abstract)

Collect troubleshooting data for problems with IBM WebSphere Data Interchange. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Resolving the problem

This document describes how to collect troubleshooting data specifically for when you encounter a database error in Windows based WDI Client..



Database error encountered in WDI Client

In most cases, unexpected errors encountered during WDI Client navigation are related to the database. If the error is DB2 related, diagnose the issue first by checking the specific SQL code and DB2 reason code.

If the issue persists, and when requested by Support, capture a DB2 CLI trace and/or ODBC trace as follows:

CLI and DB2 Trace instructions:

- Use the following document for specific DB2 instructions: Collecting data: CLI Applications
- Recreate the problem on WDI 3.3 Client,
- Close the error window and exit WDI Client,
- Turn all tracing off,
- Zip/compress the trace files before submitting information to IBM Support.


ODBC Tracing instructions:

Windows Start menu -> Administrative tools -> Data Sources (ODBC) -> Tracing tab (see below) -> Click browse to fill log file path with a valid path and a new file name (the file name you enter will be created for you)



- Click Apply, then click "Start tracing now",
- Start WDI Client and then recreate the problem,
- Close the error window and exit WDI Client,
- Close WDI Client,
- Stop ODBC tracing,
- Zip/compress the trace file before submitting information to IBM Support.




Submitting information to IBM Support

After a PMR is open, you can submit diagnostic MustGather data to IBM. If using Service Request (SR), update the PMR to indicate that data has been sent.



Related information

MustGather - WDI Mapping
MustGather - WDI MultiPlatform (AIX or Windows) processing
MustGather - WDI z/OS Batch (JCL) processing
MustGather - WDI CICS processing
WebSphere Data Interchange Tutorials
Database error 11041 when opening a new database connection from WDI Client.
How do I disable the Data Source Login page when launching the WDI 3.3 Client?
Database error upon start-up due to a problem with WDIClient32cfg.mdb or WDIClient32dev.mdb databases
WDI z/OS database security error opening table EDIPSDI.
How To Recover from an SQL30081N Error Message?
WDI Client error 11041 when searching the Document Store.
Resolving Error 129 When Running Server Commands on Client
Why does the stored procedures for WDI 3.3 on z/OS give me a SQLCODE = -991 SQLSTATE 57015 RC1=0008 RC2=00F30049
Resolving Error Message 11041 when Exporting a Data Format Dictionary
Webcast replay: Configuring WebSphere Data Interchange 3.3 for z/OS Stored Procedures in a WLM Application Environment
Exchanging information with IBM Technical Support
Featured documents for WebSphere Data Interchange

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Data Interchange
WDI 3.3 Client

Software version:

3.3

Operating system(s):

Windows

Software edition:

All Editions

Reference #:

1624629

Modified date:

2014-12-18

Translate my page

Machine Translation

Content navigation