DSXchange

My record contains a fixed portion for 170 bytes, then depending on a # of segments field, variable 30 byte segments. The CFF (complex flat file) stage may also be able to help. From what I recall, the CFF stage can handle this exact requirement, as long as you mean a "variable number of 30 byte se...

Welcome! Post some examples, please, of Oracle errors that are not being trapped properly. I haven't seen this issue, but then I'm running 7.x and OCI9 and I don't recall checking for it back in the 5.2 version. Keep in mind that not all "rejects" come from Oracle. DataStage can kind of "pre-reject"...

Of course, if the first "if" satisfies the condition (equates to true) then nothing after that in the "if" will be evaluated. As to what your approach should be, it would help greatly to know your requirements or what it is exactly that you are trying to achieve. As a guess, I'd say try: If num(...

Yes, ditto - from all of us.

As far as I know, these are boolean values and not meant to be used in quite the way you are using them. You should simply say: if link.NOTFOUND Then input value Else lookedup value I'm not sure what you mean about the spaces, but give it a shot like this and see how that works for you. I remember (...

I think Fernando is asking how often the DataStage server should be restarted.

That's not an error, that's an informational message from the Bulk Load process. With a number like 64, I'd guess that was perhaps the total number of rows loaded. Usually commit points in a conventional load are multiples of 100, 1000, etc. Were there any other messages in the job's log? Failing th...

The only caveat to that is to understand that these would no longer be 'silent' rejects. With that check box marked, any rows that go down that link will be logged into the job's log with a warning and a total rejected records count. Sometimes that's a good thing and sometimes that can be a bad thin...

In version 6 the job freezes the value of the environment variable as soon as you add it to your job parameter list. If you go and change the value of the environment variable your job does not use the newer value. Just to add a little more to what Vince said about the rather odd way they were impl...

I'd suggest using @INROWNUM. Assuming your 'load' jobs work from landed flat files, this gives you a count of records to skip when restarting the job, regardless of how many rows this turns out to be in the target table (due to constraints, etc). In other words, don't track 'rows sent to target', tr...

Cool! That's a great idea Mr Hester.

ray.wurlod wrote:Alas this can't be done in server jobs. The Merge stage reads two text files; it does not have the ability to be driven by two streams. That's just the way it's written.

Sure you can... it's just that it takes two jobs.

No. Simply check one of the key fields in the lookup you are using for null. If you put data in and it comes back null, the lookup has failed:

Check the readme to see what needs to be setup for the DRS stage. I would guess you are missing something else from 'dsenv'. I'd look, but I'm only on 7.0.1 so I haven't played with it yet.

They should 'age out' of /tmp, but if space is tight and your job has finished then yes, it is safe to delete them if the job doesn't clean up after itself.

As to which other 'big' files are safe to delete... only those which you know are safe to delete.