Archives of the TeradataForum

Message Posted: Thu, 15 Jan 2004 @ 23:23:41 GMT

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

Could someone explain the allness flag to me in a comprehensive fashion? I've looked through the Teradata CD of manuals but find nothing but this explanation:

AllnessFlag Returns Y (yes) or N (no) to indicate whether or not the privilege was granted to all subordinate users, or to all users who are owned by the grantee.

This explanation isn't even worded very well. I assume that "Y" stands for the priviledge was granted to all subordinate users but the way it is worded that is an assumption not an obvious fact.

I'm particularly interested in an explanation that really highlights how parent-child relationships fit into this.

We've had problems with a higher parent (like a "SYSDBA" or "DBC" - a grandparent or great-grandparent if you will) not having access to a lower level database and then granting that access to "himself" and effectively "wiping out" access that lower level users previously had. These lower level users had originally been granted access by someone above them but below the "SYSDBA" or "DBC" level. These lower level users still show up with the access right, but the allness flag is N. While the flag remains N they can't access what they could before, and there is a lot of head scratching while we put the rights back the way we think they should go.

I'm not sure this is the only way we've caused problems for ourselves but I don't completely understand how the allness flag works and how it is tied into the parent/child relationship and subordinates versus owned users. I'd like to reach the point where I didn't worry that a given grant would "undo" or "overwrite" a previous grant by turning previous "Y" allness flags to "N" - whatever the "Y" or "N" means.

Patrick Fleischmann

Information Technology - Technical Services
Hallmark Cards, Inc.

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