DSXchange

Those are the names given to 'invisible' transformers the compiler adds to your job between passive stages when you don't put them in yourself. That was the second one in that job.

It's basically just your normal if-then-else, it's just that the if side has a self-contained if-then-else inside it, one that resolves to true or false.

Right... something that Oracle would have told you if you ran that same sql in something like Toad. And that's something else you're going to have to contend with - DSExecute returned a zero simply because it was able to run sqlplus, it doesn't care that your SQL failed. From what I recall, I believ...

AND hope your DataStage server and Oracle target can handle that many simultaneous PX jobs / connections.

Use double-quotes for your strings so the single quotes in the insert statement don't cause you grief. And again, make sure your parm variables are not inside your strings but are concatenated into them so they get a chance to resolve.

As noted, just load the date as is, you are wasting your time and energy doing an unneccesary conversion. Your problem is leaving the 'to_date' parts exposed so DataStage tries to interpret them and fails. Keep everything inside your strings as you build Cmd3 except for the parameter values you want...

Now... if you actually mean you want to try running a Job Activity three times in case the job (not the Sequence) aborts, that is perfectly feasible. Still won't need an Exception Handler for that, the Start/End Loop stages will get you what you need.

If your target is Oracle, there's absolutely no need to 'convert' that date format, simply load it as is with the appropriate TO_DATE mask. However, you can't simply use DSExecute to perform a sql INSERT unless you're not showing us critical (but missing) pieces of the puzzle. You could use sqlplus ...

What have you tried? If it helps, you'll need to split the date from the time, convert both separately and then stick them back together.

You'll need to launch the job from the command line using dsjob and then pass the parameter value in at the same time using the -param option. That or use Execute Command in the Sequence to run the script and then use the its $CommandOutput in the parameter value of the job's Job Activity stage.

Would need you to post something more like an actual error first...

So did I but I couldn't find what I was looking for... so had to go trawling thru the 'dsdesign.exe' posts once I remembered what executable one used for this.

Saying the exact same thing again doesn't go a long way towards changing our understanding. And my same answer still applies. If the Sequence aborts, it is dead so nothing inside the Sequence will help rerun it.

Then you need to do a more thorough uninstall it seems. See if this helps.

tanaya.deshpande@tieto.co wrote:sequence should run three times in case it aborts and after 3rd time it should stop

Can't be done with any stage inside the sequence. That's something your external job control will need to handle.