DSXchange

So you want to reset a job sequences run by a master sequence? The same rule applies. The same option of "Reset if required" can be used. But beaware, if these sequences are "Restartable" then it resetting the jobsequence will defeat the purpose of a Restartable sequence. You wouldnt require to rese...

You dont need a routine for that. Read Vincents FAQ Entryfor that.

Whats different? The system name might be different, along with some other environment variables. But the crux should be the same.

Depends if you have that coded in your control.

Depends if you have "Reset if required" as mode of execution inside the job activity.

That means your extract is fine. The bottleneck is inside your job design. Now give us more info on what your doing, what transformations you are using, how many stages are there etc etc etc.

He never mentioned anything about any target OCI stage, did he? Thats why I advised to keep a flat file or anything for that matter.

Have a stream coming out of OCI stage into the transformer and then from there to any flat file. Provide the constraint inside the transformer as @FALSE so that no rows get written to the flat file. Run your job. This way you will find out where is the bottleneck in the performance. The extract rows...

What is the error you are getting? Make sure there is no main() function in the C function. Compile it with options provided in APT_COPILEROPT environment variable.

Try the following

No it wont work there. I am sorry for misleading you. Only macros work there. You will have to do it as Ray advised in a sequence job by passing it as a prameter. If you dont want that, the easiest way would be to do it in after job subroutin ExecSh. mv edw/devel/SO_SN.txt edw/devel/SO_SN`date +&quo...

Increase the array size to say 500 or 1000. Prefetch memory to the same. See what happens.

Give it as the file name in the sequential file name. But beaware, if the file that you create is going to be used by other job then make sure your cycle finishes the same day. If you midnight crossovers then it will be a problem. Thats why its safe to rename the file afterwards. More like make a co...

What are you getting these warnings on your second run? Try to fix it rather than ignoring it and finding your way around it. Inside the job activity you have run option as "Reset and then run" or something to that effect. Choose that for the 7th job.

Make the columns you want to compare, as keys. Apply all rules of keys to these columns, like partitioning on it, sorting etc.