DSXchange

What version of DataStage 7.x do you have? The ability of the sequence to trap job level errors (via the Exception stage) was only added in 7.5, from what I recall.

Before that, you need to handle it all yourself via triggers.

You need to use a Custom trigger to handle this. For Ran Ok and Warnings, use something like this in the trigger to Job2: Job1.$JobStatus = 1 Or Job1.$JobStatus = 2 Note that 'Job1' in the above trigger code is actually the Job Activity stage name that runs Job1. I'd suggest using an 'Otherwise' tri...

Now they just need to change the title of it!

And just to tack on another bit of information, something I've never had to do but understand cannot be done with 'out of the box' Server is access anything over HTTP / on a URL. From what I understand, you're going to need some 3rd party help or perhaps (as you noted) RTI - which is now called the ...

Regardless of the array size when writing to Oracle, I have noticed that DataStage will still log a warning in the log if a DBMS reject occurs (irrespective of the reject checkbox in the constraint being ticked). True, DBMS rejects are always logged... and the checkbox has nothing to do with that. ...

Did you follow the replies posted in your previous thread on a very similar sounding topic?

If you are asking (and it's hard to tell what you are asking) what does a '0' in a constraint mean, it was answered in that thread by Phil.

In my experience, I haven't seen all that much of a performance change by bumping the array size up when writing to Oracle. Reading, yes, but writing... not really. So we leave ours at 1. It does let you know the 'real' error when there is one, but (as Ray noted) a much better approach is to ensure ...

I declare col1 as varchar2(10) in all the stages(including oracle stage) of my Job and then I write a user defined sql, say for insertion as: insert into <table_name> (col1) values (to_date(:1,MM/DD/YYYY)). I'm not really sure why you would do this manually when the OCI stage will do the 'to_date' ...

Kim, I think you got it right.

The JobReport routine from ADN will give the OP what they are looking for based on how I read their post.

Welcome Aboard, Mr Bill.

A quick search of the forums here found 14 different threads which mention SIGSEGV which is a 'Segment Violation' btw. Take a scan through them and see if any of the suggestions solve your problem.

If not, post back!

Doesn't matter what your NLS date format is when it comes to writing to Oracle with the OCI stage. If you've declared your target DATE field as a Timestamp in DataStage (which is how you should be handling it IMHO and how it looks like you are) then you need to put the date into the format that the ...

Ah... sorry. Since you replied immediately after that using [] to hack up the input argument, I figured you were.

A couple of quick points... On the substring issue, Ray meant using only the substring operator - which is what was implied by changming. All fine and dandy when rearranging 'normal' dates, but not appropriate for converting from Julian. Also, you *can* edit your own posts, so rather than post a cor...

Welcome!

Something has corrupted the log for job number 31. Try searching the forums here for keywords like 'blink' and you'll find posts like this one. It should get you straightened out.

If not, post back.

I'm curious why this "should be done in the transformer"? Do you really want to collect these stats every time a row comes through your job? This is typically done after job. If you download Kim's code, you'll see how it can be accomplished. Also, you've said you tried using DSGetLinkInfo... how exa...