DSXchange

ayan wrote:Also if 2 jobs raise some excpetion at the same time, will notification be sent for both?

No. The first signals its exception which triggers the exception handler - control is now transferred to that stream of processing.

Don't think so - the entire DS_JOBOBJECTS record will never be just the table name. A LIKE operator appears to be called for. EVAL DS_JOBOBJECTS."if UPCASE(@RECORD) LIKE '%YOUR_TABLE_NAME%' then 'FOUND' else ''" AS FOUND FMT '5L' But this reinstates the situation to which devhni was object...

In version 7 View Data will not substitute for $PROJDEF - you need to replace $PROJDEF with an actual value (the DSN in this case).

This problem is fixed in version 8.

Management, eh?

ETL experts, the lot of 'em, no doubt.

Resist stupid requirements!

OK, then maybe it's just a Windows thing. Not all shared memory operations are supported on Windows. You can see this when you check a configuration file - there's a warning about shared memory information "not being available on this platform". smat = "shared memory analysis tool&quo...

All zeroes is not, by default, legal for Decimal data type.

There is something you can set (environment variable?) that allows DataStage to accept all zeroes for a decimal number.

I don't reckon that's really a resolution. What was the cause? Sure zapping the registry entry forced the symptom to disappear; it would have been interesting to get before and after views of that registry entry. Otherwise the answer is akin to the advice to run sequentially to avoid partitioning is...

Support thinks that it may be an inconsistency of patch levels between client and server. We're working on investigating that now. Stay tuned...

No. These two environment variables must refer to the actual executables. Most rely on PATH being set properly so that only the name of the compiler/linker is required.

Run each of the jobs independently and monitor their individual resource consumption. Do some arithmetic to determine how many of these can run at a time before maxing out any of the resources.

Read ora.2714.131128.1.log - it should reveal the actual problem.

When is the interview? Please strive for a professional standard of written English on DSXchange. There is no need to use SMS-style abbreviations; there is no 140 character limit. For those whose first language is not English it is difficult enough when the English is well written, without imposing ...

Create a "lookup table" of month names (Char(36) stage variable) and use Index() function to find the month name therein. Perform simple arithmetic to get the month number. Use string manipulation to re-format.

If not the whole repository then certainly DS_JOBS and DS_JOBOBJECTS.

Make sure you have exclusive access.