DSXchange

Unfortunately the target system is a Siebel application, so I have no say as to the definition of the tables.

Wouldn't the same problem still exist, though? A column defined as Varchar(100 char) on a UTF8 database would import into DS as Varchar(300) and on a AL32UTF8 database as Varchar(400)?

We've managed to fix this problem by switching DataStage to use an Oracle 9i client (actuallly 9.0.1). I would suggest the problem was to do with the DS ODBC driver interaction with the 8 client. (This is on a dev box. Remains to be seen whether it is backwards compatible for all projects using the ...

I'm having a problem inserting into a Oracle 9.2 database from DataStage where the NLS_CHARSET of the database server is AL32UTF8. See below for the error message: JCTest1..Transformer_1.DSLink4: DSD.BCIPut call to SQLExecute failed. SQL statement:INSERT INTO SIEBEL.JC_TEST1(FIELD1, FIELD2, FIELD3) ...

There's nothing special in the routine.

I have found that I don't get the problem if I switch off row buffering. (It was set as the project default.)

Thanks,
Jeremy.

I have a very strange error that has been driving me crazy for a couple of weeks now. I have stripped back my job to the bare bones and it still exhibits the same behaviour. The scenario is this: A sequential file feeding into a transformer, followed by another transformer, feeding into a sequential...

Thank's for the suggestions. I've tried various settings for the Tracing level, but it doesn't give any useful information. Link tracing level = 32 (telnet data dump), which I expected to give me something useful didn't return anything. This is a Unix to Unix transfer, so I would expect it to be fai...

I've set up a test server job using an FTP stage to FTP a file, then process it using a Telnet after command. The FTP works fine, but the Telnet command always fails with TestFTP..ftp_3: unable to execute Telnet command 'Telnet After Command' no matter how I configure it. Does anyone have any tips o...

Having a reject link with no constraint has the same effect - no records written to the error file.

I've tried various other combinations of constraints and get either no records or all records written to the error file.

Regards,
Jeremy.

When inserting into an ODBC stage I can write rejected records to an error file using a Reject link and a constraint that looks like link.REJECTEDCODE 0 -- this works fine. When I try to do the same thing with a DSDB2 stage it doesn't work -- even though DB2 fails to insert some records, they are no...