DSXchange

You should have just started off with your problem. Post the details of your not successful DataStage installation.

Note that "numeric" includes dates and times in this context. No... not in my experience. There are other messages specific to data issues with date/time types, fairly certain that this "ORA-01722" is specific to NUMBER types. See this site for some examples of what can cause it.

You could always... upgrade.

For SQL, sure... but not for PL/SQL.

Replace "default" with your actual project name.

I'm just "mentioning" what Oracle is reporting. Are you letting the stage do all of the "upsert" SQL generation or is there anything... custom going on? Regardless, you need to start validating what fields/values you are sending to any NUMBER fields.

So now you need to track down that "invalid number" error. Somewhere, you are trying to put character data into a NUMBER field.

That's a very generic error and there should be more specific ones logged along with it, like running out of temp space or something. If you don't see them in DataStage, see if your DBA can find them in the alert log...

What exactly does this have to do with the MetaData Workbench product? And you chose a forum I can't moderate.

And... off to your own topic.

Is either environment "NLS enabled"? Have you involved your official support provider yet?

Can't be done there. That's PL/SQL rather than SQL. You can either put that work into the job or (since it returns nothing) build a stored procedure from that code and CALL the proc 'before SQL'.

There is nothing different, UNIX to Windows, other than the path to the executable. All those syntax examples are still applicable to you.

What happens when you use the source database characterset in your job?

What is the characterset of the source database?