Archives of the TeradataForum
Message Posted: Wed, 01 Oct 2003 @ 15:48:21 GMT
| Subj: | | Re: User/Database DDL |
| |
| From: | | Julie Flanagan |
Apologies - only part of this mail seems to have sent the first time I posted it ....
Many thanks to all who responded to my recent post regarding problems we were experiencing with how MSRs were performing (problem
outlined below).
For info., for those who mailed me, we raised an incident with NCR on this (RECB2LWKG) - they were aware of the issue and it is under
investigation. - But beware if you are relying on Activitycounts at the end of MSRs (as we are throughout our production batch) - If your
final Insert returns no rows... your Activitycount will be ZERO - and your job may abend when you did not intend it to!
Julie.
(Background to problem: We noticed, following upgrade to V2R4, that some MSRs job outputs (BTEQ) were giving a breakdown of the no. of
rows inserted by each part of the MSR, instead of one total at the end, as was the case prior to upgrade. This is causing us production
problems as we use Activitycount checks to ensure at least one row is inserted, but if the LAST part of the MSR inserts no rows, the
ACTIVITYCOUNT is 0).
| 
