DSXchange

Two can play that game, data.hari:

What sort of exceptions, please give an example and you'll get responses

royarellano - it seems that DS thinks your have an incorrect delimiter while you think it is correct. My money is on DataStage in this case :roll: What is the column definition for COLUMN_NAME, could it be VarChar(10)? Does the column have quotes around it? Could you post (in quote tags) your first ...

No, @NULL represents only one value, namely 0x00. DataStage server/BASIC has no concept of the SQL NULL value, but can represent its ASCII value.

Christina, if you search on "row too big for inter stage rowbuffer " you'll find 5 threads with the same topic. The first one suggests turning off row buffering to avoid this limitation, would that work for you?

Assuming you are not inserting and updating the same record at the same time or in the same run (in which case you'd need to commit on each row) you shouldn't have issues. While your approach is more efficient, you can also have the DB stage decide which operation to perform.

What sort of exceptions, please give an example and you'll get responses.

1 - No setting exists to change the TRIM behaviour 2 - When reading CHAR fields DataStage performs no modifiction of the data, if you have Char(10) then you will get the 10 character that are in the file. When you convert this character to a VarChar are you specifying a longer length or perhaps no l...

06:36:56: ExecRunServiusageSH (COMMAND sh) started
16:18:19: ExecRunServiusageSH finished, reply=0

What does this long-running shell script do? Could it return an error?

We just had that issue today, with over 30 developers suddenly enjoying a forced break.

Our Oracle XMETA had no space left and autoextend was (intentionally) turned off. The autoextend doesn't have to be on, but one does need enough space to store the metadata.

Project paths cannot be changed, you would need to delete the project in the old location and then re-create it in the new location.

If you look at your director log for job "sqRunMainFlow" what does it show? What have you changed since yesterday? Also, what is the dsjob -run command you are using?

8.0.1 doesn't allow one to change the logging behaviour.

Do all your files have the same format?

Just imagine that you use sequential .csv files in jobs, just as you would need to move those when migrating a DataStage project, you would also need to do the same for Hashed files. But they are not flat files, if you were to have a hashed file called 'MYFILE' you would have, by default, a subdirec...