DSXchange

It would be easier if you posted the exact error message(s). I have never seen errors caused by data (apart from NULL in the wrong place).

Separate jobs. Put the logic in the sequence that decides which job to run.

This is a joke, right?

You must have a reject-handling link if you want to obtain information about rejected rows (of course, these will probably be captured in the database logs, but that's a whole different story).

Why not make ETL_DATE data type Date?

While you're testing, lose the Oracle stage and replace with a text file. Then use one function at a time building the expression in the Transformer stage.

You really should have told us the precise error that was thrown, too.

@DAY is the day of the month. It only has values between 1 and 31. So applying that Oconv() function to it could only yield values in the range "1968-01-01" through "1968-01-31". Clearly you executed it on the seventh of the month. To put it another way, @DAY and @DATE are not th...

In my experience everything with pool names requires the configuration file to be named at design time. This is frustrating, because I prefer to use $APT_CONFIG_FILE with its default set to $PROJDEF, but I have to change this in order to effect the design, then change it back once the design is ready.

You don't need to define mapping - just enable RCP on the output of the Copy stage. If you need to generate current date into a particular column in the target table, do that in a Transformer stage or a Column Generator stage, with RCP enabled to handle the other columns. Hopefully the current date ...

Tell us how they fare with Postgres.

Don't know if it's better, but I usually pipe the result through a tr command to convert all linefeeds to comma (or tab or whatever) and a sed command to get rid of the final empty line if there is one. There's more than one way to skin a cat, as they say. Even more if you're wearing full body armour!

What errors are you getting? Do they relate, perhaps, to "block overflow"? That might mean that your blocking fields aren't discriminating well enough, so you are ending up with more records per block than can conveniently fit in the allocated amount of memory. Read more about block overfl...

Multiply by 100000.

Are the Oracle tables to be identically structured as the DB2 tables? If so you can make use of Runtime Column Propagation. Is any transformation to be performed? Are there any BLOBs or CLOBs to transfer? These add a minor level of difficulty, but you can still do it by generating custom SQL in a se...

skp wrote:but in the i/p column there is no limit of the values. In this case what can i do.... please help...

Define sufficient columns. Default unpopulated columns to NULL and filter these downstream of the Pivot stage.

Have you purchased the SAP R/3 PACK for DataStage?

That depends somewhat on your configuration file. To achieve what you've stated the configuration file would need to have (at least) six nodes but only four of those in the default node pool. If your configuration file only has four nodes mentioned, there is no way that your requirement can be accom...