DSXchange

Hopefully something similar but with better stage variable names. :wink: FYI - this is old school stage variable usage for resetting a counter while doing group change detection. And the first variable isn't really needed but can be helpful if your 'group' consists of multiple fields. And as with al...

I'll be curious if anyone can help as you're kind of out there on the bleeding edge of the product, playing with new functionality. You may need to involve your official support provider and then come back and tell us the answer.

ps. You can't link to an image on your local PC. While you can see it in your post, no-one else can. Either post the log contents (text) or upload the image to any of the free file sharing sites out there and then link to that.

Probably because 20,000 of them are spam bots.

asorrell wrote:The QEWSD entry is a marker inserted by the drivers to show illegal use of the drivers by products other than DataStage.

Interesting... one learns something new every day. Or most days. Well... once in a while.

Is this coming from the O/S or from Oracle? Please post the entire error message. This is an "Interrupt Signal" which can (for example) come from a kill command. I'd be curious if the stage has been returning records during the 7 or 8 hours or if it was still 'gathering' information and th...

**VIEWDATA ROW LIMITER HIT** means exactly what you would think it does - there's only a finite number of records that the viewer can show at once and you've hit that limit. From what I recall, there's an option to limit the viewer to the first X records.

Welcome.

In your shoes I'd be chatting with your DBA for errors like that. Obviously something has changed and seems to me they could help track that down once you show them what you are doing in the Connector.

Googled for your SQLSTATE & CODE. Perhaps these help:

http://dba.stackexchange.com/questions/ ... d-for-user

or

http://www.sqlserverblogforum.com/2012/ ... ep-failed/

I'm assuming it's more about the size of the originating string (255) rather than the data itself. If you drop the string size down to match the data, does that change the message?

Hopefully it goes without saying that any manual method would be a weapon of last resort.

Let me break the tension... same!

They both accomplish the same thing. However, one is button click and the other is a pain in the butt that requires several slides to document.

It would help if you explained your 'grouping evaluation' logic in the transformer. Assuming this shared container is meant to be used in multiple jobs then I would suggest you make no assumptions about how the incoming data is arriving. Sort it by group first, add a Key Change column to ease your g...

asorrell wrote:DataStage doesn't really have a concept of "cached" records.

I'm assuming they are referring to the transformer cache introduced in 8.5 along with looping and the SaveInputRecord() and GetInputRecord() functions. Yes?