|
|
Archives of the TeradataForum
Message Posted: Thu, 18 Sep 2003 @ 19:20:53 GMT
Subj: | | Re: COGNOS Impromptu Scheduler |
|
From: | | McBride, Michael |
Sorry, what I meant, In the case of MLOAD (not MLOAD itself) is when your script contains drop and create secondary indexes in the load
script you will get blocked (we do this to expedite the ETL) ...MLOAD does not request EXCLUSIVE LOCK ...but these DDL statements do and can
get blocked as is also the case with the RENAME TABLE commands ....
What I said previously, STILL holds true, "...[ ANY REQUEST ] that requires an EXCLUSIVE LOCK..." will get blocked even when your user
views are requesting ACCESS locks through COGNOS, as long as the sessions had not logged off ...
Similarly, ARCMAIN has the same problem for running backups if a COGNOS session is holding access locks even after the query has
completed and the session is 'idle' . We have ran into this on a number of occasions here at American Eagle. We logged an incident with the
GSC on this very issue, but NCR claims it is exclusively (no pun intended) a COGNOS issue, thus the workaround in my previous post...
| |