DSXchange

Does it work with Manager or Multiclient manager.
My case was the Shared container alone.

But I believe the lookup key is constant for both the file.
That case, read the rest of the column in file 2 as single varchar field.
Once you able to find the lookup record, using transformer, you can parse the specific field using Field function.

Could you explain you job design? What is DSLink83 connecting to?
Was your conversion successful?
What is the source value and what is the conversion logic you used?
If you write the data to a sequential file before lookup, were you able to the value of timestamp getting converted correctly?

Datastage can handle this by itself. If your source stage has metadata configured, the record that do not comply the specified metadata will be rejected and the records can be captured if the Reject mode is set to output.

I too faced one such issue, may be package sent along with CD might be corrupted by some reason.

Try to run the .net framework separately before installation and check if that gets completed.

Yes, Global table will persist only till that session alive. Its a temporary table.
You ll need to go for normal persistent table creation.

It takes some time to configure in Registry. But how long were you been waiting?
Do does the icons got installed in Desktop and is it working?

Shared container cannot be compiled. Only the job which uses the container can be compiled, and hence the Container code will be a part of jobs Compiled code.
May I know what is the version that you are using?
I tried with 7.5.1, it did got imported without any errors.

It is available in the same thread, but with less than 3 cents a day. Grab the Premium membership quickly and get the full essence of Dsxchange.

Its very well possible. The basic need to ETL is to intergreate data available at different system.
All the options avaialable in OCI should funciton as normal as this scenario is concern.

The datatype can be directly changed in Transformer stage. You will need an explicit conversion function. You need to make sure the key field of main stream as well as the lookup stream are of same datatype and same length. Atlest compatible datatype. The warning that been shown is due to the reason...

Thats good. Do you wish to mark the topic as resolved?

Hope you don't end up in writing Batch Control for this.

What is the change in rows/sec now (after spliting the job)?
What is the total time (job a + job b)?
If you run the the job which has OCI to HASHED file will it give you the same old performance?
Because, it may be issue with network at the time when you ran the job, as noted earliar.