 |
 |
Archives of the TeradataForum
Message Posted: Thu, 06 Oct 2011 @ 22:53:45 GMT
| Subj: | | Re: Release mload is taking long time |
| |
| From: | | libin.jose |
Anomy.Anom wrote:
| | 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. | |
Hi,
I believe this happens when you choose "clean" mode at startup in the TD connector stage.
Try changing the property to "keep" and run the job and verify whether that is still generating any release mload statements.
Regards,
Libin
| |
