DSXchange

So... have you not been reading the reponses? That guidance is there.

Not so much "already inserted" as "already commited" rows. Ideally, the Transaction Size should be set to zero for an "all or nothing" load.

Still, all posted advice still applies. And do let us know why you posted a select statement for your Oracle target.

SBSA_DW2 wrote:nope.. multi-category does not work. multiple definitions in a category does though
seems its going to be a manual process.

Correct and correct.

Instill some discipline in your developers. I've found fear helps... and a cricket/baseball bat.

Good catch, missed that little nugget.

Do you have a "tmp" directory at the root of the drive where DataStage is installed? Is it writeable for your user? Have plenty of space in it?

Then you're not really doing "load append" but plain old inserts. And the rollback happens when the job aborts, so you need to ensure that happens, usually via a Reject link set to abort after 1 row.

Please heed Ray's advice and learn how to do "ascii art" properly here. Without the code tags all white-space is collapsed out with your art smashed up against the left-hand wall. Edit your post and make copious use of the 'Preview' option as it won't line up quite like you expect, being a...

No, you cannot change the format to "whatever you want", it needs to match what's in the file to convert properly. Regardless, won't help here. And the OP has already reported success treating the field as a string.

That's not what you posted says.

Make sure you've supplied the correct schema, you are connecting to the correct instance and have select grants on the table.

Read the record as a single long string. Break out the first field (various ways to do that) and direct your output based on the content of that first field: 'CUST', 'COUT' or none of the above. Colum Inport and/or Filter stages should be useful here.

Use the Manager GUI, it allows the standard Windows multi-select. There's no command line option for this that I am aware of.

Correct. You could remove the word 'BASIC' from what you wrote and have a statement applicable to either job type. Reset is for status, compile... compiles. As in the 'executable', whatever it is - BASIC, C++, OSH, etc.

(as I cannot use it within the same job and expect a unique number) What makes you say that? :? I have read it somewhere in one of the blogs and also I learnt it from one of the folks I talked to here. The explanation that I gathered is, as it is the same process and the same state file is accessed...

vivekgadwal wrote:(as I cannot use it within the same job and expect a unique number)

What makes you say that?