DSXchange

That error message can also occur if an attempt has been made to kill the job processes using operating system commands. There must be processes (resources) existing for Cleanup Resources to be able to work.

The warning is only a warning; you have asked (implicitly perhaps) a Sequential File stage to preserve partitioning, but it must execute in sequential mode, and must therefore perform collection of data from all partitions into a single stream. This is not the problem. The error messages suggest tha...

Is there something else, perhaps another DataStage job, perhaps some other process. that has locked the Oracle table? Check with your DBA.

It was just an observation. The first time I encountered this error message that was the cause. When next someone is searching I had hoped to cover the extra possibility.

It may not be the first Transformer in your design, but it was the first one painted onto the design canvas. Comments in the code will tell you the name of the Transformer stage from which the code was generated.

vsi wrote:Does it affect the working of Datastage if i clear the status of jobs? i guess i used option 11 and now not able to log in.

Clearing one job's status file, or even a few, will not block login. There is something else awry with your project. What message do you get when failing to log in?

Only an upgrade or an updating of the account would make anything disappear from VOC, other than an explicit DELETE command. The project cleanup button (which has been removed from the Administrator client and from the DS.TOOLS menu) ought not to affect "Q" and "R" type entries in the VOC file. I su...

The parallel Aggregator stage seems always to generate dfloat output for numeric input.

It's not an XSLT error. The error reported is dsjob: not found which means that your PATH environment variable does not include the DataStage bin directory.

Just set the NLS_LANG environment variable appropriately.

You might like to investigate

mkdbfile only creates the data portion. You need a second mkdbfile to create the dictionary portion. This should be named according to the convention <dir>/D_aaa.hash in your example. Ideally you should also populate the dictionary with the hashed file's metadata.

Or, to avoid the EVAL

Looks like you may have some orphaned components - you should never delete from UNIX, since it does not remove the VOC entries. Execute the command DS.CHECKER to search for and remove orphaned components, and let us know if that has fixed the problem. If you can get exclusive access to the project, ...