DSXchange

Don't ever say "can't". What if the ONLY solution requires you to have two jobs? Think about what is happening. You are establishing a cursor to select rows from the table, and attempting to perform updates against a table with an open cursor. Will any other tool allow you to do this? Why do you exp...

Please read the relevant help topics or manual chapters for each stage type then post specific questions. In general Enterprise stage types are to be preferred, but there are some circumstances in which they might be contraindicated.

I still think it's a bug in the client.

Chances are that the file was the same physical size because the larger pointers consumed more of the free space in each group, without causing any of the groups to extend into overflow.

Tell us more about your configuration. In particular, what are you using for your ProfileStage DataBase (PSDB)? How is the ODBC connection to the PSDB configured?

Events 1 through 4 alert you to possible data truncation and will not be fatal. Event 5 suggests that you are using an ODBC connection to MS Access with the parameter array size set to something other than 1. MS Access does not support array processing.

First, let me assert that Windows XP is not a supported platform for Information Server. I suspect that your problem lies somewhere in there. However, is there any information in the error messages about an inappropriately-set CLASSPATH environment variable? And is that the exact error message? If n...

Welcome aboard.

You do not appear to have asked a question.

The space is for the sign character, in case your Decimal number is negative. Remove it with a Convert() or Trim() function.

The code area is inactive until you have given the routine a name on the General tab.

That's it, then. The function expects a uint32 and your BigInt is a uint64. DataStage alerts you to the possibility of error (if your number is too big for a uint32). You can handle the message, but better would be to ensure that the incoming column is defined as uint32.

That's because there is no mechanism in DataStage for "Comparing a wild character in the source data with the lookup". You will need to devise a more appropriate strategy. Please post your source-to-target mapping specification for this column. This is an English language specification, not code or ...

The commands in your original post all need to be executed in UPPER CASE.

Is the PXEngine available on all processing nodes? That is, have you properly deployed the parallel execution run-time components to all machines in your environment?

Most databases have limits on identifier names. Under the ODBC standards it's 18 characters.