DSXchange

Forgot to come back and close this out. Pretty sure I posted this in a related thread, but the root of the problem was the version of the Oracle client the DBAs had installed. Reimaging the server didn't help as the Oracle client version hadn't changed. Finding they had installed a version known to ...

Search the forums for 'Fault type is 10'. I know there's posts out there.

That would be Sequencer stage. You could also just send your failure link directly to a Termination Activity stage. I've never really seen much use for the Exception Handler myself. [shrug]

That will work. I just modified one of my test sequence jobs to do this, no concatenation operator or quotes around the number and it worked just fine:


etc.

abc123 wrote:how do I send it the exception handler?

You don't "send" anything to the Exception Handler. Read the section that explains its properties in the Designer Guide pdf.

How would you specifically code for error in the routine? You'd need to handle that on a case-by-case basis. What I meant was check statuses or trap errors so you can control what gets passed back. For DSExecute() a non-zero value in the variable you've named rtncd would indicate a problem with the...

Ah... good to know. Never done the command line import, just export.

Welcome! :D Does creating 1 job for all the four mappings give me any performance benifit? No. In my opinion, there are no 'pros' and all 'cons' to this approach. If there are any dependancies on any of these jobs, you now need to wait for all jobs to complete. The bigger issue to me is restartabili...

From what I remember, you need equal signs between the options and values. And you don't use the words "project" or "filepaths" at all, just the actual values:

dscmdimport /H=host /U=test /P=pass /O=N /NUA=Y Proj_test C:\DSX\Test.dsx

For best performance of the Aggregator stage use sorted input.

What exactly is PARM1 and PARM2? I'm having a hard time following your question, it almost looks like you want to create an Invocation Id with a dot in it - "PARM1.1" - when that is not allowed. Or is PARM1 the name of your Sequence (note - not 'Sequencer') job and the '1' is the desired Invocation ...

What I've done in those cases where I need to check three flavors of return values from a routine is use three triggers. I have something similar where I pull Link Row Counts from a job and then: $ReturnValue=0 Link to 'no rows' processing $ReturnValue>0 Link to 'have rows' processing $ReturnValue<0...

Controller problem: Unhandled failure (5) encountered calling routine DSU.FoundFileCount This comes from having the 'Automatically handle activities that fail' option enabled in your Sequence job. As noted, your Routine returned a value of five (shown in parens) and a routine that does not return a...

[sigh] Rather than awaiting my reply you should be searching the forums and helping yourself. Your answer *is* out there if you search for "ParamValue/Limitvalue is not appropriate". Did you even try?

One example. There are others.

This is what I have in Triggers tab of the RoutineActivity stage: RoutineActivity.$ReturnValue<0>=1 That's your problem. You've already done the <> thing so there's no reason to do it again in your trigger code, never mind the fact that you chose to use the 'zero element'. Try this: RoutineActivity...