Archives of the TeradataForum
Message Posted: Mon, 12 Sep 2011 @ 08:50:50 GMT
<-- Anonymously Posted: Monday, September 12, 2011 04:32 -->
We are facing a peculiar problem.
Recently the developers have started to use Data connector component of Datastage which uses Teradata Parallel Transporter for multiloading into Teradata Database.
The problem we face is if some user is running a dirty read on the target table then the job waits to acquire exclusive lock on the target table and in turn blocks all the other business users who are trying to use the target table for access.
From query monitor in TDWM we can see that a release mload is waiting for the exclusive lock on the target table.
My understanding is normal multiload does not explicitly issue the release mload command and during successful mload no exclusive locks are placed on the target table.
Exclusive locks are only required during the release mload statement which one manually issues if a cleanup is required after a mload failure.
Can anyone confirm if my understanding is correct.
Has anyone faced similar problem using Teradata Connector component of Datastage.
I have raised a case with IBM but its bit difficult as its a grey area between Teradata and Datastage.
Any help is appreciated.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|