DSXchange

Not sure I'd call that "huge".

What database? What's the typical ratio of inserts v. updates, any clue?

First suggestion - take your actual "exporting nulls" error and search the forums for that exact string.

This might help:

http://www.dsxchange.com/viewtopic.php? ... ht=regedit

Umm, Arnd, both the hash marks and the parameter value being passed are there in the post.

You "skip" them using a constraint in a transformer (@INROWNUM > X) but there's a lot more to it than that in the PX environment. And only you can say if it will "give good result" if you do that.

They're not routines, they are interludes to routines or wrappers. Just like the routines themselves, double-clicking on them opens them up and exposes both the "source code" and any documentation as to how they work and/or are used.

As noted, what problems are you having with it? How much sql experience do you have?

So, since you can't "truncate for a particular date", how are you going to handle deleting the previously loaded data? Perhaps a Transaction Size of zero is on order so you get an "all or nothing" load?

Ah. It's always a "best practise" to add an active stage between any two passive stages. Granted, DataStage will add one if you don't (hence the IDENT1, IDENT2, etc you see occasionally) but sometimes odd inexplicable problems can be solved simply by adding the transformer yourself.

I made the silly assumption that the metadata is different across the 70 files. Otherwise, there's no reason for anything more than 1 job and a parameter for the filename. Or a fixed work file name and a 'before job' concatenation. [shrug]

Short answer is "skip them". However - static source? Meaning when you rerun it, will the 103rd record in the second run be the same 103rd record from the first run?

Sorry, but the only thought I have this late at night is "use meaningful stage variable names". How is anyone who comes after you supposed to follow calculations involving StageVar, StageVar1 and StageVar2?

Rea_Antony wrote:but nothing is being fetched from the source

Yes, I know, you said that already. You didn't answer the question - you've got a Varchar in the job *and* the database for this field and it "failed to convert" it? That doesn't make a lot of sense.

Errors are always thrown by the transformers as they are the active stages in Server jobs. What 'DataStage type' and database type is this "not fetched from source" column?

Database? Stage? Generated or user-defined sql?