DSXchange

The question arose in conversation yesterday about whether DataStage could be said to be "CWM compliant". Any thoughts?
This article suggests that there's a good argument for "Yes", at least in the case of DB2 Data Warehouse Center.

You might take a look at protected projects; there's a role that effectively limits operations there to import. No edits at all are permitted in a protected project.

Maybe the logic should handle $RETURN_VALUE -eq 0 separately. This means that the job start request was successful and that the job is still running. You have no idea when it will end.

The excluded records are simply category placeholders - they record the existence and relationships of category folders. They contain no other information.

QualityStage.

Does ORAOCI8 exist in the Stage Types branch of the Repository?

Does it exist in the DS_STAGETYPES table?

Nothing to worry about. In fact, there are no ROOT records in DS_JOBS.

Short answer, no. Longer answer, both the XMETA database and the WebSphere Application Server have high availability (HA) failover capability in version 8.5 and later. For more money, of course.

1. Yes.
2. No. But you can provide it as part of the custom SELECT statement.

I have done this in the past, generating the SELECT statement via a query against the Oracle system tables. This was done in an upstream server job and the SQL query saved in that job's user status area.

It means that you can identify the server but cannot connect to it. Read your database or ODBC driver documentation to decode the error code.

Welcome aboard. What do you mean by "performance"? The same parallel processing architecture is used in version 8 as was used in version 7.

Those error messages refer to routines that should be, but aren't, in the global catalog space. The fact that they aren't suggests that the installation did not complete successfully. Did you inspect the install log?

It remains the case that OEL Linux is not a supported operating system.

There is no concept of tying nodes to physical processors. Even with something like Affinity in place you have no control over the processes that run DataStage jobs, particularly parallel jobs, start. And you certainly can't do this with Metadata Workbench, which is much more an after-the-event util...