DSXchange

You really should Search DSXchange - this question has been asked and answered in the past. There are basically two possibilities - the key is invalid or the hashed file is corrupted (perhaps by reaching its 2GB maximum size with 32-bit addressing). Your key appears to contain dynamic array delimite...

First off, there is no version 9.0. I will assume you are migrating to version 9.1.

You migrate users using Information Server tools, specifically the istool command line. Find this in the manual or Information Center.

You're on UNIX - why are you expecting Windows line terminators?

Also, the warning is "command not found". What command are you trying to execute? Is your PATH inclusive of this command's parent directory?

You simply can't invoke DSOpenProject from within the context of an already-open project - that is, from any DataStage component. This function, as I noted four years back - is only available in the C-callable DataStage API, which is intended for writing applications that sit outside but call DataSt...

Try setting the Data Element in the Columns grid to "Date".

In ODBC stages at least this triggers the conversion from internal to external format.

You are correct. DataDirect is the vendor that supplies the ODBC drivers that ship with DataStage. Both the Oracle Connector stage and Oracle Enterprise stage use OCI.

dsrpcd does not authenticate users. They are already authenticated before the connection request to the engine tier is made. The dsrpcd processes accesses dsrpcservices file to determine whether the node from which the request for the dscs service is acceptable and, if so, starts the corresponding e...

It will work on multiple nodes, provided that the data are partitioned using a key-based algorithm (hash or modulus) on the key being used in change detection, or at least the first column thereof.

"Object reference not set to an instance of an object".

Somehow or other one of the objects was not able to be selected.
Try again in a new instance of Designer and it might well work.

Cores relate only to licensing ("processor value units").

Nodes, and therefore partitioning, are driven purely from what's in the configuration file. As Craig notes, these are a logical concept.

Try setting the Data Element in the Columns grid to "Date".

I'm using it in 8.7. It's not separately installed; it's integrated within the engine. Performance is not an issue, as you're working one row at a time. By and large it uses the same memory that the job is already using; probably requires a small amount of extra memory to maintain the watchlist and ...

I think you'd have to get it from HP.

Then you'd better show us exactly what you are doing.

The only explanation is that the design specifies generation of a random date. Does the extended column metadata include a random Generator property?