DSXchange

Munish - that just means that you don't have a field incorrectly filled in the first 600 rows of your data. This error is not dependant upon amount of data in a source, just the length of data in a given field and that could happen in any row.

myotoo - please start a new thread with this question, as it really has nothing to do with the specific problem in this thread.

Doing a global update of all containers using that UPDATE command is, in my opinion, not a good idea at all.

Simplest for you is to export the container into a .dsx file, then use your favorite editor and change occurrences of Readonly "1" to use the value 0.

Paul M wrote:...we found out this is probably due to varchar string export that is UTF-8 encoded... The datastage log file does not give any information, the job just aborts...

What leads you to believe that the problem is being caused by NLS and UTF-8 settings?

The words "intersection" and "inner join" can mean the same thing, but you would need to give a bit more information in order for this question to be answered with any authority. What kind of an intersection are you looking at doing, and from what kind of source(s)?

PX sizing = look at your apt_config file for paths used
Server sizing = as mentioned earlier, look at the paths in uvconfig

DSGuru2B - If I understood the posts correctly this is already being done, but I just noticed that checkpointing is being used as well.

Once you get this error message, what does the director show as the "state" of the job?

Rohan, I have to disagree with your conclusion, at least in part. The message is syntactically & grammatically correct but is quite confusing, even to native English speakers. But a "reset" of a job, either manual or via the "reset if required" switch in a sequence will allow it to be run withou...

My initial thought is that you might be "overloading" your Windows server. I would recommend using a DataStage PX configuration file that only defines 1 node for testing, and also set APT_DUMP_SCORE to true to get some additional information. Also, how many nodes do you define in your current file a...

The message is a double-negative and confusing, think of it as: (a) Job's right state is "compiled and not running" (b) Job is not in state (a) Apart from a job being in an "aborted" state, I have most often seen this error when using multi-instance jobs and trying to start the same instance multipl...

Ingo, I am assuming that the firewall disconnects any user sessions, not running jobs. If you activate the lock daemon (described in the product documentation) it will periodically scan the locks and clear up any open ones; there should be no reason to reboot your DataStage server for disconnected s...

...The hash file is a lookup of itself... My thought there is that you might have buffered writes turned on, so that a lookup of a record might not return a value because it hasn't actually been written to the file yet. This could happen more frequently when a lot of writes are done and are buffere...

kumar_s wrote:...validate Datastage License...

I'd be out of here as well since I can't afford my own license, I just leech off the clients that I work for

Rony, a "hang" is a tough condition to analyze. When the job "hangs" does it use any CPU or I/O or other resources? Do the players still exist on the system or have they stopped? Does the job "hang" right at the beginning or after some period of processing rows? Does the the amount of data being pro...