Archives of the TeradataForum
Message Posted: Mon, 13 Feb 2012 @ 15:34:29 GMT
Orphan rights not the similar to direct grants, those are the rows in dbc.accessrights be left behind after a drop table. I am not sure whether you are aware of the story behind how these orphan rows in dbc.accessrights be left behind even after the table has been dropped. Here is the answer...
In order to minimize blocking, a row that gets created in DBC.TVM that sets a TempFlag column with a value of 'I'. After performing operations on the table like granting rights inserting data etc the flag gets set to 'N' . If the table is archived before the flag gets changed to 'N' then later if the table gets restored (or arc copied) the flag gets set back to 'I'. So if at one point the table had a value of 'N' then after it gets restored (or arc copied) and set back to I, this is where we run into the issue of orphan rows getting left behind.
Come to the part of cleaning the rights, I don't think so you can able to clean these simply using REVOKE as these rights are created internally.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|