DSXchange

Currency fluctuation...

Failure to load shared libraries is typically caused by the shared library search path (an environment variable called LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH, depending on your particular operating system) not being set correctly, in this case not including the parent directory of dsdb2.so.

There is no way to change this mapping other than to change the mapping. The threat of a major security breach given that every disgruntled employee has administrator access should convince your Administrator to get it right.

I guess we need to know whether the migration is from version 7 to version 7, or from version 7 to version 8. In any case, you don't really need to migrate much of the repository - only wanted entries from configuration files such as DSParams and uvodbc.config. All the rest are created when you impo...

The version 7 repository is stored on the DataStage server in a proprietary database (called DataStage Engine, based on the UniVerse database). It is not DB2, or Oracle, or anything else.

That story changes once you move to version 8.

Can you please post the query and the data types of the columns mentioned in the query?

Check DataStage credentials in the domain management part of Web Console for Information Server. My guess is that all login users are mapped to dsadm.

Welcome aboard.

Does the job work properly? (That is, are data transferred properly?) View Data utility is not always a reliable indicator - use some other tool to view the source and target.

Welcome aboard.

You can search DSXchange for answers.

As a general rule, though, we do not like to answer what are obviously interview questions.

hellboy wrote:any way i am not the premium member.

That, at least, is easily fixed.

It can actually be more performant, in parallel job or with inter-process row buffering in use in a server job, because you split the load of reading from the load of parsing.

Actually (in version 8 and later) DataStage will do this automatically and invisibly.

CHECK the data before you send it to Oracle.

As you have already been advised.

If you don't send erroneous data, then the server will have nothing to complain about.

In my opinion, jobs should abort if there is an unresolvable data anomaly.

If the original problem has gone please mark this thread as Resolved

Today DSXchange is behaving differently from yesterday, though I am using the same machine, the same browser and on the same network as yesterday. Has any change been made on the DSXchange end? As far as I can determine no change has been made here. The symptom, and it's dashed annoying, is that the...