DSXchange

You'd need to write your own looping job control as I don't see a Sequence being able to handle this gracefully unless you are willing to string 70 jobs together in a row. Another thought, a job that reads the filenames in from a flatfile along with the name of the job that processes it and calls th...

Suggest you start clicking... 7.x is a one-at-a-time world.

It worked all the other times, too.

Those zeroes are not significant. You have no control over how the data in a NUMBER field is stored internally in Oracle. You are arguing about an external representation, which is strictly an artifact of how you select the data. Try this: select to_char(YourField,'99999999.99') from YourTab...

Ken? Is that you?

Again - what issue? Did the data not load or otherwise generate an error? Or does it just not look the way you'd like it to when you select it back from the database? If the latter, that's just an issue with your select, not the load. That's the difference I'm trying to see if you understand.

What "plug in"?

Supports 10g.

What kind of "code" are you asking about when you say "DataStage 5 code"?

You don't have a problem. Seriously, what makes you think you do?

Sure, but there's no point for a NUMBER field. They aren't significant and Oracle doesn't need them. If you want to see them when you select the data back from Oracle, use an appropriate TO_CHAR() mask but worrying about that during your load is a complete waste of time. Or is this going into a VARC...

Suggest you let us know what your target is. If we're talking sequential file, then in spite of what you wrote the FMT function *is* the answer. For a database or anywhere else where those zeroes are not significant, don't even worry about doing this.

So, I'm guessing you think this would make a good FAQ and would like to discuss creating one? If not, please post this question in the proper forum based on the job type - in this case the PX forum.

Unless you've got the previous version stashed off in SCCS or some other versioning / source code repository.

What stage are you using?

Don't use it. Those combo actions are a crutch IMHO, one that lets you lean on how easy they are to setup at the expense of speed. Prequalify updates v. inserts. Split your processing. Use dedicated insert and update links.