DSXchange

I think there is some information missing that might explain this behaviour. Are you doing a straight load from table to dataset, and are you doing any sorting (implicit or explicit)?

The first problem isn't too tough, you need to apply the rule as the first and last characters must be double-quotes and the internal delimiters must be '","'. This can be done with simple left(), right(), and count functions in your transform logic. Once you have that solved, you can look up "pivot"

Have you changed anything in DataStage or on the server? Do you have other DataStage jobs that connect to this Oracle instance and are they working or also failing? Have you talked to your Oracle DBA to see if he/she can find something amiss in the database?

Phantoms are background processes, but I would suggest that you don't follow the advice and terminate these processes without knowing to which job they belong. By far the best thing to do is let DataStage take care of locks by enabling the deadlock daemon (you can search this site for references on ...

Can you explain what "server getting crashed" means? Does it mean that your job aborts or that the DS Engine stops? In either case, an error message posted here will go a long way towards getting a qualified response.

To take part of your command line, "-param prmDbSrcName=prmDbSrcName " means that your Oracle instance name is "prmDbSrcName" which I doubt is what you wanted to specify. What are you trying to do - use environment values, i.e. "-param prmDbSrcName=$prmDbSrcName"

No, I think that they are part of DataStage. I recall having had to clean up after processes at one site before, we wrote scripts to to the cleanup. I think it was because of network or system timeouts.

ray.wurlod wrote:I'm uncertain what the Heisenberg effect is - can you please amplify?

Sorry, Ray, I cannot do that; since it would change the result for others. But I do have a [live] cat in a sealed box for you....

Unfortunately the old approach of a UNIX backup is no longer sufficient with Version 8 as it has other components and metadata stored in the Information Server repository.

There are few, if any, good free materials available to learn PX jobs. If your site has PX installed then you can use the tutorial that comes with the product along with the manuals to "play" on a real system. Learning becomes quite difficult without access to a PX system.

Craig, "kill 'em all and let the big FNUXI in /dev/null sort 'em out" is what I say. The file unit 13 might just be a pipe that, while not closed, isn't communicating

Open up your transform stage details and set the compiler flags, including the "-O0" option, in the "Compiler Flags" line f the "Build" tab. I don't think that there is much of a penalty if you remove the optimization at the project level (through the Administrator tool), since much of transform pro...

I don't know where your problem might be happening, but you might think about using the debugger. Find out the last "good" output line and put a breakpoint on that value, then step to the next one and see if the data contents might give a clue as to the cause of your problem. Sometimes the debugger ...

DataStage telnet sessions that have timed out? Can you see what system calls they are doing (i.e. "truss -p 4392")? I recall I have seen lots of semi-defunct processes on a system, so think that these really are DataStage processes.

Probably locks of some kind. If you have a small project and access to root/dsadm, then shutting down and restarting Datastage might be your quickest solution.