DSXchange

Is it just me?

laxmi_etl wrote:I copied them in the admin tool, but its not refleting in my jobs.

Explain what both of these statements mean. Let's start there.

You'll probably find that you need to UUENCODE the attachment...

ray.wurlod wrote:NVLLVS ANXIETAS

Cvte...

Obviously, you can do pretty much anything with a big enough X - lever, server, whatever. Just wondering how practical it would be, that's all.

Just do it. Which part is throwing you, the 'remain same' part? That's simply where you set the value of the stage variable to itself.

ps. That's a hint... use a stage variable for this.

There are many factors that can effect this. We'd need to know all kinds of gory details about your job, hardware, network, etc before any conclusions can be drawn. Question: Are you saying the manual direct-path bulk load step actually takes 29 minutes? Or that's the total time to build and possibl...

for some reason job aborts with the same row out of sequence error there also even if i remove the sort stage and relied on orderby clause. Bottom line - it aborts with a 'Row out of Sequence' error because (oddly enough) your rows are out of sequence. Whatever order you are sorting the incoming da...

All these terabytes flying around in '1 or 2 hours maximum' using the Server product? Interesting...

Ok... now we're resolved with no resolution posted.

To help anyone searching here who has a similar problem, can you please post your resolution to this issue?

I'd be curious as well, but can pass along why we've done something similar across our project. We have certain lookups of 'core' reference data, the kind that should never fail. On the off chance one does fail, there's no reason to carry on and process anything else, no reason to be subtle about it...

Yup... and if it is installed elsewhere or you are using something other than sendmail, then your error message tells you what to do about it:

Please check any paths in the following command file are correct, and if necessary adjust the 'dssendmail_template.txt' file in the project directory.

Generally, there are no prerequisites to using the stage, you just drop it in a job and go. Should work just fine out of the box. The following parameters in the call to DSSendMail were not mentioned in the file 'dssendmail_template.txt': server Ignore this, it's a perfectly normal message from the ...

No... that would just select the highest job number issued so far. More than likely, that will have very little resemblance to the actual number of jobs in the project... unless you've never deleted any jobs or imported jobs into the project that already existed.

In other words, it worked just fine and it's Operator Error.

As noted, don't schedule 'the job'. Schedule a small script that looks for the files and trigger the job(s) based on the result. Use an Enterprise Scheduler if available.