DSXchange

Does anyone still have the PDF files that used to be on these links? http://www.ibm.com/developerworks/data/library/techarticle/dm-1207configtuningdatastage/index.html?ca=dat http://www.ibm.com/developerworks/data/library/techarticle/dm-1205datastageopsdb1/dm-1205datastageopsdb1-pdf.pdf http://www.i...

I have not personally seen that either, but then again, I'm not a developer.

Try doing a repository refresh, then look at the value.

Well, the tool is not made the way you envision it. An ISX file can be located anywhere during it's load process. The contents once loaded into the tool, are no longer dependent upon the presence of that isx load file, meaning you can deleted it. The content of your DataStage repository COULD contai...

Well, like I said, I use an ISX file not a package.

I also don't have enough info as to how you had set up your environment.

Do you have a funcation authfile?

message me privately with the full command syntax you are using.

Send me the full error message as well.

We don't use packages here, we simply use isx files. Here is what I do to get a list of what the ISX contains. shell script command: jobList=`$DSHOME/../../Clients/istools/cli/istool.sh import -domain $host:$port -authfile /$userName/.datastage.authfile -archive $isxFile -preview -datastage "$h...

Might want to double check your version of python on the host, and look at your default system settings for user id resources. the "ulimit -a" stuff. Make sure your file handle quantity is up to snuff. Another gottcha I found was the "nosuid" setting on the mounts (see /etc/fstab).

Is your environment set in a grid where the nodes get distributed to different hosts? Or do you have a consistent hard coded APT file?

sometimes during a migration things hiccup and it's sometimes best to simply make a new container from scratch. I would rename the existing container. Create a new container (not a copy of process), and drag new stages onto the canvas and repolulate with the desired logic. Recompile container, (forc...

In your shared container, there must be some code (basic?) that is making a call to open a project/job.

Can you show us what you are doing there?

Well, is your environment the same as it was before? (stand alone host vs grid or cluster)

Are any other jobs broken or just this one?

Can you show the code that actually loads the other project code?

Do you have to validate each row or does a "sampling" suffice? You can extract from a table (based upon keys) sort the data and then instead of dumping to a sequential file all of that data, you could output a checksum value. Then just compare both checksums. Another option is load system ...

If there was a command like that it would be "root" associated.

(The Australians will get the joke.)

===========

Please explain what you mean by creating a user.

Do you mean granting access to a user to a particular project and assigning a role?

You could install two instances of DataStage on the same server and have them log in to their respective version. Or you could simply tell your customers that "In order to lower cost of ownership and to obtain a lower end cost for you, I have placed your project upon a shared resource. Capacity...

Ask the DBA if compression was introduced to the database when you went to 12c.

Why compile objects on your target hosts when you can deploy the executables in the isx file?

istools.sh should be used to import/export your jobs (isx format) via the command line.