DSXchange

What stages do you use in your job? If you disable buffering the job will run slower but use less space. Are you using sorting?

The most common cause we have seen for this error is when a REINDEX is done while the project still has users logged into it. Have you done this? If so, just ensure that no users are logged in and REINDEX.

Do you have your auto-purge enabled? That has caused some issues for me in the past when multi-instance log details have disappeared on me.

The error occurred in the DSD.RUN program, not in your generated code. If you know how to get to the TCL prompt, then you could try "VLIST DSD_BP DSD_RUN.B" and post 15 lines before and after 2156 and someone here might point you at the possible cause. Since it is a DataStage program, it c...

The error occurred in the DSD.RUN program, not in your generated code. If you know how to get to the TCL prompt, then you could try "VLIST DSD_BP DSD_RUN.B" and post 15 lines before and after 2156 and someone here might point you at the possible cause. Since it is a DataStage program, it c...

Talk to your DBA and have him/her look at the query and costs; most likely the query is doing an expensive or even a full table scan. Setting indices and/or other options should speed this up significantly. Also, if you use only a couple of bytes per row then even a billion rows would fit into memor...

You probably have a VarChar2 data type, which does get loaded with trailing spaces. Look up the use of the environment variable APT_ORACLE_PRESERVE_BLANKS and set it so that the spaces are preserved

Try clearing out the contents of the &PH& project subdirectory and re-running the job, then looking at the text files to see if there is additional error information visible.

This would be the GNU C-Library, but you will need to post the complete error message in order for anyone to make a suggestion.

Have you tried resetting the job then looking at the "from previous run" entry in the director log? This might provide additional information.

Without additional information, such as the complete error message and code, you won't get a qualified answer. This is analagous to saying "my car won't start". Also post your configuration file. Is the machine heavily loaded or underpowered?

I am not sure what you mean with Q1, but the answer to Q2 is "no". I would strongly recommend enabling the lock daemon and setting the time down from the default 15 minutes to something more acceptable to your site. Once you enable it, when you get a locked out job all you need to do is to...

The job should fail, unless the warning is such that it occurred and then was corrected automatically upon retry. Note that the message was a "warning" in your PX job. Was the result from the PX job correct or not? If not, then this is certainly a bug.

Hello Steve, there is nothing fundamentally different in how nulls work that I'd noticed before. I trust that both the job metadata as well as the database definitions are nullable for all those fields and are identical with each other, but I'm sure you've already double-checked that. Can you make a...

You need to run "MyJob.ID1" and "MyJob.ID2" if you want them to run in parallel, you cannot run two identical instance names at the same time.