DSXchange

SQL is: Insert into Table Name(Col1, Co2......Coln) Values (?,?,?....?) With None; With none what? :? I assume this was a system generated SQL which was modified when User-Defined SQL was selected. It was always there, totally unchanged.. As i keep stating, i did not touch the job in Production. Ho...

rachit82 wrote:SQL is: Insert into Table Name(Col1, Co2......Coln) Values (?,?,?....?) With None;

With none what?

Seen similar problems in the past in low memory situations. Restart your PC and see if the problem persists.

Sounds like you need the Windows XP "Service Pack 2" patch for DataStage. Request it from your support provider.

What is your "Update action" in the target stage? I don't want to make any assumptions about what "loading" means here. Also, how are the end users counting what was loaded in any given run?

What issue, exactly? Does everything else parse out, just not that? Is there an error or warning generated? You really haven't given us any information about your job either - for example the XPath Expressions you are using in the XML Input stage, in particular for this element.

Be patient, if someone can I'm sure they will.

In the meantime, did you try searching the forums for your error message? I got 9 other hits on "non-zero in the leading nybble", did none of those help you?

You really don't want to be writing to a database from a routine, while it can be done I don't see the need. Simplest solution is to take your information and write it out to a flat file, then have a 'normal' DataStage job that reads that file (or files) and loads the information into your database ...

Hmmm... that should be happening automatically. The only time I've seen that not happen is when people were not using a Job Activity stage to run their jobs. How are you running yours and what warning limit do they end up using?

From designer if a job is in aborted state it won't let you run without compiling. Nothing stopping you from resetting it from the Director first. Regardless, the bottom line is what Ray noted, the assertion that "it is always necessary to recompile if a job aborts" is incorrect. It is ne...

Server job, so no "EE" stage here. And the OCI stage will automatically drop the array size down to 1 if it is not already there when using these combo actions.

Someone must have thought so, but without details one cannot comment on the 'correctness' of the approach. Typically, all required parameters would be defined in the Sequence job itself so it could pass them along as needed.

Ideally you shouldn't ever get any errors in any mode. :wink: Insert/Update means the insert is first attempted and if it fails an update is attempted. In order for the insert to fail there must be a unique index / primary key on the target that gets violated. However, any error reported from this o...

That's already been noted along with the fact that that requires a VOC entry, i.e. an account-based hashed file or a pathed hashed file with a manually created VOC record.

Not really sure what you mean by "RAC compatible". RAC is invisible to any connecting clients, nothing about how DataStage connects into Oracle changes just because of RAC. So are you actually asking about the failover capabilities of DataStage itself? If there is a failure that takes out ...