DSXchange

Nothing unique about accessing a 10g database with a 9i client, we do that "all the time". Now... I specifically mean as source and target, we do not have 8 dot anything so are not using Oracle in that manner, if you mean for your Repository database.

#DIRNMAE#? What exact 7.x version do you have? Before 7.5.x there are known issues where parameters are properly expanded in the job's log but the actual command run leaves in the parameter names and hashes. For example, you put "csh #DIRNAME#/#FILENAME#" in the stage and it logs the fact that it ra...

Yet another wrinkle - will other apps or jobs also be generating keys for these tables at the same time? Another major technique choice factor.

Thanks for the information, Ray. Now I just need to decide if I really want to go through with this exercise.

That's probably the best approach. Another is a 'pre-check' and then skip running the job if the query returns zero records. Personally, zero byte files don't bother me in the least.

Try using something other than a comma for the delimiter - like a tab (009) for instance.

Doesn't work that way - it will always create the file.

Not, it's not an issue per se. It will effect the performance of the job but you'd have to decide if the performance was 'acceptable' with it set to 1. The root cause will require you to provide a great deal more information than you have so far. However, I'd guess that it is related to how much inf...

Guess you haven't picked up my PM yet, Andy. At least I tried to keep things hush hush and a little more covert rather than a public correction.

There's typically more to these kinds of issues than just the array size. However, try dropping it to 1 and see if that helps.

For Server jobs? I doubt they would have any effect.

ps: 7.5x2 was a special Windows only release. You either have 7.5.2 on UNIX or 7.5x2 on a Windows server. And if the latter, then I suspect you actually have a PX question...

I'm curious if anyone has done this before and if there are any hidden gotchas. Specifically... I have an old Version Control project that I want to put out to pasture. Rather than just create and use a new one, I was thinking I could play a little game. Create a new Project of the same name with a ...

You might want to clarify why you think you need to 'wrapper' them... or do you simply mean 'call'? That being said, I don't believe there is a 'best' or 'better performing' language to use on the calling end. As to your last question, you can only 'retrieve' whatever the job has been programmed to ...

Well, that sure gets an honorary membership into our Hall of Very Odd Requirements. While you may be able to limit something based on a record count, no clue how you do the same for 'source size' unless you compute the average record length and turned that into a record count limit on a case-by-base...

Where did anyone say anything about doing so on a Project-wide basis?

Check the Performance tab of the job, it can be enabled there for the job in question.