DSXchange

Good question, didn't notice the dreaded "8" for the version number. Does this work differently now?

I'm not aware of any limitations or settings that would affect this, but I haven't done all that much with that particular stage. Need to see what someone like Ernie has to say when he gets a chance to stop by.

Hmm... try setting the Data Element in the XML Transformer to "XML" to keep it from translating things like that, see if that helps.

Build the simplest DB2 job you can, export it. Replace DB2 with Teradata, export it again. Compare. See if the difference between them is something you want to tackle in any kind of automated way.

A sparse lookup does not allow multiple reference links, as far as I know it still allows multiple rows to be returned by a link.

That tab is only active on a Windows server, it plays no role for UNIX.

I would google for something like "Windows ftp script", you should be able to find plenty of examples and help out there.

I would assume the same, seeing as how the Import first deletes the original job and then creates a new version (with a new internal number) when in brings in the replacement.

ArndW wrote:We didn't want to be child-killers, we just throttled them a bit; sort of like Homer does to Bart

Why you little...

Don't start them.

We had to do the same thing, just shows an installer problem specific to Itanium servers. And you may want to consider upgrading to the latest Oracle release - it typically is pretty painless when it's a minor version like that and they've released it for a reason, typically to correct problems in t...

Don't use the FTP stage which is metadata driven. Script an ftp session that goes an "mget" with the appropriate wildcard pattern. Talk to scripting gurus at your site, ftp scripts can be a little tricky to get right - typically someone there has already done something similar so this saves reinvent...

First you'd need to define what "sync" means and decide how you are going to capture the changes. The "real time" part is probably the easiest part of the puzzle... lay the foundation before you try to build the house.

Also note the same question has been asked in the PX forum:

http://www.dsxchange.com/viewtopic.php?t=122855

Don't be - there are all kinds of goofy problems you can lay square at the feet of particular Oracle versions that have nothing to do with DataStage. It may be as simple as using a different / more stable version of the client on your DataStage server. What exact 10g version of the client? Is there ...