DSXchange

YOU do the needful, which is to disable operator combination so that you can determine accurately the source of the error.

Constraint expressions.
InLink.AS_LOCATION <> "D" (regular output)
InLink.AS_LOCATION = "D" (reject link)

If you have Version Control then you have its manual. It's all on the CD.

The entry for uvodbc.config is essentially correct. <SEVER_NAME> (sic) is the Data Source Name. You said that you had defined a DSN, which is why I assumed that you had already installed a driver - you can not define a DSN without one. Yes, you need to have a UNIX-based ODBC driver for Microsoft Exc...

You didn't mention a Sort in your original post!

Well done on resolving it yourself.

Have you created an entry for your DSN in the uvodbc.config file in your project?

PUT such a constraint on the output link.

Or it may want semi-colon (";").

Folder stage is not an option when file size is too large. Don't have exact figures on that ready to hand - if, indeed, the limit is documented at all. It has to put the entire contents of the file into a single field.

It's stored in the DataStage Repository. We don't have complete information as to where, however it can be retrieved from the local DataStage Repository. There is a separate table there for each job's log. Why do you feel the need to replicate that?

Welcome aboard. MetaStage is a separate product and separately installed and licensed in version 7 and earlier. The vendor has a training class on the books, but given that MetaStage no longer exists in the current version (8.x) they are unlikely to present it without sufficient demand. I am unaware...

What are the data types in the Oracle table? Is the date format correct for your Oracle instance? What is the SQL being executed (this is reported in the Oracle stage)? I use this oracle table CREATE TABLE TBablexx ( T_ID NUMBER(8,2), T_DATE DATE ) Three questions, one answer. Your problem is at be...

Show us your code, especially that part that assigns the value to UnixCmd variable.

mikegohl wrote:I would recommend you open a case with Oracle. I'm sure you are not the first customer that has run into this limitation.

I take it you mean Oracle as the owners of PeopleSoft?

Parallel jobs don't handle this. You could solve it by pre-processing the file (for example using sed or awk command) to convert the double double-quote characters to something else, then converting these back to single double-quote character within the job.