DSXchange

Hmmm.... from what I recall, you can just type it in. May be wrong but worth a shot. That or there may be a checkbox that automagically sets it to "localuv"? Don't have any way to check from here...

Guessing this may help.

Resolved, it would seem. So what was the actual resolution?

No, that's the maximum size of a log entry. So, this is resolved or are you still trying to figure out what's going on? If you still need help, take a shot at answering my two questions...

What you posted is not the error but simply an informational message from DataStage that everything couldn't fit in the log message. What else was logged? What exactly are you doing in the script / sql?

zulfi123786 wrote:

vamsi.4a6 wrote:I increased the APT_BUFFER_MAXIMUM_MEMORY value from 3145728 to 31457289 but still facing same problem?

I dont think this would help as you are just trigerring the command from datastage.

It won't (and didn't) as the APT environment variables are PX job specific.

You do have to deal with them, yes, since the results are returned in a dynamic array.

After the regen, did you restart DataStage?

Transformer before then sum in the Aggregator.

EXE_CMD_CREATE_DIRECTORY.$CommandOutput<1>

Show us your syntax in the stage, how you "trigger the ksh script".

Is your Oracle client 32bit or 64bit?

Sorry, but you really need to ask a question and as part of that question explain to us exactly how / where you are getting the error in your subject. I'd also be curious what flavor of UNIX you are running and the "bitness" of your Oracle client is.

I'm assuming someone will be along that could help, but please keep in mind the fact that this is DSXchange, not PerlXchange. You'd be better off posting questions like this in a dedicated Perl support forum.

Any chance you can use it as a source and dump it to something like a flat file?