DSXchange

i have tried so much not getting suceess. Till now i came to know that the compiler we are using is not Compatible but is there any other way to solve this problem. Please reply me as sson as possible because it is urgent. You're running 7.5.2 and this is an urgent problem? Really? And you must run...

ArndW wrote:Sharali001 - this is a 2-year old thread that is on a different platform with a somewhat different problem than yours - it shouldn't be hijacked but you should open up a new thread with your problem. I trust one of the admins will do that.

Done.

And in case you are unfamiliar with the Chinese Proverb:

"If you give a man a fish you feed him for a day. If you teach a man to fish you feed him for a lifetime."

We generally prefer to teach fishing around here rather than simply hand out fish.

Put the entire WHERE clause in the parameter so you can leave it empty when you want everything. Or include "Package in ('x','y','z')" in the parameter string so you can change it to "1=1" when you want everything. You're also probably going to need to set the environment variabl...

qt_ky wrote:I've been using DataStage from version 3.5 (Ardent)

With manuals that still said "VMark".

(oh wait, that was 3.1)

How much RAM is in your client PC?

Interesting... don't remember that from what little I've read about it. The "run in the Optimized way" doesn't make a lick of sense to me but perhaps it will to others who have had actual experience with the BO option. I can however see how they would happily force you to license it everyw...

kripakarprasad wrote:the BO plugin used at the time of the optimized job generation

This. After that it's just a 'regular' job.

I added a URL to a support article on the How To of parameter value files, in case that might help.

Now I'm wondering what "making a call to an oracle DB" means here. I assumed sourcing from it but this could still be used for a lookup, if that's what you meant.

Use a Sequence job to retrieve the values in the flat file and pass them to the processing job as Job Parameters. Then the Job Parameters can be #bound# into the where clause of your source SQL so that you only pull exactly what you need each run. Have you done anything like that before? Another opt...

Talk to your DBA.

http://www.dbtalks.com/Forums/Thread/37 ... table.aspx

mario_j wrote:I know, this is a large protocoll, but maybe some can tell me what this means

Your official support provider.

Can you post the actual complete error message(s) you are seeing?

Are you not able to use the Stored Procedure stage for this?