Troubleshooting
Problem
The WDI client for Windows allows transactions in the Document Store to be selected by "Date Added to Store" (column TRANDATE). However, there is no index for TRANDATE on Document Store table EDIENU33.EDITSTH, hence the query does a full table scan to identify these transactions.
Symptom
Depending on the number of transactions in the Store, a WDI Client 11041 time-out error may occur or selection performance may degrade as the number of transactions in the Store increases.
Resolving The Problem
One solution would be for the WDI Client end-user to specify selection criteria for "Transaction Handle Between" values to select a date, or date range, instead of using "Date Added to Store Between." This is more efficient because "Transaction Handle" (column THANDLE) already has a DB2 index (EDIENU33.EDITSTHX) defined as part of the base WDI server installation.
If the "Date Added to Store Between" selection criteria is preferred, the data base administrator can add a new DB2 index to improve query performance. For example:
- CREATE INDEX EDIENU33.EDITSTHI1
ON EDIENU33.EDITSTH
(TRANDATE)
USING STOGROUP EDISG332
PRIQTY 1000
SECQTY 200
ERASE NO
FREEPAGE 0
PCTFREE 0
BUFFERPOOL BP0
CLOSE NO;
As another example, if end-users commonly specify both "Date Added to Store Between" (column TRANDATE) and "Source or Target Equal To" (column TRANDIRC), then the DBA could instead add a new index as follows:
- CREATE INDEX EDIENU33.EDITSTHI1
ON EDIENU33.EDITSTH
(TRANDATE , TRANDIRC)
USING STOGROUP EDISG332
PRIQTY 1000
SECQTY 200
ERASE NO
FREEPAGE 0
PCTFREE 0
BUFFERPOOL BP0
CLOSE NO;
Was this topic helpful?
Document Information
Modified date:
01 August 2018
UID
swg21692643