DSXchange

The stage tries to insert, if the insert fails with error code (-1), it will then try to update. The issue here is. It fails on update as well. What happens if you do only update? Try to capture the record thats causing this error. See whats different. Does that value exist ? For debugging purposes,...

You can rate everyone's replies depending upon how helpful the comments were.

Use either Pipe or Ampersand.I was aware of the fact that its windows as ExecDos does not exist in unix. For some reason I though a semicolon should work. Anywho...

chulett wrote:Too slow.

Alas, my slow fingers.

Its a three time 'Yes' from Craig. Its stone written now.

Did you spot check a few fields in the flat file. Is the conversion correct?. Also in my initial input, ICONV for time should be "MTHS" instead of "MT" This conversion will only be successful if there is no space between seconds and AM/PM. If there is space you need to get rid of that space then.

Yes we can. Search the forum or read about shared containers and its uses in DS manual.

Its not against best practices. I use it all the time. But if the data size is huge, it might not be a good practice. Therefore it depends. But then again you should also have a cleanup process in place that cleans out files so that huge files dont just keep sitting there for months.

Sql Code 1403 means that the update record was not found according to the listprovided by Vincent. Is your key a char column ? What happens when you change that to varchar. There might be an issue of spaces with char field.

Return code for an aborted job is 3. While running the job, stick in -jobstatus so that the return code of the command will be infact the job status which can be read by $?

Also, search the forum, you will find a variety of shell scripts that does this for you.

Lookup_8,0: Ignoring duplicate entry at table record 1; no further warnings will be issued for this table Do an exact search on "Ignoring duplicate entry at table record" for the above error. And for the below error, do an exact search on "Delimiter for field ". One of those search results turns up...

Multiple writes to a hashed file is possible. Let your source hashed files go to either
- a single hashed file stage with the same hashed file name for each input
or
- 18 hashed file stages with the same name.

Its semi-colon seperated. There are more options as well.

...by reseting it from unix command

Try changing it. Also, since this is such a struggle, load it to a flat file, just a few records to see how it looks like. It should have two parts. The first is date in the format YYYY-MM-DD and second is time in the format HH:NN:SS. Both parts should have a single space in between them.