I have just started working in informatica tool.
I have an issue related to update strategy. Following is the issue.
In my mapping, there is one expression from which a router is connected. This router has a condition called 'UI' (Update & insert) which is in 2 groups. This logic is used bcos for UI condition i have to update the latest record based on the unique index and then insert a record for the unique index record. Hence for update i have a group called UI_Update for UI and for insert i have a group called UI_Insert for UI. Hence when such record comes to the router, the record will flow to 2 update strategies, one for updating the record in destination table and one for inserting the record in destination table. Here i am not able to prioritise which one should happen first - update or insert. The load runs the update strategy of insert before update strategy of update and i get a Unique index violation.
This problem is not happening in development environment. But after moving it to deployment group and deploying this to Test environment, such issue is raising. Even the data in the tables are same between development and test environments.
I tried redeploying to Test, same thing happened. I used normaliser transformation and i sequenced the insert operation after update, still insert is running first and throwing unique index violation error. Its a surprise that everything is working fine in development environment and the same code is not working in Test environment.
I confirmed the deployment process and its all perfect.
I am using informatica 8.6 and using SQL Server 2000. I recreated the whole mapping again and then redeployed and error didnt occur. Still am not able to find where the problem is.
Please let me know why this occurs. Thanks in advance.