DSXchange

It looks like you cannot get rid of the message unless your source string is fixed length, I've experimented around a bit. You can always suppress the message from the log and it might be worth submitting the problem to your support provider.

tini - did you use 13 instead of 14 as the string end position? How did you declare this new column in your metadata? Somewhere you have specified this as unbounded, which is where the warning is coming from.

Try That will give you a lenght of 14, not 15 as you are currently doing.

The link row counts will work if called from the after-job subroutine.

The "cleanup resource" method will result in lost data if the job is locked because it is running; if the job is locked for editing then just the changes since the last save will be lost.

The only tuning you can do in this case that would make any difference is to pre-set the MINIMUM.MODULUS to a higher number. You will still end up with 100% I/O activity.

Specify an explicit length of 14 for your new string and the warning will go away.

JoshGeorge - in the context of the user working with instanciation, the job is almost certainly not "runnable" because it is already running; not because it aborted on the last run.

Ray answered your question in the publicly visible portion. You don't have a problem, so there is no solution. If you wish to speed this up you will need to talk to your system administrator and discuss what options you have on your hardware platform and UNIX OS to tune I/O buffers.

Kaps - that error happens when you try to run a job that is running; which means that your Invocation ID is not unique.

You need to read the help files, they describe your options in detail. You need to set the index option to mainenance or rebuild; but you also need to understand the implications so you really should read the docs before adding this option.

The read-only objects are DataStage builtin routines and they do not need to be exported, as they are present in all projects. You can safely ignore this message.

re-running the installer and specifying NLS will do what you requested, but you really should follow what Ray just suggested and go through the documentation. Once you have NLS you cannot go back.

Have you though about just using 3 Oracle Enterprise stages and linking the 3 streams using a funnel stage?

Vinita, there are few things as frustrating at DSXChange as having someone post that they are getting an error and need help in solving it - but they never post the actual error message. Ray is still developing the "RMM" stage (read-my-mind) but that won't be available until the telepathy protocol i...