Archives of the TeradataForum

Message Posted: Fri, 30 May 2008 @ 14:08:51 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Hello,

after the upgrade of our DEV and TEST machines from V2R5.1 to V2R6.2 we have discovered duplicities in DBC.AccessRights (4 on DEV, 118 on TEST).

Duplicities may be displayed by

     Select
              UserId,
              DatabaseId,
              TVMId,
              FieldId,
              AccessRight,
              count(*) as Occurring,
     from DBC.AccessRights
     group by 1, 2, 3, 4, 5
     having Occurring > 1
     order by 1, 2, 3, 4, 5;

For each two problem records in DBC.AccessRights the only difference is in the CreateTimestamp column. One of them contains NULL, the other contains timestamp.

Duplicities can not be administered by standard revoke command.

Has somebody encoutered this behaviour and knows what has caused these duplicities?

How to repair our DBC.AccessRights?

What should we do to prevent it from happening during the upgrade of production system?

Thank you for your help

Lubomir

	<Prev	Next>		<<First	<Prev	Next>	Last>>