DSXchange

Should still be automatic if you define your target field in the Sequential File stage as Decimal with a scale of 2, you shouldn't have to do anything magical to get what you want. If you want to have specific control over the format of the data, define the target field as Character or Varchar and t...

Math on a string forces a numeric conversion under the covers. You would need to do this if you were populating a field heading to a database table, for instance. I prefer to multiply by one, but that's just me. However, if this was still "in flight" in your job moving between transformers, you shou...

Defaulted. So... 'Use Project Defaults' is checked in the job and - at the project level - 'Tunables' does not have 'Enable row buffer' enabled.

Titto wrote:It worked out!!

Yah!

pnchowdary wrote:Can't we use the Real function in this scenario?

Not sure as I haven't had a need to use that one before. Might be something to try for grins.

Still think math would do the trick...


Give that a shot.

Read the online help available from inside the stage so you understand how all of the update actions work. That action issues an update and - if the update fails - also attempts an insert. There is another where the two actions are reversed. There is no update action that works only if something ha...

You could always try looking it up in the BASIC reference manual.

It does what you would think it does from its name - returns a boolean, true if the variable was never assigned a value and false if any value was assigned, including a null value.

Sometimes a 'month' is defined as a 30 day interval. When it needs to be 'real' months, you need to roll your own. It's not all that hard to put together a routine that adds months to a date and handles real months and leap years and fun things like that. The 'conv' brothers help alot in that regard.

Well, you can certainly 'undo' database changes via either 0 commit levels and constraints that check for rejected records or transaction grouping if that's available in your database stage. The Output Link variables like REJECTED, REJECTEDCODE, DMBSERROR, etc are what I am referring to. The hashed ...

No, that's the thing - no options are checked. None, not in the stage nor in the job. The reference hashed file does have its 'Pre-load to memory' option enabled, but so do all the other similarly designed jobs that do not exhibit this behaviour. The writing side of the hashed file has all options d...

Suggestion to all consultants of employers: include something like this in all your work. This code is provided "AS IS" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infrin...

Based on your use of SYSDATE, making an assumption of Oracle. All you would need in your query's constraint would be something like: DATE_COLUMN > ADD_MONTHS(SYSDATE,3) You may need to 'trunc' both dates if you don't want the time portions to come into play, but that should help in your 'whe...

Search the forums for CRC32 - not sure if it applies to PX jobs, however.

Ok, what is up with the message in the subject line? I have a number of very similar jobs and one of them is misbehaving. All do basically this: 1) Read from a landed flat file 2) Transforms on the data 3) Hit an existing keys hashed file for insert/update 4) Generate a new surrogate for inserts 5) ...