DSXchange

Or, if you happen to be using a Transformer stage, you can do it in there. There are half a dozen null-handling functions that appear when you choose this branch from the Functions > Null Handling branch of the expression editor operand menu.

There is no pivot function. There is a Pivot stage. It has its own manual and its own help, and is quite easy to use. Indeed, an earlier poster provided all the information you need.

This is actually a good task for MetaStage, particularly if good and wise practices have been used in DataStage design.

What's the setting of CLASSPATH ?

It can't be done using Parameter Manager.

In Director, select Log View, select Project > Print from the menu and check the Print To File check box.

Maybe, but I've used that knowledge more than once to play "spot the culprit" (who has a job locked) before exporting projects.

Do whatever you like. You're in charge. Design the job sequence and its recovery mechanisms to your own specifications.

Please share with us what knowledge you have already obtained by searching the forum, using the on-line help, and referring to DataStage and data base manuals. Or taking training class(es).
Then we can help to fill in any gaps.

Please share with us what knowledge you have already obtained by searching the forum, using the on-line help, and referring to DataStage manuals. Or taking training class(es).
Then we can help to fill in any gaps.

Use ls -l to see how big the hashed file is. With 30000 records it's unlikely to be anywhere near 2GB, unless you've got huge records. The message suggests that there is internal corruption. It's probably easiest to delete the hashed file and re-create it. You could attempt repair with fixtool.

When you use sqlplus you don't specify a SID so sqlplus is picking up a value from your ORACLE_SID environment variable.

What happens when you try sqlplus user/password@SID suggests that the SID you're specifying is not in tnsnames.ora on the machine from which you're trying to connect.

I recommend changing the contents of UV.FLAVOR to prevent accidental creation of accounts via the uv command.

UV tables are hashed files. The only difference is that, if you create them as UV tables, then entries are written into the system tables (SQL Catalog), and they can't be deleted with DELETE.FILE (you must use DROP TABLE).

Even better is to ask "do I REALLY need to load more than 2GB into it?". Do you really need all those columns? If they're not used in a job (there is no line drawn from the column in a Transformer stage) you don't need that column and therefore don't need to load it into the hashed file. Do you real...

They're not obfuscated. The key is made up of the client machine identifier, followed by the client machine name, followed (by a colon then) by the pid on the server of the agent dsapi_server process that is maintaining the connection to the client. The file dictionary for DS_LICENSE limits the colu...