DSXchange

You are not the first and will certainly not the be last to get hit by that UNIX cp command quirk.

No worries - you can copy the D_... file and the directory; but make sure that you also include the hidden file ".Type30" inside the directory otherwise it won't work.

I think you need to increase 2 environment variable values:

$APT_MAX_TRANSPORT_BLOCK_SIZE
$APT_MAX_DELIMITED_READ_SIZE

There should be no difference between a designer and a director run. The only likely source is that you use different parameters when calling up the job. Does this always happen or just sometimes? Can you make a copy, then replace stages with "peek" and recompile/run from the director until the erro...

veera24 - in order to see Ray's post in its entirety, consider signing up for a membership

I think you are referring to the "transform" functionality in Server jobs, where a 1-liner piece of code can be written centrally and used in many jobs; when this code is changed the new version will be used in jobs after they are recompiled. I just tested to see if this could somehow work for PX jo...

keshav0307 - that might take up needless storage; I think we get the picture. But I would like to know which limit you have reached - that of the DS-Window or some Oracle limit? How long is your SQL? rajkraj - can you see things to strip away in your SQL? shorter column names? schema.table.column ty...

Hehe, looks like the 0 length guess was good. I've done that before, by mixing source and target directions in those tricky UNIX commands.

At least 0 length executables are easy to debug...

The BASIC transform stage is usually not in the palette, you can find it in the Stages -> Parallel -> Processing -> BASIC Transform category (names might be a bit off, I'm doing this from memory)

The original poster has the option of using a BASIC transform stage and calling his/her original function from there. The downside is performance, of course. I don't think that it is the responsibility of IBM to do this. This is like saying that if a company produces both a COBOL and MODULA compiler...

In server jobs you have a much more powerful and versatile set of functions, ICONV() and OCONV() which can pretty much convert any date type you can imagine. You've specified the output, but what is the input format?

Could you add a peek of all rows between remove duplicates and lookup and manually check row 2257 +- 1?

All of the functions exist in PX Transform stages, so you could emulate this function using stage variables and the same string functions. You would need to write c++ code if you wanted to call a function, though.

Did you delete the original installation completely (uninstall program, delete directories & clean up registry) before re-installing? If not, you should try a clean delete and install.

Remember to allocate even more swap space than you normally do; as Solaris has the strange method of allocating swap space when a process request virtual memory.