DSXchange

Somewhere in your job design you have a VarChar or Char column with no precision (size, length) defined. You have to find it and fix it. It may or may not be in the Oracle Enterprise stage.

Have you read the Orchestrate Operators manual? It's more comprehensive.

Even IBM's software solution is largely wetware based, plus you have to agree to your jobs being "off-shored". Other consultants also offer this service.

Cache sharing requires other things to be configured. You can read about these in dsdskche.pdf. Meanwhile do not enable cache sharing - the separate processes will create separate caches and, design being appropriate, both jobs will work OK.

There is no single job executable. There is an osh script (suffix ".osh") and a shell script for running that (suffix ".sh"). There may also be compiled C++ components linked into libraries (suffix ".o") or shared objects (suffix ".so"). But, when it all boils down, what gets executed is none of the...

Put a Column Generator stage on each input to the Join stage, and use it to generate an integer sequence. Allow appropriately for partitioning if running in parallel. Make sure you get the same sequence on each input. Then use that as your join key.

And, if none of those works, assemble your long query into a stored procedure and call the stored procedure from DataStage.

Prefer type 19 if the names are going to exceed 14 characters in length.

Welcome aboard. There is no SQL Server stage per se, but you should be able to see an MSOLEDB stage. Ask your administrator if it has been installed. If it is not there, it can be installed on the server using the DataStage Package Installer (available from the Start menu on the server). You will ne...

Post your question in the correct forum is what you can do. This forum is for server jobs.

This may mean that one of the plug-in (= optionally installed) stage types is either not installed or not registered in your new project. This may be the case for a server stage type or a parallel stage type, depending on in which job type you encountered the message.

I'm not sure about 7.1 but in 7.5 you can change licensing on the Licensing tab in Administrator client.

Search

This has been answered a couple of times recently, and lots of times - bajillions of times, even - in the past.

I was thinking about licensing, rather than installing.

Study the error message - get everything you can out of it. For example, what are these characters, and why can't they be converted?