DSXchange

Change your routine to log a message to prove that it's operating. If it is, then show us how and where you're trying to use the activity variable.

Delete the Data Set - it still has the column definitions in its record schema from when it was created. By deleting it you force its re-creation using the new record schema.

$UNSET tells DataStage to pretend that the environment variable was never set at all, which is entirely legal. Check your spelling.

In a word, beforehand. Or afterwards. If beforehand, get the line count from the input file and compare it with the value in the control file. You can use operating system utilities to get both values, and compare them in a Nested Condition activity. If afterwards you can compare one of the row coun...

Learn patience, grasshopper. It's not hung. If there are tens of thousands of entries in the job log, the Director will take a long time to refresh - first it has to sort them in date order (since they're in a database table). There is a "Refreshing" progress bar in the Director's status bar when yo...

You should be able to login to PartnerWorld and get it via that channel. If not discuss with your manager - this is part of what being a partner is about. I'm not, so can not really give any more advice.

If the time interval is asserted the row interval is ignored. Bring both environment variables into your job as job parameters, and give the special default value of $UNSET to the time interval parameter. In this way the row interval parameter will be able to "do its thing".

That is not a legal definition. There can be no "." between the V and the 9.

Doesn't Search work in your browser?

One Oconv() removes all alphabetic characters, the other removes all numeric characters. Anything left over is non alphanumeric.

No. The project is a schema in the database. It is not "in" the database in any other sense. Existence of a project is recorded in system tables UV.ACCOUNT and UV_SCHEMA.

You will (may) get multiple copies if your data are not partitioned as per the keys mentioned in the Remove Duplicates stage.

Maybe the file was populated on a previous run?

Do you get a row count with

You need a connection (session) before you can issue an ALTER SESSION command, too. That's why it has to be in the stage, and can not be done globally.

What stage type is MATERIAL_DESC_EXCEL_ldr ?
What are its pertinent stage properties?
Was any other error/warning logged?
Why might an export (conversion from DataStage internal format to "text" format) failed? Do you have write permission to the file/directory in question?