DSXchange

However your business rules (business analysts) determine. It's not your problem: you highlight the deficiencies in the data (ordinarily with a profiling tool such as character investigation or Information Analyzer) and require them to make the decision. Typically you will also create a note in the ...

I don't know. Many people here ask questions about how to force jobs to abort. To me that's anathema. So it's my personal best practice to create jobs that don't abort, even though that may require more thought than just cranking out the code. Deadlines? Pah! You will spend less time doing it right ...

Is JobMonApp running or disabled? Are you collecting performance statistics when running from Director?

There are three considerations. One is your commit interval. Array size should not be larger than commit interval, and rows/transaction should ideally be a whole multiple of array size. Second is related. If you are using auto-commit, or if you require accurate reporting of row errors, you need to s...

Welcome aboard. All but the first in the LIST.READU output are "administrative" locks, which is why they don't show up in Director. The four tell you that you have two connections to the sample project, both from the same client (69280549-CB9F-4456-B5F6-1D9FAB62030A-IBM-L3CGT6H) and give t...

I'm not quite sure exactly what is meant by "Oracle operators" Andy - can you clarify? Oracle operators are the Orchestrate operators that deal with Oracle, such as oraread and orawrite. You see these mentioned in the "modules loaded" event in the job log. And in the score, of c...

Parallel jobs (at least up to the current version) are notoriously bad at handling embedded quote characters. Server jobs manage it much better.

Disable RCP to see whether that resolves the issue. If it does, try to discover why the additional, unspecified columns might have raised an interrupt signal.

You also have to assign DataStage Developer role using the DataStage Administrator client (logged in as a user whose suite component role is DataStage administrator).

I disagree. If jobs finish OK then files on scratchdisk should be cleaned up automatically. If jobs abort then the files may be left there, and would need to be cleaned up manually. This is one of many reasons why I try to create jobs that don't abort.

Permission issue on "resource disk"? Are any error messages logged?

The Oracle log file may be on the scratch disk defined in your configuration file.

Classic fork-join design with downstream filter on count being equal to 1 or greater than 1.

The "best" solution involves using a Standardize stage with the COUNTRY rule set. Downstream of that use a Filter stage or Transformer stage to separate the records based on the ISO country code added by the Standardize stage.

Welcome aboard.
Can you please post the full detailed text of the error message, and the stage type that threw the error?
If necessary (if the operator is APT_CombinedOperatorController) disable operator combination before re-running, THEN get the error message.