DSXchange

This error most usually occurs when the Precision field for a Decimal or string column has been left unpopulated. That's the first thing I'd check.

Nor is it permissible for precision to be zero or a negative number nor, indeed, too large.

rpm is a Linux command. It may not be findable in your PATH, but it should be findable if you're logged as superuser. Of course, you could use a find command to determine the location of the rpm command.

Create a routine that subtracts 3 from the month if it is 4 through 12, or adds 9 to the month and subtracts 1 from the year if the month is 1 through 3, then adjusts the date backwards until it is valid. From that new date, rebuild the timestamp. Alternately you could perform these steps in stage v...

Welcome aboard.

Please prove your assertion, and describe the Partitioning settings on both inputs of the Join stage in question.

Please also be a little more careful when crafting English sentences.

OK, what is the timestamp three months before 2011-05-31 11:12:13 ?

Yes you have (erred in your design). ExecSH is a "before/after subroutine". This type of routine is not suitable for use as a Routine activity - only "transform functions" can be used. The reason for that is that before/after subroutines do not have a mechanism for returning a va...

You have not yet set up the Engine credentials.

Do this using the Web Console for Information Server, on the Domain Management menu. You will need to be logged in as a user to whom Suite Administrator role pertains.

uvGMTSecs <-- System(99) uvDays <-- Int(uvGMTSecs / 86400) uvSecs <-- Mod(uvGMTSecs, 86400) uvDate <-- Oconv(uvDays + 732, "D-YMD") uvTime <-- Oconv(uvSecs, "MTS") uvTimestamp <-- uvDate : " " : uvTime Generalize from the above. You couldn't, for example, do all of tha...

Out of memory? You would need to look at the detailed logs to determine on which tier the memory problem occurred.

In an expression in a job sequence (for example in a User Variables activity) you could use the System(99) function, which returns the number of seconds since midnight GMT on January 1, 1970, then use Oconv() and Time() functions to convert that to current.

Sometimes the business rule then specifies that the day in question must be a business day (not a weekend or a holiday).

What are your business rules?

Routines aren't in DS_JOBS or DS_JOBOBJECTS at all.

Job type is identified by JOBTYPEIND in the DS_JOBS table.

Why do you want to avoid "the holes"? They are not relevant for surrogate keys. Except in very special circumstances, noted elsewhere, it is impossible to guarantee an unbroken sequence from the Surrogate Key Generator stage. You need to use a different mechanism. Why not have the Sequenti...

Show us your routine code. In particular, what value are you putting into the Ans variable?

But why are you using a Routine activity at all? Surely an Execute Command activity would be more appropriate?

Once you know the format of the CSV create a source-to-target mapping specification and base your DataStage design upon that.