DSXchange

They are equivalent and really shouldn't case a problem. When you generate the XML Output, do you have the 'Data Element' column set to 'XML'? My understanding is that data element type is responsible for making those 'safe XML' substitutions. So, if it says XML make it blank... or perhaps vice-vers...

Then (in a nutshell) you should be able to leverage the checkpointing and the ability to 'Automatically handle activities that fail'. Between those two and the Exception Handler you should be fine.

What exact version of DataStage?

Call Support. They will have to make the patch "available" to you and the specific ecase number helps them know which one you need.

kumar_s wrote:Is it possible to get the patch released for an ecase which is not created by us.

Of course. Anyone with the same issue can get the patch.

This is a known problem and there is a specific patch to fix it. Reference ecase 72758 - it corrects this issue in 7.5.x2, 7.5.1 and 7.5.1A.

1)We trigger it from DataStage director. Explain exactly what this means. And let me clarify something I said. When I said 'by user' when mentioning Director defaults, I meant per user installation - per machine the client is installed on. In that sense it doesn't matter that you 'always use admini...

It seems like they might have, Arnd. Are you saying the production jobs are run from the Director? Meaning you've got them scheduled via cron? Keep in mind the fact that Director defaults are stored on a per user basis, so could be different from person to person. So the behaviour could depend on wh...

How can you have a Varchar in a fixed width field file? Change it to a Char.

Some days, yes. Especially with a prolific poster like yourself, gives one alot of hits to wade through. Just trying to help out our fellow forum dwellers.

Ah yes... that post, I remember it well. Thanks.

The fist thing that struck me was that it could be something with the date formating. Does oracle interpret :MI and :SS as variables? No, not when they are quoted and in a TO_DATE like that. This smells like a bug to me. I'd suggest you delete that OCI stage from the job and add it back in from scr...

And you can go back and edit the title of your post, if you like. A Sequence job will pass whatever Run/Warn limits it is started with to all of the 'child' jobs it runs. How was the Sequencer job started - from the Director? If so, check your defaults there - click on Run and switch to the Limits t...

Sorry Mr Kim. Can you post a link to the SQL that you mentioned so us poor slubs don't have to go hunt it down?

Then you've got yourself a wee bit of a Catch 22, it would seem. Unless I'm mistaken, doing a dirty read should just mean that you would see the state of any transactions that are 'in the air' as their 'before image'. You wouldn't see the result of anything actively being changed until the next time...

I don't use the ODBC stage all that much... is there an option to do a 'Read Only' or dirty read type query from the source database? As you mentioned, that may solve this issue for you.