DSXchange

Setting up is very straightforward, and is managed by the installation script. Essentially you have a separate project (by default called VERSION) in which are stored version-stamped copies of the objects from your actual DataStage projects. The Version Control tool provides an interface through whi...

It depends on which user is used to start DataStage.

Please mark this thread as Resolved using the green button at top.

Right click on the SET icon in the Repository toolbar and choose Provision All. Or, as you're selecting the rule set within a design you can do the same thing.

Not really. I guess you could create synonyms in the database. But DataStage can't deal with column names that are numeric.

Come on, look at the value that was rejeced!

Then enable "first line is colunn names".

Import errors at offset 0 are almost always due to this property not being properly set.

Row buffering must be on if the Link Collector stage is used.

Always use the right version of updater.jar - the one that ships with the software. For example, version 188 does not work installing FP1 client - it hangs - you need to use version 164-176 (from memory) - the one that ships with, or is linkd to from - FP1.

Projects are created from the (Administrator) client. Therefore su is not an option.

Usually this message stems from failure to provision all files in the rule set.

The second person personal pronoun in English is spelled "you", not "u". U is one of our posters. And it's YOU (or your aborted job) that locks the rule set. If the deadlock daemon is running, the lock will be released automatically in the fullness of time. The trick is to creat...

It's an activity variable. Search DSXchange or the manuals for details.

Because Oracle stores all dates with a time component.

Oracle is... different.

Depends, but almost certainly not. A sequence spends most of its time uninterruptably asleep waiting for activities to finish. If you check the system time after each activity finishes you can direct control to an "ending" path. The more complex the sequence, the more additional activities...

I do so hate "we heard", particularly "we heard somewhere". Please cite your references so we can judge their provenance. Each reference input to a Lookup stage consumes more memory, because the data set associated with the link must be fully loaded into memory. But this will onl...