DSXchange

All errors in the 81xxx range are RPC errors. Execute this query to decode:

Would you be prepared to try using an Enterprise ODBC stage, just to determine whether the symptom is database related or client software related?

No reason not to use stage variables. You just need to have sorted by the entire composite, and use stage variables to assemble the current and previous composites for the purposes of comparison. Or compare the individual components and combine the results (OR the "NE" test results, for example).

Control Panel, System applet, Environment

You need to reboot after you've changed anything here in order for the changes to take effect.

In DataStage you handle the date and time components independently. Dates prior to the reference date are stored/processed as negative integers; after the reference date as positive integers. Because there are no data types in server jobs, there is no necessity to have an actual Date data type. You ...

While a job is running its phantom (background) process redirect their output to files in the &PH& directory in the project. If the job aborts, there is no possibility for these to be transferred to the job log. When you reset a job any such information (unless innocuous, such as "started, e...

If the input value is invalid i have to abort the job Nested Condition activity to detect the invalid value triggering a Routine activity that invokes DSLogFatal. Better, if you have 7.5, is to use a Terminator activity ahead of DSLogFatal, to send "stop" requests to other running jobs. i have to d...

I have definitely used the Client Switcher utility (precursor of MCM) in a 5.2 and 7.0 environment, successfully.

How many columns are defined on the input link to Agg01?

How many columns are defined on the output link from Agg01?

How many columns are defined on the other output link from Agg01?

( Optional: What are you trying to achieve by aggregating aggregated data?)

If you have recompiled the job, the "from previous job" information has been purged; it is no longer accessible.

This error means that DataStage found 71 columns in a row, whereas your job design has only six columns defined for that link. Can you please let us know what stage types you are using in your job design, and how they are linked together? One place this can occur is where reading from a sequential f...

You get all patches from/through your support provider. This may or may not be the same as your vendor; it depends entirely on the arrangements that you (or your site) have made.

The control file is the file whose name ends in ".ds" that you enter into the Data Set Management utility. In your case, this appears to be D:\target\NewFinance.ds Its schema has the 30 columns that you showed in red. That's what's in the Data Set, you will need to find the job that populated the Da...

When you reset the job is there a message "from previous run..." in the job log? If so, tell us what was in that.
(If you recompiled, rather than reset, you will have destroyed this history.)

It's an Oracle error.

Get to the server and type oerr ORA 900 to find out what it means.