DSXchange

What exactly do you mean by "didn't work"?

The main (only?) one is to make sure that you install the different clients in different locations. Multi Client Manager will look after the rest.

My current site is running 8.7 FP1 on AIX and also does not have BDFS. Maybe it's initially only available when the Engine tier is on Linux.

The link row count shows how many rows were sent to Oracle, not how many were inserted. Oracle may have rejected some of them. It is possible to capture rejected rows in server jobs. +-----------+ out +----------+ -----> |Transformer| -----> | Oracle | +-----------+ +----------+ : : rejects : V Link...

Agree, shouldn't be necessary if dsjob behaves as we believe it does, but it will force asynchronous execution of the command unconditionally.

Do a lookup or change detection against the target table to determine existence, and create separate streams for inserts and updates. I am assuming here that the same key occurs no more than once in the incremental set.

Not really.

You could do the filtering in a Tranformer stage, using last record in group detection, but a Remove Duplicates is entirely adequate. Either approach requires data sorted by ID and by date, and partitioned by ID.

Use a sufficiently large target data type.

Try preceding the job run request with nohup

Have someone with Information Server Suite Administrator role check, using Web Console for Information Server, that the Engine credential mapping for your user ID is correct. This is to be found under the Domain Management menu.

sanygup wrote:It was working fine earlier.

What has changed?

"Nothing" is not the correct answer.

As far as I am aware, a timeout always generates a warning from the Wait For File activity. You might like to submit an enhancement request to disable this "feature" (a check box in the activity, perhaps).

Well, it's at your site. You will just have to do some more in-depth detective work to find out where it's coming from. You have not answered my questions about telnet connections.

Table name (or SQL) is a property of a link. In the local repository table names are to be found in the "pin" records of the DS_JOBOBJECTS table. A "pin" is one end of a link. OLETYPE of "pin" records indicates whther the pin is an input or an output link with respect t...

Incidentally, it's a Sequence, not a Sequencer. You can use a Sequencer in a Sequence (it's the activity with the big blue arrow icon, and only one property (Any/All)).