![]() |
|
![]() |
![]() |
Archives of the TeradataForumMessage Posted: Tue, 13 Sep 2011 @ 07:55:14 GMT
<-- Anonymously Posted: Monday, September 12, 2011 20:35 --> Hi Macha, Thanks for your direction. I had already been through that thread. The thread kind of points/confirms that Normal mload does not make use of the "release mload" statement. Its the exclusive issue of the statement which causes the issue. I need to understand whether the Teradata Parallel Transporter or the Teradata connector component of the Datastage explicitly issues this "release mload" statement or whether there is some setting in the Datastage where the issue of this statement can be avoided. Unfortunately the Datastage guys are not able to provide much detailed logs. The IBM Datastage support guys are saying that Teradata Parallel Transporter as part of its API puts a exclusive lock on the table. I don't think its true. Does someone has any idea about it. Thanks for all your suggestions. With every suggestion we learn something new. Thx.
| ||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
![]() | ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||