DSXchange

Sure you can, but you are still restricted to the fact that you can only point to one Oracle Client in your Server. So there's really no reason to use the other stage. You can and it will typically work but it will also generate odd errors on occassion, depending on exactly what you are doing. Been ...

Why don't you have 'sequencer accessability'?

For someone new to DataStage, you are taking the 'harder to learn and maintain' job control path...

Turn off 'Automatically handle activities that fail' - a routine that does not return zero is considered to have failed. It's in the help.

You can't use 'both stages' in one job if you have both - they are mutually exclusive as noted in the documentation. Well, actually you can but the job won't run and you'll get all kinds of goofy 'put' errors. When you are dealing with multiple Oracle versions, you need to play the 'least common den...

Not sure exactly what you mean by 'blocks', examples might be good. Did you import the metadata for this file or did you create the XPath expressions manually? If you have repeating elements, did you mark the 'lowest level' as a Key?

SQL script in the Execute Command stage.

Not buggy, per se - but you are making it do more work than necessary. If you do not assert a sort order in the Aggregator stage, it has no idea what order the incoming data is in. It then errs on the side of caution and so needs to take all of the incoming data into the stage, order and then aggreg...

Would you be opposed to using an ODBC stage for this? It will support a link with a dummy column that is not bound into the sql and your user-defined sql can be simply 'TRUNCATE TABLE XXXX'.

Done that before as well.

Why do you need User Defined SQL? As you've found, that's going to cause you nothing but grief trying to bind things. The DRS stage when set to Oracle has two truncate Update actions: Truncate only Truncate table then insert rows Seems like either would work for you, considering you aren't planning ...

rwierdsm wrote:Then the sort in the aggregator, while it won't hurt, will be incidental.

Actually, asserting the 'sort' order in the Aggregator is required or else all your database sorting will be wasted.

Much mo' betta!

Look at the dsapi.h file installed under your DSEngine/include folder.

How do you propose to convert a character into a number? What are your rules?

That would work, unless they need to know how many rejects occurred... or would have occurred. That was my impression.

Thurmy - please edit your post. Wrap your indented code in 'Code' tags. Disable smileys.