Problem while reading from DB2 using DRS Stage

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
siva4joy
Premium Member
Premium Member
Posts: 34
Joined: Fri Apr 14, 2006 6:10 am
Location: London

Problem while reading from DB2 using DRS Stage

Post by siva4joy »

Hi,

We are using DRS Stage (ODBC) to connect DB2 .
while reading from DB2 tables using sql we are not getting all the records, ie, last set of records are dropping.
We never under stand why we are getting less number of records (usually 1500 records but last month the query extracted only 1150 records) becuase we never get any error while extraction .When we run manually same sql in DB2 we are able to see the 1500 records.

For this we asked the DB2 DBA to monitor the extraction process and below are the reults.

The Datastage Run bale to extract 1476 records while the manual run shows 1505 records.

FETCH (125)1 6.258 3,403 ms 36 ms *RC( 0) C=C01 D/X PS(1513
FETCH (125)1 9.694 3,460 ms 35 ms *RC( 0) C=C01 D/X PS(1473
FETCH (125)1 13.186 3,301 ms 35 ms *RC( 0) C=C01 D/X PS(1447
FETCH (125)1 16.519 3,276 ms 34 ms *RC( 0) C=C01 D/X PS(1428
FETCH (125)1 19.829 3,285 ms 34 ms *RC( 0) C=C01 D/X PS(1414
FETCH (125)1 23.148 2,647 ms 35 ms *RC( 0) C=C01 D/X PS(1379
FETCH (125)1 25.828 2,665 ms 34 ms *RC( 0) C=C01 D/X PS(1361
FETCH (125)1 28.528 3,121 ms 37 ms *RC( 0) C=C01 D/X PS(1367
FETCH (125)1 31.681 2,659 ms 36 ms *RC( 0) C=C01 D/X PS(1382
FETCH (125)1 34.375 2,672 ms 34 ms *RC( 0) C=C01 D/X PS(1400
CLOSE 1 37.077 14 us 14 us *RC( 0) C=C01

SERV-DTM 37.079 *TYPE=COMMIT MESSAGE RECEIVED
CLOSE-TS 37.079 DB=DSNRLST TS=DSNRLS01


Normally, when DB2 has retrieved all of the rows and there are no more to retrieve, the trace record looks like the following:

FETCH (170)1 6.618 47 ms 6,116 us *RC( 100) C=C01 D PS( 321)
CLOSE 1 6.688 15 us 15 us *RC( 0) C=C01

SERV-DTM 6.690 *TYPE=COMMIT MESSAGE RECEIVED


The RC(100) indicates that all of the rows from the DB2 cursor have been retrieved.

The actual trace record from this morning never displays a RC(100) so I can reasonably assume that something prevented DB2 from retrieving all of the rows.

According to the DBA something preventing to retrieve all the rows.

Can anybody ever faced the same kind of issues before?

Any thoughts or ideas would be of immense help to me.

Appreciate your help on this.

Thanks.

Regards,
Sivasankar.Z
Post Reply