DSXchange

I'd also add a suggestion to not set Run_Stat that way but instead run the command directly and then capture $? and see if that changes things.

This typically means your XPath Expressions are not correct. How were they generated - from an xsd or manually? Can you post some samples of what you are trying to generate and the XPath Expressions you are using?

If this happens to just you and no-one else, then I would suggest a complete removal of the existing client and a reinstall. If it happens to everyone, then bigger issues are afoot.

Please post the complete, unedited error message that you receive.

A hashed file lookup fails when the key values don't match exactly and it is typically something like trailing spaces on one side or the other that do people in. As noted, triple-check your values.

Not necessarily an NLS issue, at least not yet. Any chance you are moving any kind of "LOB" data in the job? It is not supported and can generate that error, hence the question.

Hkonishi wrote:Q5) Oracle client version on DataStage server?
A5) No Oracle client was installed on to our DS server at this stage. We are now planning to install 10g client by the end of this year.

Not possible. The OCI stages do not function without an Oracle client installed on the DataStage server. FYI.

Something that says "CRITICAL ERROR! Notify the system administrator" should be reported to your admin and then they in turn will need to contact your official support provider.

There is an extra step needed when importing a .xml export file, it will first be converted to .dsx 'under the covers' automatically and then imported. This conversion can be... lengthy. FYI.

Ugh... the moment you put any 'intelligence' or 'business logic' into a surrogate key it is no longer a true surrogate. Why the desire to include the date/time information? Are you doing this so the incremented portion can start over from 1 each load?

I would think that your business rules re: duplicate records would drive the solution. Are all processed? Only the first one encountered? Only the last / most recent record? The answer would affect the solution.

Appreciate it.

And adding it at the Project level will immediately affect all jobs in that project, depending on what you use as its default value.

Well, then... I've seen something like this and it was a bug that getting a newer version of the Oracle client solved. Maybe not exactly this.

To Kunal, since it's a related discussion, I would opt for posting my queries in this thread itself rather than creating lots of threads under same topic. What do you say? Related != same. We ask people to start their own topics even for allegedly 'related' questions for multiple reasons, including...