Deadlocks during ETL using Informatica

Not applicable

Deadlocks during ETL using Informatica

We are using TPump upsert, updates while running ETL against Teradata using informatica.

workflows are failing because of deadlocks. As i understand because transactions are read committed by default, select statements lock the table and prevent updates.

I noticed that in Informatica loader Tpump configuration, it serialize is unchecked, deadlocks issue get resolved.

Can somebody explain me what role does serialize plays here and how it is able to avoild deadlocks on table for concurrent running workflow sessions.


Re: Deadlocks during ETL using Informatica

Why dont you create corresponding views for the tables to be loaded with access locks defined in the view and then use these views for the load purposes rather than directly loading the tables. This might solve your deadlocks problem.