Navinth Bakmeedeniya, March 24, 2017 - 3:57 am UTC
Thanks for your update.
But why Oracle has implemented it in this way? Is there any special reason why Oracle blocking the revoke operation?
If Oracle proceeds the revoke operation when the view is invalid, any issue that can arise compared to the situation where view is valid? If there are no issues, why users should go for a workaround to complete the revoke instead implementing it in the expected way?
As I mentioned, I don't see any relation of revoke operation with the invalidity.
March 25, 2017 - 3:37 am UTC
It is what it is.
I have a bigger concern
Bill S., March 24, 2017 - 5:36 pm UTC
Why is your focus on the inability to revoke a grant and NOT on the fact that your view is invalid for a reason?
Fix the view, the grant becomes active and you can revoke it.
Seems eminently more sensible than asking Oracle to allow the revocation of privileges on objects that are not in a ready use state.
Monji Midani, August 07, 2017 - 7:32 am UTC
I have a task to lock any users and to revoke all privileges from these users.
There are any invalid views.
It is not my task to validate these views.
I have diffucilties to revoke privileges on invalid objects...
It is not logic to not allowed revoke privileges on invalid objects!
But it is allowed to grant privileges to locked users or to create synonyms for invalid objects....
August 07, 2017 - 8:42 pm UTC
You'd need to use the method I said before.
- remember the bad definition of the view
- replace it with a simple one
- revoke it
- replace it with the original one