Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Wed, 14 Apr 2004 @ 07:21:12 GMT

  <Prev Next>   <<First <Prev

Subj:   Re: COGNOS Impromptu Scheduler
From:   Anomy Anom

<-- Anonymously Posted: Wednesday, April 14, 2004 00:47 -->

Michael McBride

I want to clarify your comment in your earlier posts

Access Locking will not prevent contention in this scenario if you are using MLOAD or any DML such as table renames that require an EXCLUSIVE LOCK. The reason being is the COGNOS query tool (Impromptu) does not release locks, even access locks unless you have specifically set the read parameter to "READ UNCOMMITTED".

You can still query the Table being Multiloaded using an Access Lock. We are using views with Access Locking. So do we still need to have the 'READ UNCOMMITTED' option in Impromptu. And if we are using Views with Access Locking to develop Cognos Cubes, can we say that we will not have any locking contentions. We rarely drop or rename anything.


  <Prev Next>   <<First <Prev
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 28 Jun 2020