Deadlocks during ETL using Informatica
Teradata Teradata Discussion Forums Teradata.com Discussion Forum
Visit Teradata.com
Home       Guidelines    Member List
Welcome Guest ( Login | Register )
        


This online forum is for user-to-user discussions of Teradata products, and is not an official customer support channel for Teradata. If you require direct assistance, please contact Teradata support.


Deadlocks during ETL using Informatica Expand / Collapse
Author
Message
Posted 10/17/2007 7:58:07 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 11/1/2007 6:11:06 AM
Posts: 1, Visits: 5
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.

Post #9278
Posted 10/29/2007 9:21:28 AM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: 9/22/2008 2:11:57 AM
Posts: 118, Visits: 62
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.


Regards
Ramakrishna_Vedantam
Post #9485
« Prev Topic | Next Topic »


Reading This Topic Expand / Collapse
Active Users: 1 ( 1 guest, 0 members, 0 anonymous members )
No members currently viewing this topic.


All times are GMT -5:00, Time now is 9:44am

Powered By InstantForum.NET v4.1.4 © 2008
Execution: 0.031. 9 queries. Compression Disabled.