DSXchange

A deadlock in the XMETA repository? I would involve your official support provider.

If you need to do it the answer is simple, just assure they have unique names.

Apparently you can. Assuming this is something you are doing rather than planning on doing.

I would wager only one ever gets used and probably that would be the first one...

So, this is actually a Parallel job? Off we go...

Keep in mind the fact that it does say it is a temporary fix, ultimately you should "Install patch or upgrade to 8.1".

Link.TimestampField[6,2]

First, help us out by exlaining what "Invocation Id Expression" would be and what you mean by extract. Also, how are you planning on using this information?

The 'DataStage scheduler' on UNIX is cron. Enterprise schedulers are more robust, support dependancies and can schedule anything rather than just jobs.

Oracle supports a 'default value' but you need to not mention the column in your sql for it to be applied, if you specifically pass a null to the column it will be set to a null.

To me that means it is coming from your job, somewhere in there a default value is being applied.

Right, we had zero desire for any need to go back and modify old fact records for late arriving dimensions.

asaf_arbely wrote:Does any one know if it's possible to change default values of attribute in datastage stage

It's not.

Pull the plug?

Why would it be a 'bug' for a 32bit application to look for 32bit drivers, the only ones that it can use? Still, thanks for posting that solution.

If that was true then your [1,4] substring should have worked. Change your target to a flat file, include the timestamp and show us what you get.