DSXchange

Make sure there's no trailing space at the end, I've had that happen once. And that letters are letters and numbers are numbers, from what I recall the numbers are in italics?

To answer the question of 'job parameters', these should be used for anything that could change from environment to environment - instance, user, password, schema owner, etc.

ok chulett i wont use user define sql Hey chulett i have replace the db2 udb stage with new one and run the job but i am getting same error APT_CombinedOperatorController,0: Fatal Error: Fatal: This SQL statement did not contain the same number of parameters as columns on this link. This usually ha...

Compiled should be fine and runnable. Triple-check you're running the job you think you are. Do you have this issue with any other jobs or just this one?

Did you try removing and re-adding the stage? Impossible to tell from what you're posting.

If you really think that's your solution, use Convert() along with the decimal value of the character to strip it from the string: Convert(CHAR(26),"",YourField) :idea: Next time please do a better job of choosing a thread subject. We know your question would be about "DataStage"...

The only one that can analyze this, other than yourself of course, would be a SysAdmin for that box.

What is your XPath Expression for the 'row number' field? It should be left blank to mean a simple pass-through value and then be dropped by the last transformer.

When I've seen things like this, deleting and recreating the stage from scratch has resolved the weirdness. Do not set up any user-defined sql.

You might also contact your official support provider, from what I understand there are scripts available to help clean up XMETA discrepencies like that. Worth a shot.

As noted, please start your own thread rather than hijacking someone else's.

Env 2 - There was no ORACLE_HOME and ORACLE_SID variable present LD_LIBRARY_PATH do not contain oracle path in it INIT_VERSION is not present There is no LANG variable This makes no sense. You need to track down why these are 'missing', they are required for any native Oracle stage to work. What Or...

The compiler is not going to check the veracity of any of the property values, that all happens at runtime.

Do you have an Oracle client installed on the DataStage server? Has DataStage been configured for it?

As noted, not a whole lot to work with. Details would be good.

There's no such thing as a Sequence that resets itself. A Best Practice is to schedule a script that that runs your Sequence using dsjob and checks to see if it needs to reset it first. Again, using dsjob -jobinfo and dsjob -run -mode RESET off the top of my head.