DSXchange

You need to have your EMC disk array monitored a bit more. Even though the actual physical channels are not shared the central cache, which makes the SAN so efficient, is shared across all users. So you might have your I/O being flushed out of the EMC cache, thus slowing down your I/O. The method of...

The error message shows that the data it is reading is the name of column - perhaps the first line of your source contains column names and you haven't specified that and this is the first non-string column and is therefore giving the error.

Please check up on your column definitions, you can specify "column contains delimiters"

Arun, this is a common error when your database is not set up for the type and size of job you are running. You should talk to your DBA about the rollback space set up for Oracle. A quick workaround is to increase your commit frequency in your DataStage job; but if you feel that it is set to good si...

Do your jobs that don't work have any characters in their names that the UNIX command line processor might interpret incorrectly?

As per the previous descriptions, a shared container is copied into a job at compile-time. The shared container itself is not used at runtime, since it's links and stages have been duplicated and copied into the actual DataStage job. Since at runtime there is no such thing as a "shared container", i...

As Sanjay has already mentioned, the gain is potentially in design-time because of reuseability but they have nothing to do with performance gains (either in PX or in Server). Shared containers are actually loaded into the job when it is compiled, so the resulting object code is going to be the same...

Vijay, the VOC and catalogued name have nothing to do with the questions you have about this routine and it's use in a sequencer. When a function or routine gets compiled it is "catalogued" by putting an entry into the VOC (VOCabulary) file which points to the object code. It is only changed when yo...

Kumar, a UNIX level copy of the project does not result in a working project. All files with secondary keys will need to be re-indexed, a check needs to be done to make sure the VOC contains no hard-coded full paths, the SQL table information needs to be reset for all files, and more. Most important...

The DSExecute command runs a command on the machine which is running the DataStage server engine. Since IBM/Ascential don't have an AS/400 implementation yet there is no option in DSExecute for that OS. I am not sure if there is a remote command facility for AS/400 along the lines of rsh, you might ...

Ray - we had made sure that a backup was made of the DS_JOBOBJECTS prior to the attempt at fixing it! It would seem that there is no recent backup so they might be SOL; but they've contacted support and might get the file fixed as far as possible from them. I thnk we've all been through that frighte...

The part of error that I find odd is 1.(warning)Unhandled failure (A0206YTD) encountered calling routine . This sounds like the RoutineActivity is interpreting the function return value "A0206YTD" as an error code and since it is non-zero it is logging a warning and then the program aborts. Do you h...

I think you might have declared this as a before/after subroutine; could this be the case? If so, you need to redefine it as a normal function.

Since the error is coming from the code in the routine, you would need to post it in order for anyone here to be able to help you.

Have you tried to re-run the fixtool to see if it corrects more errors on subsequent runs?

Unfortunately it does look like you've got a terminally ill file - I hope you don't lose too much data.