DSXchange

A 5 minute delay in updating status or the log?

How about my 'thought' that seems to have been completely ignored? Did you check for a 'before job' activity in JobA? Get that card off the table if it isn't a factor.

asitagrawal wrote:What is combinational effect of check / Uncheck of the four options on the genral page, viz:
<snip>

How about you build a little test Sequence and see for yourself? Best way to learn is to do...

To actually answer the question that was asked, that was because the Sequence ran to completion without problem. The fact that the jobs the Sequence job ran had problems doesn't really bother it - unless you specifically tell it to be bothered. One way to do so is the option that DSGuru2B mentioned,...

I'm not going to code it all up for you, but here are the steps you'd need to derive that: * Get current date in any format * Replace Day # portion with '1' * Convert to Internal format using IConv * Subtract 1 from Internal value * Convert back to External format of choice using OConv That should b...

OMG it works. Actually if I set the update array size to 100 it works also. So it seems that they array sizes have to be the same for it to work? You sound surprised. No, they don't need to be the same per se. However, with your previous settings the sending of the Inserts to the database were bein...

Because it is one of Ray's patented Premium Posts.

Ok... then let me know what happens when you change your Insert Array Size to 1.

That's ok - I guess that would be the short version of what I said. Shane can pick his poison.

Keep in mind the fact that Oracle will happily update nothing. In other words, an update will only generate a reject event if the update itself creates one - trying to set a required field to null, creating a unique constraint violation, RI issues, etc. The mere fact that it updated zero records in ...

No. Have you read the Help on what it actually does? It 'splits' an Input string (one big field) into Output columns (many smaller fields) and only supports one link in and one link out.

All you need are two links from a transformer to your '2 odbcs'.

Sheesh... how did we get this deep into your issue without ever knowing what database you are writting to? Answer some questions for the record: 1) What is your target database? 2) What stage are you using? 3) Is the stage generating the sql or are you? 4) If the stage is, what is your update action...

That would be controlled by your Operating System, not DataStage.

If you truncate the target table and load the data this error should not occur I'd be careful about giving advise like this without qualifying it, especially for a newbie. We don't want people going around truncating tables just to solve unique constraint errors... unless, of course, that's appropr...

It's not about the Column size as defined in the job, per se, it's about the size of the actual data as compared to the target field's size in the database.

In other words, one or more of your column names are invalid. Make sure you've got the table name correct first, that's a sure fire way to generate this error.

Then start checking everything else.