DSXchange

OR you can use the same as mentioned, Sort your input records before the transformer and inside the transformer 1. svOld: svNew 2. svNew: <KeyColumn> 3. svCol2: If svOld <> svNew Then svCol2 + 1 Else svCol2 Map this svCol2 to your Col2 And the point 3 needs to be changed to something like 3. svCol2:...

split your output to aggregator
then lookup seq file with hash file

welcome to dsxchange

First try to create a XSD, then import it in the XML output stage
You can easily create this xsd from a sample xml file using xmlspy

chulett wrote:Are you certain that in all that patching / killing that your DataStage server wasn't simply rebooted while your jobs were running? ...

The patching activities were done on MS SQL server cluster and process that was killed was DB processes. DS server was running and nothing was done on DS server.

ArndW wrote: a rare occurrence. ...

I hope so, if this rare occurence is due to absence of connectivity at time process kill.

Was DataStage reading from the database when it was failed over? If DataStage doesn't get an error from the DB then it cannot know that there is an error. Normally during a write the DB must return in ... That is where I am unable to reason - if DBA has killed the process why the job still in runni...

chulett wrote:They were still actually running or just in a 'running state'? Could you find active processes for the jobs? ...

Jobs were in Running State. We were not able to stop from Director.
We had to clear the status.

Recently I had face a issue. I found the jobs are in running status while it should be Aborted. Here I am talking about a DataStage server (hosted on a virtual machine) retrieves data from MS SQL Server hosted a different Cluster server I have went through the earlier post http://www.dsxchange.com/v...

From the very first post - using a query I can get below recods to update System Plan Id P1 102 202BILGN16 P1 102 202BILGN16 P1 102 202BILGN16 P2 103 202BILGN15 P2 103 202BILGN15 P2 103 202BILGN15 Based on this above data at least there is atleast another composite key. Hope you have identified all ...

I think the Delete operation is not working; and most probable reason can be that you are deleting Master table and FK constraint is not allowing.

But this should not create the INSERT problem, unless the record do exists in Master table with same PKs

Considering that we are working with KEY FIELDS. Here is an alternate design - pk1,pk2,pk3 = oldval input -----------> xfm------------ODBC (delete) | pk1,pk2,pk3 = newval | ODBC (insert) Use user define statement in each statement for example DELETE FROM "xyz" WHERE ("pk1" = ? AN...

Looks like this topic is related to earlier post
viewtopic.php?t=135099

Please describe your job design.

Still you can't do ? then my last suggestion is (considering that the table in which you are working is a Fact/detail table) -

Delete the existing rows with old keys and then Insert the new rows with new keys

Please update the Subject to something like "updating key column"

qutesanju wrote: input query -->transformer-->database table

Can you share the stage used and the Update statement used in stage