DSXchange

That makes sense if you understand what has to happen when there's a level number higher than 01. There's an intrinsic left outer join with the lowest level columns and the higher level columns.

The moral of the story seems to be not to include level numbers where they're not required.

Try doing a search for "heap allocation failed" both here and developerWorks (and even Google). This will give you some clues.

No idea. Any clues in the log files? In particular check the "job starting" entry to ensure that the correct parameter values have been received.

Can you please capture and post the score from this job?

Errors from "main program" are usually from inserted operators or operators (usually the modify operator) that have been optimized onto links.

I'm certainly surprised to see a message from DSR_EXECJOB. Did you accidentally request that the selected job(s) be run? For example (unlikely, I know) might you accidentally have pressed Ctrl+F5 ?

Write out (in English, not in code) the rules that specify how and when each date needs to be incremented.

I'll warrant that some combination of stage variables and loop variables will prove to be the solution you seek.

The reason would be the appliance layer between the rest of the world and the database on an Exadata appliance. But I've been wrong before - why not try it and let us know? It won't do any harm - Balanced Optimization is a design time activity only. You don't actually have to use the generated jobs.

No. At least not yet.

How/where are you executing awk, if not as an after-job command?

IBM has not announced a date yet.

My guess would be April 2015.

Use an after-job subroutine ExecSH or ExecSHSilent to execute the command

At my current engagement we run UTF-16BE - so I guess the OP is on an Intel-chipped box.

No.

Perhaps you could use a generic name for the key explicitly in DataStage, and create an alias in the database for the key column.

mandyli wrote:where should I find syncproject script ?

ASBNode/bin/SyncProject.sh with the -Report option to see if it finds the issue, and then use the -Fix option to resolve it.

Try running the syncproject script (a) to determine whether there are any issues and, if so, (b) to fix them.